Ramadhani -- Don't worry. You will not get banned if your scenes don't work properly!
Concerning your issue, it would be better for me to determine why your scene is glitching if I was able to look at the actual scene. Without the actual scene, I can only guess about what might be happening.
Based on your description, it seems to me that you have two objects overlapping each other that have the same collision layer enabled. Algodoo does not like when two objects occupy the same space, even if by a small amount. It's like in real life if two people attempt to stand in the same place, it is impossible and they will try to push each other away!
If this information does not help you fix the problem, then I would ask you to go ahead and upload your scene that is glitching and I will take a look at it to see if I can determine what causes the glitch.
For example: Personal messages are not allowed in the scene, the scene title, or the scene description. Personal messages ARE allowed in the comments. A personal message, for example would be: "Hey guys, I'm back!" or "My mom just bought me a new computer!", etc.
Yeah, I realize that some of the rules are ambiguous, but I think anyone who can read and has common sense should understand them. Of course there are some users who do not read and write English, so they would need to use Google Translate or similar app, or have someone else translate the rules to their native language. Again, people should have common sense that it's not Okay to cuss, and it's not Okay to threaten another person, etc.
Thanks for your question because other people might learn from our little chat!
a_bored_coder -- Why don't you simply edit the scene description instead of making corrections in the comments? You do that by clicking on "Edit", then make whatever changes you want to the title or the description, then upload it. You do not need to enter the filename unless you made changes to the actual Algodoo scene file.
Wait, I see you did that already! Now we can delete these comments because they no longer apply!
Ramadhani -- It took me a while to figure out what is causing the train to stop as if it hit a wall. Well, the culprit is not a wall, but is a very tiny (almost invisible) object located at [15.916721, 6.8467669] which is located to the left of and just below your text "is confused me". Here is how you can delete that thing. If you select that entire area (I used the Move tool) and then press your delete key, it should become deleted. Try that and see if it fixes your problem.
While checking out the recent slide rule scene, this scene popped up in the list of similar scenes and so I decided to play around with it. While playing with it I discovered a minor issue that I missed back in 2013. That is, if I happened to click on the outer scale, it of course gets selected and then I am unable to drag the inner moveable scale. To prevent that from happening again, it can be fixed with the usual app.gui.playMode = sim.running script.
I'm glad you like it! I've had it in my stash of Algodoo assets, and I don't recall where I got it from. I probably stole it..... ummmm.... I mean borrowed it from someone else many years ago!
I found four other slide rule scenes on Algobox by searching for "slide rule" (include the quotes). You may want to see them if you are interested in how other people have created their slide rule scenes.
No problem! People from around the world use Algobox and so I'm accustomed to people responding from many different time zones that are often many hours apart.
By the way, I'm in Minnesota, so you are only 1 hour later than I am.
MuzStruzhka -- In a properly designed Algodoo scene, there should never be an object overlapping other objects that have the same collision layers activated. In real life, that would be like three people occupying the same space at the same time. It just can't happen! People have uploaded scenes that simulate explosions by utilizing that situation where many objects are crammed together with the same collision layer, and then when the scene runs, those objects fly apart at very high velocities. Normally, objects of the same collision layer stay apart until one of them collides with another one. That then would be detected as a collision between those two objects and your script determines what to do next.
I did play around with this scene that you were questioning and I was not able to determine what or why one object would detect a collision and others would not. It just seems to be a critical or random timing issue.
You can make the scene a little more interesting by sticking a tracer on the ball! Just right-click the ball, then hover down to "Geometry actions". When the next pane opens, left click on "Attach tracer". Then run the scene and you will see the actual trajectory of the ball! Make the tracer whatever color you want to.