Target NPC and Pathing broken

[GurdyMan]

This just started between revision 246 and 253 but it doesn't find the right person.

Target Locken in Silverfall.

Code: Select all

	    player:target_NPC("Locken");

This finds Helen Yis and talks to her.

Game outputs:

We try to find NPC Locken: Locken,
We successfully target NPC Locken and try to open the dialog window.

What's also weird is my waypoint is supposed to put me in front of Locken, but instead it places me next to Helen who is on the other side of a caravan. My deviation is set to 0.


Also, why is he so jerky now? I liked the smooth movements.

[GurdyMan]

Just ran it again and the bot would get stuck on open road and the romscript times out a lot. This didn't happen with the first run.

Code: Select all

We use the normal waypoint path AnteaterDQ.xml now.
Clearing target.
Moving to waypoint #3, (-5238, 3114)
Paused. (Delete) to continue, (CTRL+L) exit to shell, (CTRL+C) quit
Resumed.
Clearing target.
Unsticking player... at position -5382,3213. Trial 1 from maximal 10 trials
Moving to waypoint #3, (-5238, 3114)
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
Clearing target.
Unsticking player... at position -5317,3209. Trial 2 from maximal 10 trials
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
Moving to waypoint #3, (-5238, 3114)
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
TIMEOUT in RoMScript ...
Clearing target.

And the third time he just ran a wide circle (over 100ft in diameter) around the area getting stuck at every open place possible.

I reverted back to r246 for now. Everything's working again.

[Administrator]

And the third time he just ran a wide circle (over 100ft in diameter) around the area getting stuck at every open place possible.

I reverted back to r246 for now. Everything's working again.

I'm not entirely sure what could have done it. There really wasn't any changes that should effect that. However, it could have to do with the keyboard delay, maybe. Try adding keyboardSetDelay(0) right above the attach() call in bot.lua. Does it start happening again with that code?

[GurdyMan]

And the third time he just ran a wide circle (over 100ft in diameter) around the area getting stuck at every open place possible.

I reverted back to r246 for now. Everything's working again.

I'm not entirely sure what could have done it. There really wasn't any changes that should effect that. However, it could have to do with the keyboard delay, maybe. Try adding keyboardSetDelay(0) right above the attach() call in bot.lua. Does it start happening again with that code?

I had made that change before I updated and it ran for hours without issue. It wasn't until I deleted my modified files and did a full update to r253 that it started. Also, with delay set to 0 bot was still moving smoothly.

Maybe look at the diffs and see if something was removed on accident?

[Administrator]

I had made that change before I updated and it ran for hours without issue. It wasn't until I deleted my modified files and did a full update to r253 that it started. Also, with delay set to 0 bot was still moving smoothly.

Maybe look at the diffs and see if something was removed on accident?

That's the strange thing. It doesn't look like any of the changes since r246 should have any effect on that. I guess the best thing to do is to narrow it down by reverting to different versions.

EDIT: Just tested it out, and it seems like the problem was keyboardSetDelay(). I'll look into a proper fix.

[j_schlott]

i am also having issues targetting npcs now, all my code has been set for weeks, so its something new that is going on


neither one of the commands:

Code: Select all

player:target_NPC("")
or
player:merchant("")

are working for me atm

seems to be the same for me as the above poster , MM says successfully targetted NPC but its targetting any other npc close to the one i want


***EDIT***

i deleted this from bot.lua:

Code: Select all

keyboardSetDelay()

and things seem to be working as they did before

[Administrator]

This is fixed in r264. You can turn keyboardSetDelay(0) back on.