Simple Keypad Events

Uploaded by Conan

The add-on board icon. Events
The add-on file name icon. Event_SimpleKeypad.zip
The add-on upload date icon. Mar 11th 2021, 5:35 PM
The add-on download count icon. 499

Description

A simple keypad event system to simplify making passcoded doors! Has VCE support to access and view the passkey, and can be used to create string patterns.

Events

fxDTSBrick > inputPassKey [string] - Appends the indicated string to the current stored input passkey on the designated brick (named brick or self)
fxDTSBrick > displayPassKey - Chats the current passkey to the client who triggered the event.
fxDTSBrick > clearPassKey - Clears the stored passkey on the indicated bricks.
fxDTSBrick > checkPassKey [passkey] [salt] - Checks the stored passkey against the passkey in the event. When changing the password, make sure the salt field is cleared so a salt to encode the passkey will be generated.
onPassKeyCorrect - Called if the passkey is correct when checkPassKey is called.
onPassKeyIncorrect - Called if the passkey is incorrect when checkPassKey is called.

#VCE To access the passkey with VCE, use <var:br:passkey> or <var:brick:passkey>. The BLID of the last person to edit the password (inputPassKey, clearPassKey) is also stored in <var:br:lastInputPassKey>.

Comments (3)

Queuenard
2021-03-17 06:17:00

Consider the risks of numeric-only passcodes... Average times it would take (on my CPU) to break passcodes: (numeric codes only) 6 digits < 1 second 7 digits 5 seconds 8 digits 35 seconds 9 digits 353 seconds Divide by 4 since I could even multithread this.

Conan
2021-03-18 20:59:08

@Queuenard: fortunately you can configure the event to work however you wish it to. There's no limit on the number of characters in the paramter box of fxDTSBrick>inputPassKey (although the passkey limit is 50 characters) Bruteforcing is also easily resolved by putting the brick with the check events outside of ghosting range - this just makes it not trivial to figure it out by saving the build. But I suppose given that scenario, an unsalted passcode check event would be fine as well.

Queuenard
2021-03-20 02:37:07

It is true that you can place a brick outside of ghosting range, but this isn't always feasible. Take, for example, a CityRPG. Also, be aware there is a bug that forces a client to ghost all bricks, but that's StreamShark levels of cheating. My comment was just a warning against short passcodes, especially numeric. Maybe consider not storing the salt in events. Check out: https://blocklandglass.com/addons/addon.php?id=1103

Back to the top