headcrab
Members
-
Joined
File Comments posted by headcrab
-
-
-
Lua function IsEquippableItem called in disenchant procedure. Did you put true for "DE green items" option?
Anyway, IsEquippableItem is present in vanilla WoW: http://vanilla-wow.wikia.com/wiki/API_IsEquippableItem
I did not tested disenchant in vanilla, maybe it not works. You can try to fix this error: open plugin in notepad, find 'IsEquippableItem' (line 77) and comment this line like this:
//if (!Lua.LuaDoString<bool>("return IsEquippableItem(" + item.Entry + ")")) continue;
-
-
-
-
-
-
too much copy-paste code. I suggest you to use Lists/arrays and loops like this:
public class Main : wManager.Plugin.IPlugin { private static List<int> ArtifactItems = new List<int>(){ 141926, 152435, bla bla bla }; private static List<int> ReputationItems = new List<int>(){ 147727, 146937, bla bla bla }; private static List<int> ContainerItems = new List<int>(){ 140225, 140226, bla bla bla }; private static List<int> ChestItems = new List<int>(){ 151467, 151465, bla bla bla }; ... private void OpenItems() { List<WoWItem> myItems = ObjectManager.GetObjectWoWItem() .Where(item => item.Owner == ObjectManager.Me.Guid && item.StackCount > 0); foreach (WoWItem item in myItems) { if (ArtifactItems.Contains(item.Entry) && WorldQuestBagItemsSettings.CurrentSetting.UABool || ReputationItems.Contains(item.Entry) && WorldQuestBagItemsSettings.CurrentSetting.URBool) { // use it ItemsManager.UseItem(item.Entry); Logging.WriteDebug("Using "+item.Name); Usefuls.WaitIsCasting(); } else if (ContainerItems.Contains(item.Entry) && WorldQuestBagItemsSettings.CurrentSetting.OCBool || ChestItems.Contains(item.Entry) && WorldQuestBagItemsSettings.CurrentSetting.ODBool) { // open it ItemsManager.UseItem(item.Entry); Logging.WriteDebug("Open "+item.Name); // and loot every slot Lua.LuaDoString("for i=1,GetNumLootItems() do LootSlot(i) end"); Usefuls.WaitIsLooting(); } } } }
Also, you using OCBool in your code 2 times and ODBool - never. Need to be fixed
Profession helper
in Plugins - MoP
Yes, it was my mistake, fixed in v1.3.8