iLPdev / iLPdev/discMapper

Speedwalking with no wait or delay

Open
#129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
8
Forks
5
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the speedwalk handling and move queue for the speedwalk_delay=0 and speedwalk_wait=false path. Inspect how gmcp.room.info events report room changes during a walk, then verify with a walk of six or more rooms that the mapper continues tracking the location without creating rooms in the wrong place.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.