"Restrict actions" is BROKEN!

[Pkeod]

I've not been successful in making an example showing that restrict actions does seem to break, but I know that it does, and a few people have confirmed that it does seem to break over time too. I am aware of the work around, but that still doesn't solve the problem of the "Restrict actions" condition breaking over time.

Here is my observation: If a game is left open for a long period of time, left alone, or not in focus, then any event that uses a "Restrict actions" condition breaks and pretty much because "Always." I've seen this happen in four different projects, and it's annoying to have to go through a ton of code to put the work around in long after I realize there is a problem with using "Restrict actions." Frankly, having this broken condition even available to me has cost me too many hours in lost productivity :eek:

[Kimera]

I have never been able to get the restrict action function working but I thought it was me. I have not spent much time with it.

K

[Random]

I always found "restrict actions" the cure to the problems you get with "every". But maybe it indeed broke in one of the later versions.

[Brandon]

It works fine for me in a very simple example. Make a counter and then:

+Restrict Actions for 01"-00 (1 second)
-Add 1 to Counter

I'm using the most recent build and it counts up 1 every second. I tried it without focus and it still worked fine as well. How long is yours open before it starts malfunctioning?

[DavidN]

I do remember something like this being mentioned - by Nifflas, I think, as the structure of the game Knytt meant that it stayed on the same frame for upwards of half an hour. I can't remember the exact figure, but it's possible it happened after 65536 frames, though that works out to about 20 minutes at 50 frames per second and seems rather low.

However, I thought it had been fixed in the build after it was first reported.

[Brandon]

I do remember something like this being mentioned - by Nifflas, I think, as the structure of the game Knytt meant that it stayed on the same frame for upwards of half an hour. I can't remember the exact figure, but it's possible it happened after 63356 frames, though that works out to about 20 minutes at 50 frames per second and seems rather low.

However, I thought it had been fixed in the build after it was first reported.

I think it may have been fixed because I did the same test as in my previous post, except with a frame rate of 300. I let it run for 300 seconds (approximately 90,000 frames) and it worked the entire time. And also, it was a near solid 300 frames the whole time.

[Pkeod]

I'm on build 248 and it just happened again to me. Unfortunately the project is too big for me to send to Clickteam; however, the event is as simple as this:

* Restrict actions every 5 seconds:
Create Object at X,Y

Leave the game on for a while, and I'll come back to objects being created as if the event was an always event.

[Werbad]

Ran it for 10 minutes at 500 framerate and it never bugged...

[Pkeod]

It has caused problems with my projects many times, and I know for a fact that others have had it not work as they expected. Perhaps you cannot just blind test the one event and need to actually have it inside of a project which is doing many things. Maybe the problem is more complex and the condition isn't actually broken, but the fact for is that it has broke for me. It's broken for other people too. I'm just asking Clickteam to look into it.

[Bornemix]

What happens if you try it using the Java runtime?