Help Creating a Number Pad (Updated)

[kood99]

I was wondering how I could create a number pad that a player could enter a number password into in order to open a door.

EDIT:
New problem! I'm not sure if I'm doing this correctly since the game won't let the player input anything when the event is interacted with. Nothing happens.

 

[SmashArtist]

There actually is a function to have number passwords by default in MV, it's under "Message" in event commands page 1 called "Input Number". The number the player inputs is kept in the chosen variable, which you can then check with a conditional branch. Make sure to set the variable to 0 before you bring up the input number command if you want to have the pad reset every time.
Unfortunately it doesn't visually look like a number pad, if that was what you're looking for you might need to search for a plugin.

 

[kood99]

There actually is a function to have number passwords by default in MV, it's under "Message" in event commands page 1 called "Input Number". The number the player inputs is kept in the chosen variable, which you can then check with a conditional branch. Make sure to set the variable to 0 before you bring up the input number command if you want to have the pad reset every time.
Unfortunately it doesn't visually look like a number pad, if that was what you're looking for you might need to search for a plugin.

Oh! That's how that works! I was a bit scared to mess with it.

 

[SmashArtist]

Happy to hear I helped, though I noticed your edit on your main post. My guess is that the second page of your event has no conditions(or the condition that is there is being met) and therefore, is prioritized above the first page. (In general higher numbered event pages are prioritized, so they will be run if there are no conditions against them)
Edit:
You need to put a conditional branch after your input number command. Have that branch check if the variable is equal to your passcode if so, turn on self switch A. Then have the second page's condition be set to self switch A.
If you'd like some screenshot examples I'd be happy to show you some.

 

[kood99]

Happy to hear I helped, though I noticed your edit on your main post. My guess is that the second page of your event has no conditions(or the condition that is there is being met) and therefore, is prioritized above the first page. (In general higher numbered event pages are prioritized, so they will be run if there are no conditions against them)
Edit:
You need to put a conditional branch after your input number command. Have that branch check if the variable is equal to your passcode if so, turn on self switch A. Then have the second page's condition be set to self switch A.
If you'd like some screenshot examples I'd be happy to show you some.

No, It's alright! I solved my second problem.

 

[Kes]

[closed]IgnoreMe[/closed]