If you want you could contact me on skype I got a nice idea for the checkmate recognition.

If it's already in a loop just do

while rs.getInput("side") do

Edit: In your case.

repeat
until not rs.getInput("side")

bin3, on 27 December 2012 - 12:51 PM, said:

You have to see, what you posted was very basic and if everyone who wrote a script like that for the first time would post it here the forums would be flooded. I'm sure you are very excited about coding and writing an awesome login script, but it's very basic and not worth a forum thread.

PixelToast, on 27 December 2012 - 11:14 AM, said:

It is on an English forum. I speak German, I know the language itself is not wrong but on here, it is.
And that makes it useless, I look at this section to see other people's cool work, but anyone who knows how to code can write a more helpful script in 30 seconds, so the only people who would learn anything from seeing it would be people who don't know how to code, and if they don't know how to code, what are they doing on here?

Lol, I just realized it still had a few copy & pasted elseif 's in it, they don't affect the code though so whatever, lol

Wrong language and this is basically the definition of a useless thread.

Some of you may know that on my server I restrict ComputerCraft to only my OS so to keep people from using malicious code.
Unfortunately this keeps people who like to use computers for their farms or doors from using them.
So I had an idea, I could let people access the "redstone side" of computercraft, and this is how:

Redscript

So what does it do?

Redscript is a scripting language I made which uses VERY simple commands to execute basic redstone operations and a bit more.
You can toggle redstone signals, wait for inputs, go to different lines ( for loops, etc )
and soon you will be able to compare text to user input ( good for password doors )

Here it is:
http://pastebin.com/YBJxRbSt


How to write scripts:

Basic functions are
SIDE on/off
wait #
wait SIDE
goto #
compare a b ( soon )


There you go, always happy about input and suggestions.

The last code I posted work 100% fine, this mean you must have misspelled something when copying it, based on the error you gave me, you must have misstyped the variable name of either TimeOn or TimeOff.

Why all the "do" 's ?

Well, the code is fine so you must have misspelled something.
Make sure you capitalize the variables the same way every time. That is most likely the issue,

crackroach, on 13 November 2012 - 08:53 AM, said:

Have you tried it like this?

TimeOn = 18.00
TimeOff = 6.00

while true do
	if os.time() >= TimeOn or os.time() < TimeOff then
		rs.setOutput("bottom", true)
	elseif os.time() >= TimeOff and os.time() < TimeOn then
		rs.setOutput("bottom", false)
	end
	sleep(1.0)
end

It should work, if not, please tell me the error.

You have 2 options to get information about a block.

a.) You get a peripheral which lets you get more information about blocks, there is many that output the block ID.
b.) You can use turtle.compare() to compare the item in front of the turtle ( or compareUp / compareDown ) with the current selected slots. Now with this you would have to have the block in question in the turtles selected slot and then you can use compare to determine if the block in front of the turtle is said block.

I do realize that Lock1 and 2 were set but in the piece of code you posted it was neither of them it was just Lock.
So even though you set Lock1 and Lock2, you are still comparing Lock ( which is nil )

If that is the exact code then the other turtles never send anything because of this line.

while Lock==0 do

Because Lock is nil , you only got Lock1, and Lock2. If this is not the exact code then please give us the exact code because we can't look for errors in a poor copy of the code.

Also, tip for the future, instead of color-coding everything you can simply use the code tags, makes everything easier to read.

It should work just fine.

PixelToast, on 10 November 2012 - 02:28 PM, said:

Well what were you referring to with this?

PixelToast, on 10 November 2012 - 12:32 PM, said:

Human, on 10 November 2012 - 12:55 PM, said:

No idea what you mean.

Human, on 10 November 2012 - 12:55 PM, said:

No idea what you mean.

PixelToast, on 10 November 2012 - 12:32 PM, said:

??

MechaTallon, on 10 November 2012 - 12:27 PM, said:

?

Also, FYI, the loginserver now logs all PCID's which should help in case someone does make a script because I can simply look for these for the script in question.

Human, on 10 November 2012 - 09:47 AM, said:

You are again completely disregarding my statement about your logic being flawed because it is simply not possible to fix all bugs, Also, if you exit out of the other scripts you simply return to XoXOS, the script it was loaded from.

Human, on 09 November 2012 - 10:43 PM, said:

Your entire argument so far is that it could be done simply with bug-fixing but your logic is flawed because it is based on your believe that it is possible to fix all bugs. I bet you that if you set up a server with whatever bugs fixed etc, I would still find a way to crash it with computercraft.
Also, it seems as if you think that as soon as someone says "I know Lua" they get dev access on my server. No, if I see someone has played for a few days and built a house and town, etc that's when they even become eligible, because if they are actually willing to waste all that time just to crash the server once and then get banned then sure, go ahead.
No matter how good your bug fixing is, if there is even a single bug left that can be exploited then ANYONE can join and crash your server without any effort.
With this there can 10000 bugs that could crash the server but no one can abuse them because the time they would have to spend on the server to get access to computercraft just isn't worth it, and the people who are actually interested in staying can play normally and eventually ask for access.

As for what you said about my code.
The main XoXOS file is tabbed fine now, the others aren't because I wrote them ingame most likely.
As for comments, as I don't plan to show this code to anyone who plans to learn from it I don't comment, no need to comment if I'm the only one reading it.
And don't just say "Could be done better" without suggesting even a single thing I could improve.

Updated to V1.2 ,
Major changes
- Added DevNet . Chat for Devs
- Added version for turtles, lets users use excavate and tunnel..
Minor changes:
- Added Pastebin support into the UI
- Maybe some bugfixes if I found any, dont remember.

Oh sorry, I didn't notice I messed that up in the instructions. I'm going to update this very soon, I think this time I will upload the collection of files in a .rar

I never said anything bad about afterlifelochie and I'm sure he did a great job coding his BIOS file, my point is that as long as all users have access to run any lua script there is always a possibility that they find an exploit.