The Dink Network

Reply to wait_for_button DinkHD weirdness

If you don't have an account, just leave the password field blank.
Username:
Password:
Subject:
Antispam: Enter Dink Smallwood's last name (surname) below.
Formatting: :) :( ;( :P ;) :D >( : :s :O evil cat blood
Bold font Italic font hyperlink Code tags
Message:
 
 
March 24th, 06:16 AM
custom_simon.gif
SimonK
Peasant He/Him Australia
 
So doing some testing and for some reason the wait_for_button command stops recognising the CTRL button being pushed - i.e. it does give &result a value of 1. But the other keys are working...

I am in DinkHD debug mode, so not sure if that is impacting, but it only seems to exhibit this error on one screen after defeating the summoned knight in Story 2 of SOB.

I've used the translocation spell to fight with bow and arrow from the mud, but while I can use the magic to get into the mud, I can't complete the next spell to get out as wait_for_button is looking for &result to equal 1 to exit the loop of positioning the target of where to teleport to.

So I added the line of using spacebar to achieve the same effect as ctrl and that works...

This was working fine before... in DinkHD, at least a month ago when I last tested this part.

=====================================================================

Weird thing is the same thing happens using the Ultimate Cheat warp.

And even weirder, if I save the game at that point using Ultimate Cheat, then reload it, the wait_for_button() command now registers the CTRL key press.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

As you can talk to the Mudman from the mud you can still complete this task and move onto Story 3 the Desert, which is serendipitous - but still would like to know why the CTRL button press stops working for a bit.

I guess I'll see if the error happens in freedink at this point of the game.