I have a minigame system that goes off button presses. It tells you things like "Press Up!" and "Press Shift!"
Input.dir8 != 0 and !Input.trigger?(Input::UP) works for the 4 / 8 directional movement system. But when I want to do a Shift or Q key, I'm stumped.
What is the line of code to make sure a player is pressing a button, but not pressing the right one?
Full Version: No button press. [SOLVED]
I'm on a phone so... Rpg maker > help file > search > input > constants.
Hope that helps.
Hope that helps.
That's the first place I went, and how I found the Input.dir8 But there is nothing in there that mentions how to do a check for any button press.
If the player presses W when he should press Space there is no penalty. Only if he presses any of the direction keys. I want to make it so there's a penalty if he presses any button.
If the player presses W when he should press Space there is no penalty. Only if he presses any of the direction keys. I want to make it so there's a penalty if he presses any button.
At the bottom of that page you'll see a tab called 'Constants' in bold are the keys you can check for press.
So you're saying I have to do like 150 different lines of !Input.trigger?(Input::BUTTONWHATEVER) if I want to check if the wrong button is being pressed plus one for if the right button is being pressed? 
I wanted it to make a sound and force you to wait if you pressed the wrong button.
I wanted it to make a sound and force you to wait if you pressed the wrong button.
you don't need to include handling for every incorrect option, instead have something like:
CODE
unless Input.trigger?(Input::BUTTONWHATEVER) # this means unless the correct button was pressed, which means ANY other button will trigger this condition
#beep here
#wait here
#whatever for the wrong condition
else # this is in case the correct button was pressed
# do something good
end
#beep here
#wait here
#whatever for the wrong condition
else # this is in case the correct button was pressed
# do something good
end
But won't that also trigger if no button is being pressed? At least, it does on all my tests.
Right you are, lemme see, I'll write you up a little snippet. It shouldn't take more than a few minutes.
QUOTE (Night5h4d3 @ Sep 13 2011, 08:39 AM) 
Right you are, lemme see, I'll write you up a little snippet. It shouldn't take more than a few minutes.
Hehe, thanks. Now you see my dilemma
you're telling me, it takes actually trying this out for me to remember how
notorious ruby is for disliking tertiary expressions. So here it is:
The way you use this is you call it like a normal input call, sort of:
And to boot, here's how you can do it with conditional branches:
notorious ruby is for disliking tertiary expressions. So here it is:
Night5h4d3's Any Input Script
The way you use this is you call it like a normal input call, sort of:
CODE
if Input.trigger_other?(Input::A) == true
# this is handling for incorrect input
elsif Input.trigger_other?(Input::A) == "noinput"
# put handling here to return up and check again
else
# this is handling for correct input
end
# this is handling for incorrect input
elsif Input.trigger_other?(Input::A) == "noinput"
# put handling here to return up and check again
else
# this is handling for correct input
end
And to boot, here's how you can do it with conditional branches:
I assume this wouldn't work for scripts that allow extended inputs?
Also I think you have some typos in your code, possibly here:
ANY = [Input::UP Input::DOWN, Input::LEFT, RIGHT, Input::A, Input::B,
Also I think you have some typos in your code, possibly here:
ANY = [Input::UP Input::DOWN, Input::LEFT, RIGHT, Input::A, Input::B,
Unfortunately not, it wouldn't be incompatible, it just wouldn't have handling for the other inputs. and whoops, fixed that. RIGHT was supposed to be Input::RIGHT.
Shouldn't Input::UP also be followed by a comma?
That's good that it is still compatible, unfortunate that it doesn't accept other inputs.
Why can't this be aliased into the Input.trigger method instead of creating a new method?
That's good that it is still compatible, unfortunate that it doesn't accept other inputs.
Why can't this be aliased into the Input.trigger method instead of creating a new method?
Looks like I missed that too, XD fixed it in the post.
And simply put, Input.trigger is a hidden def. If I alias it, I've 2 options, call the original before the extra code, or after, doing so before would nulify my code, as the def would have returned by then. and as for before, well, how would I detect if the button was 'triggered?' Because, the code for detecting a trigger is in the same def I have aliased.
The only way of overcoming this issue would be to:
A) Know the ruby code for the Input module
or
B) Create a new def that will call the trigger method separately on all possible inputs
Reverse engineering the RGSS dll is the only way to obtain the code for the input module, which is illegal; not to mention that it is written in C/C++, which is not ruby.
Hope that explains why I have to go with method B.
And simply put, Input.trigger is a hidden def. If I alias it, I've 2 options, call the original before the extra code, or after, doing so before would nulify my code, as the def would have returned by then. and as for before, well, how would I detect if the button was 'triggered?' Because, the code for detecting a trigger is in the same def I have aliased.
The only way of overcoming this issue would be to:
A) Know the ruby code for the Input module
or
B) Create a new def that will call the trigger method separately on all possible inputs
Reverse engineering the RGSS dll is the only way to obtain the code for the input module, which is illegal; not to mention that it is written in C/C++, which is not ruby.
Hope that explains why I have to go with method B.
Great :3 Thank you kindly.
I believe I understand why you do it in style B. Makes sense to me now.
I believe I understand why you do it in style B. Makes sense to me now.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.