erich - Thanks for your comments. It's not very often that users who receive a warning actually apologize for their actions. I really appreciate that, and you did it in a comment which is seen by the public.
Concerning "art" scenes, yes I am aware of the situation. It is sometimes very difficult to determine which scenes will be deleted and which will be allowed to stay. No, I do not have an easy job, and because of it, I am not always liked or appreciated.
Yes, link007 was one of the first Admins, and he actually developed much of the software that makes Algobox work! As far as I know, he is no longer active on ALgobox or the Algodoo forum, and I do not know why.
Yes, I did notice that. But when I first played the scene, it did work in ascending order (1 - 2- 3), and so I assumed that it should also work in descending order without pressing Reset.
If it works like you intended it to work, then it needs no changes.
Life in general isn't fair, and so you just have to deal with it. Being an Admin is very similar to being a Police Officer in a city. Without the police, there would be chaos and anarchy. Most people appreciate what the Police do, and of course, some people (mainly the criminals) hate them. That's life I guess. I enjoy making scenes with Algodoo very much, and Algobox is a great place to show off those creations. That's why I do what I do. I believe that it's worth keeping active and keeping it working in an orderly manner. This job as Admin is not for everyone. I don't get paid, and it takes a lot of my time. But that's Okay.
Okay. Unfortunately, it's very laggy because of the laser cutter. Whenever a laser cutter is used to make repetitive cuts (such as when shaving off the edges of an object to make it circular) it requires very fast, complex calculations which makes the scene laggy. That can often be remedied by reducing the rate of cuts over time, and there are a number of ways to do that.
Only a couple? I believe that I know thyme scripting very well, but there are many things about it that I still would like to learn. The important thing is, I understand enough about it so that I could make just about any scene that I want to make with it. So, if you know, say 75 percent, of Thyme scripting, then you will be able to make nearly 100 percent of the scenes that you want to make. The last 25 percent will not keep you from making any type of movement or action in your scenes, but they will help to make them more efficient if you wanted to learn them and use them.
This not a tutorial. It is only an example of what can be done with Thyme script. It would be good if you could make it into a tutorial by showing the actual script and explain how the script works, and how a new user could make it all happen, from the very beginning to the finished product.
Since you are fairly new here on Algobox, I have a suggestion for you. Whenever you make a scene that uses the keyboard or the mouse to control things in the scene, it's always a good idea to explain what those controls are and how they work. Without the explanation, people have to fumble around trying to figure out what keys do what.
If you wanted to, you could edit this scene and explain the control keys (up arrow and down arrow) either in the scene or in the description. People don't always read the comments, and so it's best to put them in the scene.
Bye the way, Luka is right about the voting. That sort of practice is normally done in the forum, not here on Algobox. Algobox is only for displaying action type scenes (marble races included), but is not for user-to-user interactions, such as voting.
Suggestion: Explain what keys to press whenever you upload a scene that requires user input. When you do not provide that information, then people have to fumble around trying to figure out what keys to press or what mouse button to click in order to make the scene function. You can put the explanation in the scene description, or directly in the scene. It's best to put it in the scene because not everyone sees or reads the scene description.
It self destructs because the green columns and the green overhead beam have a "timeToLive" value of 5.000 seconds. If you change the three timeToLive values to +inf then they will never disappear.