Everything posted by Matenia
-
FNV-Quester Error Droids how do I fix this?
The error doesn't do anything, but you are trying to use a vanilla fightclass in TBC so that's never gonna work
-
Elevators (OffMeshConnection) all seem broken since latest update
Hey Droidz, it seems wRobot falls off Elevators since the last update. Did you change anything about pathing/movement in general?
-
Repairing at full durability
Don't set it to buy new food if you don't have vendors in your database/profile that sell food. wRobot won't know which vendors sell which stuff, unless you all set it up correctly. So if you're unlucky, it continues going to a vendor that doesn't sell food, then tries again and again. It's also possible you have set yours up to vendor every x minutes. Can't actually tell, since only ONE person in this thread has posted a log file.
-
Left click unit
Because target guid is a static offset in WotLK. ObjectManager.Me.Target = unit.Guid; works, or if you want to set mouseover: private static void SetMouseoverGuid(ulong guid) { switch (Usefuls.WowVersion) { case 5875: Memory.WowMemory.Memory.WriteUInt64((uint)Memory.WowMemory.Memory.MainModuleAddress + 0x74E2C8, guid); break; case 8606: Memory.WowMemory.Memory.WriteUInt64((uint)Memory.WowMemory.Memory.MainModuleAddress + 0x86E950, guid); break; case 12340: Memory.WowMemory.Memory.WriteUInt64((uint) 0x00BD07A0, guid); break; default: throw new Exception("Wow version is not supported!"); } } private static void SetMouseoverUnit(WoWUnit unit) { SetMouseoverGuid(unit.Guid); } public static void Target(WoWUnit unit) { ulong guid = unit.Guid; if (guid == 0) { return; } ulong tmp = Memory.WowMemory.Memory.ReadUInt64((uint)Memory.WowMemory.Memory.MainModuleAddress + 0x74E2C8); SetMouseoverUnit(unit); Lua.LuaDoString(@"TargetUnit(""mouseover"");"); //do something here SetMouseoverUnit(tmp); }
-
Some assistance required configuring the bot
Please update the fightclass (by redownloading) and try again. I made some updates to it recently that could potentially resolve a range pull problem. Please also make sure you aren't using the wRobot setting "Caculate target distance by size", as that is only needed for buggy vanilla servers and causes a lot of issues in TBC.
-
Repairing at full durability
Are you sure? Some guy tried your vanilla hunter on TBC and it somehow messed up using items. Although that is probably a side effect of backport stuff that didn't exist in vanilla nd then overwriting its functionality (accidentally) when they use it on the wrong client.
-
Repairing at full durability
It's possible that @Ordush modifies a Lua function that Droidz uses to read whether you need to go to repair
-
[PAID][TBC] Enhancement Shaman 1-70
I just completely overhauled this fightclass as part of me rewriting my framework for TBC. It's currently probably the most advanced. Although you will have to request the beta on Discord after purchase because I'm not yet 100% comfortable with releasing it.
- 12 comments
- 4 reviews
-
[FREE] FoodAndDrinkHelper
[D] 00:48:53 - [AutoSelectFoodAndDrink] Select drink: Refreshing Spring Water[D] 00:48:53 - [AutoSelectFoodAndDrink] Food: 0[D] 00:48:53 - [AutoSelectFoodAndDrink] Out of food, force wRobot to town If you don't want it to buy food, you nede to modify the code. There's a reason this is a free alternative I provide for a paid plugin. You don't get the full experience of being babysat.
-
Mass ban on Northdale
He didn't say it, someone else talked about it. And the guy is an actual genius both in terms of reverse engineering the client and creating anti-cheat by reversing warden. I have yet to see anything from you that wasn't selling chars you mass-botted with someone elses software and the occasional highrating after PvP in this game had already been dead for years.
-
[PAID][TBC] Feral Druid 1-70
Make sure to disable all addons. Also make sure if you are running catform, you understand that you can't range pull unless you already have Fairie Fire (Feral). Otherwise you'd waste way too much mana.
- 12 comments
- 5 reviews
-
[PAID] HumanMasterPlugin
I already check target health (you can decompile to check for yourself). The problem is, if I add more variables (such as health+mana combined by AND operator), it's becoming too complicated for people to use. They already currently have problems configuring the functionality.
- 188 comments
- 19 reviews
-
[TBC] WoW Error #132 happening in the same spot
Unfortunately, I don't know. It's possible my client has somehow been corrupted or my memory might be broken. I guess I will have to do a mem-scan when I have the time. If anyone else mentions this issue, I will redirect them here.
-
Taking over my quest profile
There was a very early version of this profile that went level 1-28. I worked on this and gave it to bambo, so that he wouldn't have to implement 300+ quests by himself. He added 30-50 completely from scratch, did all starting zones, added class quests AND made sure all the quests in it do work and aren't done at too low/high level etc. Compared to the last iteration of the Enraged (guy who took over Arcangelo) quest profile, there are no similarities. Enraged started it from scratch because Arcangelo scammed him promising him money for his help, then completely disappearing. The profile in this thread was always utter shit. He never tested much and if he did, only on Hunter. Alliance never worked to begin with and Horde was alright at best. Both the last iteration of Enraged and Bambo are in no way comparable to this shit show.
-
How does this bot handle PVP on Northdale?
Unless you're proficient in C# and willing to code this yourself, you won't be able to achieve that.
- [PAID] Affliction/Demonology Warlock 1-70
-
[TBC] WoW Error #132 happening in the same spot
-
[TBC] WoW Error #132 happening in the same spot
I only know about me getting it and my fightclass uses it (only in combat) but the error happened out of combat (weird). I moved my char about 20 yards away from that position and the bot ran 100% fine after that. It was only at those coordinates for some reason.
-
Stop ObjectManager updates?
I was locking frames before, that's why it confused me, that sometimes iterations took 400ms+. Currently rewriting my rotation framework for TBC. Will try locking frames again and let you know. I think storing all units by reference is a good idea. I will look into that. If I still have any problems after next update, I will get back to you. Thanks!
-
Stop ObjectManager updates?
Hey Droidz, I noticed sometimes ObjectManager is updated while I iterate it in my rotation. If I use a lot of checks on units in the ObjectManager, it can slow down my rotations a lot. Sometimes iterations jump from 50ms to 500ms ("randomly") I noticed especially on TBC, this is because the ObjectManager in game gets huuuuge and wRobot takes a "long" time on every update. I noticed (I think) ObjectManager gets locked during these updates and the lock makes my thread wait. Sometimes, this lock can happen two or three times during one iteration, if I get unlucky. One way to prevent this would be to deepcopy the entire ObjectManager (or use my own implementation, reading directly from memory with wRobot API). Both of this would be a loooot of work. Therefore I have a question, something that would be way easier: Can I stop ObjectManager from behind updated manually? Pseudo code here: ObjectManager.DisablesUpdates(); for(spell in spells) { if(spell.AllConditionsTrue()) { spell.Cast(); break; } } ObjectManager.EnableUpdates();
-
Announce Interrupts LUA script
99.99% sure that's a bug with your server not firing the correct event, warmane has never been too thorough with that
-
Party Bot
- [TBC] WoW Error #132 happening in the same spot
Not sure how exactly this is being caused, but it happens every time he quester profile (Andoido's Horde quester) reaches the step for The Defense of Grom'gol (PART 2).- Netherwing TBC Server
- [Pathing] Don't prioritize roads when dead
This is more of a feature request to save time. Currently, when you are dead, wRobot still prioritizes roads when using pathfinding. It should just use the rgular path, ignoring roads. This would help save time a lot when running back to corpse. - [TBC] WoW Error #132 happening in the same spot