What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

regarding the npc stuck

paella

New Member
Joined
Mar 10, 2014
Messages
8
Reaction score
0
as we all know, there has been a bot problem regarding the bot getting stuck in town (particularly acts 1 and 3) trying to sell to the npcs, but instead, getting stuck there just open and closing the npc dialogue.

i've observed my bot and saw that this particularly happens when the bot toggles the "Always Highlight" option by itself, in which case, it should not. and when the stuck happens, upon reloggin in the game, the "Always Highlight" option is ticked, thus making the problem.

hoping for a fix on this. thanks :)
 
Last edited:
The problem shouldn't be Always Highlight, but rather the bot not handling quest rewards/dialogs correctly anymore after that code was changed to fix another stuck issue that happened under really specific cases.

The issue should be fixed in our test version, but a few other things are being worked on to try and take care a lot more things at once before we push the next beta version.
 
Have you made sure you haven't changed or removed the button for exiting all windows? I did this as I use spacebar to attack standing still, so the bot didn't have a button to close any windows at npc's.
 
so you're telling me to change my button for exiting all windows so that this bug doesn't happen?
 
so you're telling me to change my button for exiting all windows so that this bug doesn't happen?

That used to be an issue, but it's fixed now. The client was hard coded to use Spacebar to close a NPC window, which overlapped with the default button for Close All Panels.

When you remapped Close All Panels from Spacebar, the bot would no longer close the NPC window, since the client is hard coded to use Spacebar and not the key for Close All Panels.

Our code now takes this into account to avoid that issue. The next Beta will contain new code to hopefully avoid the new issue of it trying to move too close to the vendor. It'll be built sometime today.

During my testing before the beta was built, it seemed to be working, but due to the number of reports, I guess something wasn't triggering for me that is for everyone else right now. The new code should work much better anyways though
 
Please test Beta #780 to see if the issue is fixed for you.
 
Back
Top