This is a read-only snapshot of the ComputerCraft forums, taken in April 2020.
sebbeviper's profile picture

[Lua][Error][String "lock"]:1: unexpected symbol

Started by sebbeviper, 06 July 2012 - 01:01 PM
sebbeviper #1
Posted 06 July 2012 - 03:01 PM
I can't seem to find the error in this code. :1: means row 1 right? copied this from the wiki so it should work.

local side = "left" -- Change left to whatever side your door / redstone is on, E.G: left, right, front, back, bottom, top. Be sure to leave the "s around it, though
local password = "bacon" -- Change bacon to what you want your password to be. Be sure to leave the "s around it, though
local opentime = 5 -- Change 5 to how long (in seconds) you want the redstone current to be on. Don't put "s around it, though
term.clear() -- Clears the screen
term.setCursorPos(1,1) -- Fixes the cursor position
write("Password: ") -- Prints 'Password: ' to the screen
local input = read("*") -- Makes the variable 'input' have the contents of what the user types in, the "*" part sensors out the password
if input == password then -- Checks if the user inputted the correct password
term.clear() -- Already explained up top
term.setCursorPos(1,1)
print("Password correct!") -- Prints 'Password correct!' to the screen
rs.setOutput(side,true) -- Output a redstone current to the side you specified
sleep(opentime) -- Wait the amount of seconds you specifed, then..
rs.setOutput(side,false) -- Stop outputting a redstone current
os.reboot() -- Reboot the computer, reopening the lock
else -- Checks if the user didn't input the correct password
term.clear()
term.setCursorPos(1,1)
print("Password incorrect!") -- Prints 'Password incorrect!' to the screen
sleep(2) -- Waits 2 seconds
os.reboot() -- Reboot the computer, reopening the lock
end
OmegaVest #2
Posted 06 July 2012 - 03:10 PM
Did you just copy-paste into a text document and then load your world? If you did, there seems to be a slight bug in doing so. Try typing it out, in game, in a separate program, see if it throws the same error.


Otherwise, there is nothing wrong with this code, but if you took the time to include the comments, you might take the time to take them out.