It's because target_NPC doesn't provide a y value.
I've added a check for the Y value in 'moveInRange' like I added in moveTo. I'll wait just a bit longer to see if other problems show up before committing.
Please consider making a small donation to me to support my continued contributions to the bot and this forum. Thank you. Donate
I check all posts before reading PMs. So if you want a fast reply, don't PM me but post a topic instead. PM me for private or personal topics only.
Maybe a check can be made: if target's Y-coord value is nill -> take player's Y as target Y, else use target.Y
should solve the prob.
(better to implement in bot than all of us changing files)
Bot now tries to movein and use melee skills before it states it is moving into melee range. While doing this it does a little dance with mob as it keeps moving forward continually. and as it uses a melee skill it spins to face target, as it's still moving forward it runs thru target and then as it uses another skill spins to face it yet again. It does this continually until it posts the moving into melee suguested range
Edit: Seems to only occur when it sees a mob to kill as it is arriving at a waypoint spot.
If it has
Use F: SCOUT_SHOT => Mud Lord (21142/21142)
Use 5: SCOUT_VAMPIRE_ARROWS=> Mud Lord (21142/21142)
Use F: SCOUT_SHOT => Mud Lord (20001/21142)
Ranged pulling finished, mob in melee distance.
Use 2: ROGUE_SHADOWSTAB => Mud Lord (19200/21142)
Use 4: ROGUE_LOW_BLOW => Mud Lord (18334/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (17533/21142)
Use 4: ROGUE_LOW_BLOW => Mud Lord (16227/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (12876/21142)
Use 4: ROGUE_LOW_BLOW => Mud Lord (10708/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (8967/21142)
Use 4: ROGUE_LOW_BLOW => Mud Lord (7162/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (6188/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (5436/21142)
Moving in | Suggested range: 50 | Distance: 67
Use 2: ROGUE_SHADOWSTAB => Mud Lord (2321/21142)
Use 4: ROGUE_LOW_BLOW => Mud Lord (1756/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (1299/21142)
Use 2: ROGUE_SHADOWSTAB => Mud Lord (0/21142)
Remember no matter you do in life to always have a little fun while you are at it
The behaviour you are describing sounds like the way it behaved when applying that original suggestion I had for removing the pauses at waypoints in this post. http://www.solarstrike.net/phpBB3/viewt ... =21&t=2320
If you tried this, then please restore it as that didn't work properly. Revision 586 shouldn't pause at waypoints and shouldn't behave as you described.
Please consider making a small donation to me to support my continued contributions to the bot and this forum. Thank you. Donate
I check all posts before reading PMs. So if you want a fast reply, don't PM me but post a topic instead. PM me for private or personal topics only.
rock5 wrote:The behaviour you are describing sounds like the way it behaved when applying that original suggestion I had for removing the pauses at waypoints in this post. http://www.solarstrike.net/phpBB3/viewt ... =21&t=2320
If you tried this, then please restore it as that didn't work properly. Revision 586 shouldn't pause at waypoints and shouldn't behave as you described.
Nope did a full update & revert to current revision.
Not sure why it was doing this, was really weird.
If it was moving to a waypoint it worked fine, it would only do the weird thing if it was at the waypoint coords and doing it's turn to next waypoint and then started fight.
I'll do some more testing to narrow it down.
Remember no matter you do in life to always have a little fun while you are at it