Jump to content

Seminko

Members
  • Posts

    225
  • Joined

  • Last visited

Everything posted by Seminko

  1. So this must be the root of the problem. You're using non-vanilla Wrobot version, I use vanilla Wrobot, for you it's working, for me it's not. Thank you for trying man! @Droidz we might possibly have a bug on our hands.
  2. Thanks for that, I appreciate it! But as per my previous post, for some reason it doesn't work for me. Are you using WRobot for Vanilla? EDIT: Also, do you use Pathfinder (General Settings --> Path-finding)? What are your Class / Fight Class settings?
  3. So I did some testing. I put together a complete vanilla Fightclass and a Custom profile. Custom Profile: moves flawlessly both in and out of combat both backward and strafe (doesn't attack though, duh) Fightclass: Is set it up to shoot frost bolts if distance > 6, if the distance is smaller it should go backwards. And despite it being vanilla and converted from XML, it does the same stutter as shown in the video. So now we know the issue is not with my code but rather it's something in wrobot handling combat, not just Grinder. I tried using Party mode and aggroing a mob and same thing. @Apexx what wow version do you use wrobot for? Not sure if the wrobot versions are different or not but I cannot see any other reason why the code would work for you and not for me. @Droidz / @iMod, guys would you be willing to take a look? I'm going crazy already.
  4. Would you be willing to post your code, Apexx? I would like to check the differences.
  5. I wanted to avoid this as much as possible because I have NO IDEA how to do that but if you or someone is willing to help me with that I guess it would be a good solution if it worked.
  6. I'm begining to give up, honestly... So first issue, when I stop the fight and then start it again, the bot log says I started to fight the mob I was targetting before. BUT... it doesn't do anything, it just stares at the mob... But that's irrelevant since it doesn't solve the movement issue at all, still running in circles... Second thing. There seems to be an inconsistency between presskey and downkey. Both of them make the bot run in circles, however when I do: wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.PressKey, 1000); - it does only a small movement, maybe trully 1second and then stops (still circling though) wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.DownKey, 1000); - it does circles for a VERY long time, maybe 30 seconds... doesn't DownKey require an UpKey somewhere? wManager.Wow.Helpers.Move.Backward(Move.MoveAction.PressKey, 1000); - does the chopping movement I showed in the vid wManager.Wow.Helpers.Move.Backward(Move.MoveAction.DownKey, 1000); - actually moves back but there is still slight choppiness, it doesn't look like someone pressed a button and held it pressed, it looks like someone was mashing the key repeatedly in milisecond increments, look very bot like I also tried removing the MovementEvents and it didn't have any effect on how the bot acted...
  7. I don't know about you but when I see someone backpaddling it seems suspicious not to mention it is significantly slower than strafing. I would very much like to see if strafing worked for you. Would you try and let us know?
  8. Since I see Vector3, do you manage the movement yourself? Because I don't, I let the bot decide the movement. Also try it with Move.StrafeLeft Also what does the ManageMovement setting do? EDIT: With my poor understanding of CSharp and the bot itself I've seen some people claiming they handle the toon movement themselves using a separate code. I don't even know if that could be done but worth asking...
  9. Here's an idea, does facing the target count as movement? Because if it doesn't it would make sense... we're trying to cancel bot movement but facing the target is still there? This is probably not the case but I'm trying to think of everything because we don't seem to be able to find out what's wrong.
  10. lol are you serious DownKey instead of PressKey, so obvious, yet still not so... :-D Alright, so Move.Backward + DownKey works, but that would work even without all the MovementEvents_OnMovementPulse shennanigans. When I try wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.DownKey, 1000); it STILL tries to face the target, running around in circles, practically indefinitely because I am well within the 6yr range we set up in the while loop. I even tried ForceIgnoreAttack, still the same thing. The strange thing is that even though it leaves the 6yr radius it continues strafing. It's like it doesn't wait for the movement to stop to continue. while (ObjectManager.Target.GetDistance <= 6) { wManager.Wow.Helpers.Conditions.ForceIgnoreIsAttacked = true; isTooClose = true; wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.DownKey, 2500); // wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.PressKey, 1500); wManager.Wow.Helpers.Conditions.ForceIgnoreIsAttacked = false; //Thread.Sleep(1250); } If the bot doesn't wait for the Move to resolve before continuing the script I tried putting in Sleep. Still the same thing, runs around in circles until the mob is dead. while (ObjectManager.Target.GetDistance <= 6) { wManager.Wow.Helpers.Conditions.ForceIgnoreIsAttacked = true; isTooClose = true; wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.DownKey, 2500); // wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.PressKey, 1500); Thread.Sleep(2500); wManager.Wow.Helpers.Conditions.ForceIgnoreIsAttacked = false; //Thread.Sleep(1250); }
  11. Also, tried with StrafeLeft and it does the same thing I've been explaining at the begining, it just runs circles around the mob... I'm frustrated...
  12. What does that parameter mean? I haven't been able to find any explanation to it so I assumed it defined how long should the movement be active for, in other words for how long the key should be pressed. I tried this, which somewhat works but it moves backwards REALLY choppy, it really looks like it presses S every 50ms, however changing it to something like 5000 doesn't do much... while (ObjectManager.Target.GetDistance <= 6) { isTooClose = true; wManager.Wow.Helpers.Move.Backward(Move.MoveAction.PressKey, 50); // wManager.Wow.Helpers.Move.StrafeLeft(Move.MoveAction.PressKey, 1500); //Thread.Sleep(1250); }
  13. Alright, here is the FULL code I use so you can actually try it for yourselves: Removed And here's the video: https://www.youtube.com/watch?v=GW3p0FZMMCE
  14. I'll try to record it so you guys know what I'm talking about.
  15. They exist :) I just removed them from the enclosed code because they're not relevant for our issue :) True, adding it now :)
  16. For reference, here is the code without errors, but still bad movement:
  17. Nope, does the same thing :( moves an inch back, waits a few ms, moves an inch back etc... definitely not that 1250ms as expected
  18. Ha, no error this time... Let me see if it does what we're after... Be back in a second with an update.
  19. Alright, this solved the error. Now it has a problem with these two, saying that the line if (isTooClose) or to be more specific Main.isTooClose requires a link to an object (or sth similar, I have it in my native language, not english) private static void MovementEvents_OnMovementPulse(List<Vector3> points, CancelEventArgs cancelable) { if (isTooClose) { cancelable.Cancel = true; } } private static void MovementEvents_OnMoveToPulse(Vector3 point, CancelEventArgs cancelable) { if (isTooClose) { cancelable.Cancel = true; } } Also, this is my first encounter with C# hence these, probably obvious, mistakes on my part.
  20. Didn't help. Now it says MovementEvents doesn't exist in the current context No I don't, i use Notepad++ and the code looks good inside but gets messed up when I paste it here Tried using this and same as above, it doesn't exist in the current context. Am I missing "an include"? I mean "using xyz"?
  21. Nope I use CSharp Edit: should I post my code? Maybe it would be easier to spot where the issue is
  22. Received an error. Seems the bot doesn't like the ' += ' and ' ; ' in this: MovementEvents.OnMoveToPulse += MovementEvents_OnMoveToPulse; MovementEvents.OnMovementPulse += MovementEvents_OnMovementPulse; Or I put it where it doesn't belong.
  23. So I should use the code in the way I guessed above? EDIT: nope, that doesn't seem to be the correct usage.
  24. Could you please ellaborate on that? How would I use it correctly? EDIT: do I just go with this, then use Move.Backwards and then set it to false? wManager.Events.MovementEvents.OnMovementPulse += (points, cancelable) => { cancelable.Cancel = true; };
×
×
  • Create New...