-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Describe the bug
Per help automation in discworld, speedwalking is only legal if you send all direction commands at once, not delayed as you walk. Since that is policy, I disable the speedwalk_delay and speedwalk_wait. When you do this, the mapper only tracks where you are for 2-4 squares before it stops tracking. If you then don't update the location through a look or map me, new rooms get created in the wrong location. It's more annoying than a killing bug, but part of the point of a visible map is to watch where you are on the map.
To Reproduce
Set speedwalk_delay to 0.
Set speedwalk_wait to false.
Speedwalk to a room 6 or more rooms away.
Expected behavior
Map should continue to track your location throughout your walk.
Screenshots
If applicable, add screenshots or an animated .gif to help explain the problem.
Environment (please complete the following information):
- discMapper Version: 0.5 beta
- Mudlet Version: 4.10.1
- OS: Windows 10
Additional context
I suspect the problem is that the move queue doesn't get all the directions when sent out that fast.
What I think might be done to fix the problem, is set a variable / flag to true, and follow the speedwalk path through the gmcp.room.info event generated by Mudlet whenever gmcp.room.info is sent. Discworld sends that whenver a new room is entered, you look, or you glance. I'd be happy to help with this, and other stuff in the mapper.