mrimer wrote:
kieranmillar wrote:
Going to selfishly bump this because it turns out it's a bit of an issue in something I just tried to implement. Would be great to help add more flexibility to what you want pressing the command button to do.
Sorry, I'm not clear which of the three issues reported here is what you're referring to. Would you please clarify and post a barebones hold to reproduce the issue? Thanks!
Edit: is this the same issue you posted here?
Apologies, I didn't actually quote the part I was talking about, which is this problem:
TFMurphy wrote:
A Answer-based Question asked in a Cmd script fired via Each Use does *not* pause its execution when the Question is asked. As a result, whatever is immediately after the question is run first, no matter what the result of the Question is. Only on the turn after the Question does the correct result occur.
This is not the same as the issue in the other thread you linked to.
I have attached a test hold demonstrating the issue. When pressing the command key, you get given a choice of what type of key you want to gain, but it always ends up running the first choice and giving you a yellow key before the question pops up. (Choosing to gain a yellow key gives you a second one).
What should happen: lines of scripting after the Question command should not execute until the player actually answers the question.
EDIT: I just checked out of curiosity, and it seems the same bug occurs if you put the script into your accessory slot instead of the command slot, so it might be a problem with questions inside Each Use commands in general instead of explicitly an issue with the special command key.
[Last edited by kieranmillar at 03-14-2016 08:17 PM]