Bug: `capture_move_cmd` error on connect

Question

Bug: `capture_move_cmd` error on connect

Closed this issue 4 years ago · 3 comments

iLPdev commented 4 years ago

Describe the bug
LUA error from capture_move_cmd on connect when called by sysDataSendRequest event handler.

To Reproduce
Connect to game server.

Expected behavior
No error.

Screenshots

Environment (please complete the following information):

discMapper Version: 0.4.0-beta
Mudlet Version: 4.9.1
OS: win10

Additional context
Not sure how long this has been going on or if it's new.

Answer 1 · 2020-07-23T20:29:37.000Z

Could not reproduce with clean profile.

Answer 2 · 2020-07-23T21:48:54.000Z

It's baAAAAaaaaaacccck.

Seems to only happen on initial connection when opening a profile with connect rather than offline mode.

Things to do:

Investigate where it's calling configs from outside capture_move_cmd.
Investigate if this was pre-existing in generic_mapper.xml.

Answer 3 · 2020-07-26T08:21:53.000Z

once again, I am unable to reproduce this error. so.... when does it begin? does it happen in relation to the check_version timer?

I was also unable to reproduce this in generic_mapper.xml despite it, too, calling config() from outside the local function (how is it able to do that?)