This is the script I run when a player types 'use epad'
msg ("{command:log off:Log off}")
play sound ("epad_beep.mp3", false, false)
TextFX_Typewriter ("System booting", 5)
SetTimeout (2) {
TextFX_Typewriter ("Command parametre enabled", 5)
SetTimeout (2) {
TextFX_Typewriter ("Memory check", 5)
SetTimeout (2) {
TextFX_Typewriter (".System", 5)
SetTimeout (1) {
TextFX_Typewriter ("User ID", 5)
get input {
if (result="test" or result="Test") {
ClearScreen
TextFX_Typewriter ("Logging in. Please wait.<br/>", 1)
SetTimeout (3) {
TextFX_Typewriter ("Pear ePad4 | User ID: Lance Matthews | Session log: 2334#4", 5)
SetTimeout (3) {
msg ("{command:log off:Log off}<br/><br/>{command:contacts:Contacts}")
}
}
}
else if (result="log off") {
TextFX_Typewriter ("Logging off. Please wait.", 1)
SetTimeout (2) {
msg ("<br/>Logged off.<br/>")
}
SetTimeout (3) {
ShowRoomDescription
}
}
else {
TextFX_Typewriter ("Error. Incorrect User ID", 1)
SetTimeout (3) {
msg ("<br/>")
do (EpadCommand, "script")
}
}
}
}
}
}
}
This handles an incorrect and correct password the way it should, and also the 'Log off' link, but when play testing just now I discovered that if a player types a command (not knowing that the 'Log off' link (top of script) is how they return to the game, that link is then killed and the player may be left wondering what to do. It just so happens that an input (after successfully 'logging in') returns the player to the game (allowing any available exits and normal commands as usual) but I don't think it's clear enough.
I need some rule that throws up a computer type error (such as 'Input error. Please click 'Log off' to end the session') if the player tries to type anything once they have logged into the system.
Failing that, or maybe better still, can I remove the option to input once the player has logged in to the game's device?