redshirt1

Thank you for your help, I missed the DirectX step.

It's a little strange that this happened all of the sudden because I had been using DX11 without issue until now.  :huh:

Good afternoon,

Trying to launch the WRobot client immediately crashes / closes the WoW client.

I have attempted to fix the issues by deleting and reinstalling the WRobot client.

Log is as follows:

[D] 13:12:10 - Log file created: 22 Jan 2015 13H12.log.html
[D] 13:12:10 - WRobot Version: 1.3.4 for wow: 6.0.3_19342
[D] 13:12:10 - Offical website: http://wrobot.eu/
[D] 13:12:10 - Operating System Details: Microsoft Windows NT 6.2.9200.0
[D] 13:12:10 - Lang: English (United States)
[F] 13:12:10 - D3D9 found: 6A 14 B8 48 4A 54 6B E8 47 4D 
[F] 13:12:11 - D3D11 found: 8B FF 55 8B EC 83 E4 F8 83 EC 
[D] 13:12:11 - D3D11 used
13:14:34 - Select game process: 86164 - Sto...

It works! Yay!  :D

Thank you very much!

I made sure my general settings match your screenshot exactly (even turning off things like "improve rotation") and ensured that my range was set to 5 in my fight class and it still refused to trigger even at 5.001 away. :(

I'm sorry to report that it doesn't seem to be working. I selected the new option and tried increasing the range of the profile, same behavior.

Training Dummy shows a max range in game of ~5.1, Wrotation won't respond until within 5.0.

Also tried a world boss mob (even bigger hit box) and still had to be within 5.0.

Awesome, can't wait to try it out. Sounds like a brilliant work around. :)

Hey Droidz, any progress on this issue?

 

Hi,

I say here when problem is fixed (the last update contains only new system for create quests profiles and fix for path generator).

 

I don't want to be a bother, but is there any update on this issue?

If the "check for good distance" code is available for public viewing I'd be happy to take a look at it and see if I can find anything. I imagine either that or the "range" code may be the culprit. :)

@loves: yes, that is what I tried :)

@Droidz: thank you for looking into it! I don't actually leave it unattended, I actually use it to allow me to play as I have bad arthritis - pushing lots of buttons hurts, but I enjoy coding the fight AI very much as it allows me to feel like I can still participate and play. :)

The main reason I pointed this out is because several NPCs (especially raid bosses) don't allow you to get within 5 yards. Some have built in push backs like Tortos where you automatically get shoved back before getting in range, some mobs fly higher than 5 yards on the z axis, etc.

I can manage movement just fine, but if I can't reach the mob WRotation won't work which means mashing my hand against the keyboard or avoiding those fights. ;)

Good afternoon!

There are quite a few NPCs with hit boxes greater than the default melee range of 5 yards, e.g. raid bosses; however, WRotation refuses to trigger melee skills if not within 5 yards of the NPC even though you can manually activate them.

Reproduction Steps

1. Expand "More info" section on main WRobot window to see triggered events
2. Engage an NPC with a hitbox that extends beyond 5 yards (e.g. Tortos, Megaera, etc.)
3. Watch "Target Distance" value in WRobot window
4. Move to 6+ yards of NPC, verify you can manually trigger melee abilities
5. At 6+ yards WRotation does not trigger events
6. Move within 5 yards of NPC, WRotation triggers events

Is there any way to account for larger NPC hit boxes at this time? I've tried increasing the range via the FightClass editor to 10+ yards but nothing seems to correct this issue.

Thank you!

Thank you for the quick fix!

Good afternoon,

I was using the Fisherbot without issue, but today after the update it is giving the following error message:

[Error] 15:12 - Engine > RunState(State state) > State: FisherbotState - System.MissingMethodException: Method not found: 'wManager.Wow.ObjectManager.WoWGameObject wManager.Wow.ObjectManager.ObjectManager.GetNearestWoWGameObject(System.Collections.Generic.List`1<wManager.Wow.ObjectManager.WoWGameObject>)'.
   at Fisherbot.Bot.FisherbotState.get_NeedToRun()
   at robotManager.FiniteStateMachine.Engine.KKXKYOULPALUHQGZPHJDUA(State JVMJLWQBMZJHSJTKJGKDO)
 

I tried restarting both Wrobot and the game, but no dice.