Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange move after a door explode #11

Open
medrimonia opened this issue Feb 22, 2013 · 1 comment
Open

Strange move after a door explode #11

medrimonia opened this issue Feb 22, 2013 · 1 comment
Labels

Comments

@medrimonia
Copy link
Owner

During a game, a move wasn't resulting with the expected position (moving north-east instead of east, checking in mm_log shows that a door has exploded just before).

GAME :

SEED=1361531833
bot= diffusion

mm_log last information :

mm_print_glyph: window 3 - 47:14:@
send(): g 0x2f 0xe @
mm_print_glyph: window 3 - 46:15:.
send(): g 0x2e 0xf .
mm_curs: 
mm_display_nhwindow: 3
mm_nh_poskey: 
send(): E
recv(): u
send(): S
mm_clear_nhwindow: 1
mm_get_nh_event: 
mm_cliparound: 
mm_print_glyph: window 3 - 48:13:@
send(): g 0x30 0xd @
mm_print_glyph: window 3 - 47:14:.
send(): g 0x2f 0xe .
mm_curs: 
mm_display_nhwindow: 3
mm_nh_poskey: 
send(): E
recv(): ou
send(): S
mm_clear_nhwindow: 1
mm_yn_function: In what direction?
mm_raw_print: The door opens.
mm_raw_print: KABOOM!!  The door was booby-trapped!
mm_raw_print: You stagger...
mm_get_nh_event: 
mm_curs: 
mm_putstr: Ludovic the Hatamoto   St:18/01 Dx:14 Co:16 In:10 Wi:8 Ch:6  Lawful
mm_curs: 
mm_putstr: Dlvl:6  $:0  HP:7(15) Pw:2(2) AC:10 Exp:1 Stun
mm_cliparound: 
mm_print_glyph: window 3 - 49:12:.
send(): g 0x31 0xc .
mm_curs: 
mm_display_nhwindow: 3
mm_nh_poskey: 
send(): E
recv(): s
send(): S
mm_clear_nhwindow: 1
mm_get_nh_event: 
mm_cliparound: 
mm_curs: 
mm_display_nhwindow: 3
mm_nh_poskey: 
send(): E
recv(): l
send(): S
mm_clear_nhwindow: 1
mm_get_nh_event: 
mm_cliparound: 
mm_print_glyph: window 3 - 48:1:-
send(): g 0x30 0x1 -
mm_print_glyph: window 3 - 49:1:-
send(): g 0x31 0x1 -
mm_print_glyph: window 3 - 50:1:-
send(): g 0x32 0x1 -
mm_print_glyph: window 3 - 49:2:.
send(): g 0x31 0x2 .
mm_print_glyph: window 3 - 49:3:.
send(): g 0x31 0x3 .
mm_print_glyph: window 3 - 50:3:|
send(): g 0x32 0x3 |
mm_print_glyph: window 3 - 49:4:.
send(): g 0x31 0x4 .
mm_print_glyph: window 3 - 50:4:|
send(): g 0x32 0x4 |
mm_print_glyph: window 3 - 49:5:.
send(): g 0x31 0x5 .
mm_print_glyph: window 3 - 50:5:|
send(): g 0x32 0x5 |
mm_print_glyph: window 3 - 49:6:.
send(): g 0x31 0x6 .
mm_print_glyph: window 3 - 49:11:#
send(): g 0x31 0xb #
mm_print_glyph: window 3 - 49:12:@
send(): g 0x31 0xc @
mm_print_glyph: window 3 - 48:13:.
send(): g 0x30 0xd .
mm_curs: 
mm_display_nhwindow: 3
mm_nh_poskey: 
send(): E

Result seems normal in fact according to the fact that player was stunned:

http://nethack.wikia.com/wiki/Stun

What should we do? Suppress stun, suppress traps still there on doors? I'll try to make an hotfix in the bot, but it might not be possible.

@medrimonia
Copy link
Owner Author

By deactivating the part of the bot that handle situation where location received is not the one we wanted, everything seems to work better, but this still means that some traps can occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant