"Buildism warning: This game is using an unsupported scripting technique..."

[Duck]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

[Jacob__mybb_import1]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

[Duck]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

How are we meant to make things with delays if we can't use sleep?

[noob007]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

How are we meant to make things with delays if we can't use sleep?

Notice "in an event handler".

[Duck]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

How are we meant to make things with delays if we can't use sleep?

Notice "in an event handler".

"How am I meant to put a ten second delay in my function if I can't use sleep?" Happy?

[noob007]

"...That will soon be removed, please notify the creator that <Text is cut off by in game window size>"

Which scripting technique is this referring to?

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

How are we meant to make things with delays if we can't use sleep?

Notice "in an event handler".

"How am I meant to put a ten second delay in my function if I can't use sleep?" Happy?

If said function is an event handler (callback), then use something like gamecheduleTask()

[Jacob__mybb_import1]

Using sleep() for a period of time longer than 0.5 seconds in an event handler. It will give you a more detailed message in edit mode (if it's your game, of course.)

How are we meant to make things with delays if we can't use sleep?

Notice "in an event handler".

"How am I meant to put a ten second delay in my function if I can't use sleep?" Happy?

If said function is an event handler (callback), then use something like gamecheduleTask()

The preferred way is by using os.time(). It avoids the requirement of an extra thread.

[lua]
delay = 3 --3 seconds

lastCalled = os.time()
function doSomething()
if os.time() - lastCalled < delay then return end
--do stuff
lastCalled = os.time()
end
[/lua]

[noob007]

^ or that

[Duck]

How are we meant to make things with delays if we can't use sleep?

Notice "in an event handler".

"How am I meant to put a ten second delay in my function if I can't use sleep?" Happy?

If said function is an event handler (callback), then use something like gamecheduleTask()

The preferred way is by using os.time(). It avoids the requirement of an extra thread.

[lua]
delay = 3 --3 seconds

lastCalled = os.time()
function doSomething()
if os.time() - lastCalled < delay then return end
--do stuff
lastCalled = os.time()
end
[/lua]

But doesn't that mean people could cheat / break a game by messing about with their clock

[Jacob__mybb_import1]

Notice "in an event handler".

"How am I meant to put a ten second delay in my function if I can't use sleep?" Happy?

If said function is an event handler (callback), then use something like gamecheduleTask()

The preferred way is by using os.time(). It avoids the requirement of an extra thread.

[lua]
delay = 3 --3 seconds

lastCalled = os.time()
function doSomething()
if os.time() - lastCalled < delay then return end
--do stuff
lastCalled = os.time()
end
[/lua]

But doesn't that mean people could cheat / break a game by messing about with their clock

If they do then I'll just add some code that kicks them out if time goes backwards or unusually fast.