how to print something on a monitor then go down a line?

i need to know if there is way that i can write something on a monitor the go down a line so here is the code i am working with

mon = peripheral.wrap("right")
rednet.open("left") --open to the internet
pass="test"
function listen()
while true do
ID, message = rednet.receive()
if ID == 12 then
if message == pass then
rednet.send(12, "Accepted")
mon.print("--------------------------------------------------")
mon.print(ID..": entered correct password")
mon.print("--------------------------------------------------")
else
rednet.send(12, "Wrong")
mon.write("--------------------------------------------------")
mon.write(ID..": entered wrong password"..message)
mon.write("--------------------------------------------------")
end
end
end
end
listen()

the problem is it doesn't move down a line

There's no built-in function for this purpose. However, you could create your own one which writes the passed text, then checks where the cursor currently is (with mon.getCursorPos()) and then moves it to the start of the next line down (with mon.setCursorPos()).

Here's a good sample code:

function lineBreak() --Declare function
local x, y = term.getCursorPos() --x, y is cursor position
term.setCursorPos(1, y+1) --Set the cursor's position to y position + 1 (enter key basically) and x to 1 (start of line)
end --end function

And why are you using mon.print() first but mon.write() later?

Death, on 18 December 2013 - 08:02 AM said:

Here's a good sample code:

function lineBreak() --Declare function
local x, y = term.getCursorPos() --x, y is cursor position
term.setCursorPos(1, y+1) --Set the cursor's position to y position + 1 (enter key basically) and x to 1 (start of line)
end --end function

And why are you using mon.print() first but mon.write() later?

Lol that was me testing the scruple code dosent have that… But. Thanks for your help

Then don't say it's the code you're working with when it isn't. We need the actual code to help in most situations.

Lyqyd, on 18 December 2013 - 12:35 PM said:

Then don't say it's the code you're working with when it isn't. We need the actual code to help in most situations.

I see your point… It was a mistake I made I forgot to change it back after testing and didn't catch it