Hi Fruitmonger - Thanks for the feedback! I thought of that when I was designing the game, but I decided to do it the way it currently is because it makes it a little more challenging, and the dictionary only has 15 words in it. So, I didn't want to make it too easy to beat.
If you change the collision layer from A to B on that center rod, then the assembly won't be shakey like it is now. You also need to add collision layer B to those center guides that support the center rod.
You can EDIT a bad scene rather than start a new one. But if you do start a new scene that has been fixed, then be sure to delete the old one. I will delete your old one for you this time.
Didn't you read my last comment? You should EDIT your defective scenes rather than create new ones. But if you do create new ones, be sure to DELETE the old ones! That way the Algodoo server won't get cluttered up with junk.
lucnan - Please post your technical questions in the Algodoo forum. It's really not a good idea to try to explain a lot of details in these comment sections. And when you post questions in the forum, you will get a much wider range of people responding who could help you.
Yes, I'm showing it again for new users who may have missed it before. I'll probably update it and show it again every few weeks so that it doesn't get buried and forgotten about. Unfortunately, Algobox does not have "stickies" like the forum does.
The scene works well, but many people complain when scenes use the Numpad for control because laptops do not have a Numpad. Just something to consider for future scenes.
The large block will look better if you erase the black "cut" lines. You do that by selecting the entire block (drag a selection rectangle around it with the Move Tool), then right-click and move cursor to "appearance". When the appearance menu pops up, uncheck the check box "draw borders". When you remove selection (just left click on background) you will see that the black lines no longer show.
While looking at my code for errors, I realized that when I copied and mirrored the upper row of sequencing circles (to make the bottom row) I also copied the sequencer script, which is located in the rightmost circle of the upper row. That, of course, was causing a conflict between the two rows. I deleted the sequencer code in the bottom row (leftmost circle), and now the sequence is much smoother. Thanks for making me look at my code again!