@rjoseph - It doesn't look like a difficulty level, difficulty levels can have different designs like meters or bars, so this scene is an HP bar. This is 2 years ago and I joined Algobox in Nov 2023 without knowledge of thyme script and I made it on Dec 2023. I suggest you should not comment negatively like this and not continue the conversation, because I tried my best.
Last edited at 2023/08/06 19:04:23 by BlueMoon2607
@rjoseph - I'm sorry you didn't enjoy my scene, it is best to read the rest of the text including the scene for instructions, to build a code, clone the blocks and place it in the workspace from the left line to right, if the line is full, then go another line from left to right. If you highly doubt it, then you may check my other scenes instead.
@Djcoolguy_90 - Very good question, I created this scene with thyme script. I can insert a script into a block, if the block is a P"", that mean the prompt block and if is activated, app.gui.showMessage() will run.
@VikingOMG - (Every) variable name starts with _ so it doesn't turn undefined when saving and then reloading the scene. If you tried to copy the whole scene into your new scene, then the variables go undefined, because your new scene doesn't have some variables declared and these variables are in this scene. (not your scene)
Last edited at 2023/08/07 07:05:07 by BlueMoon2607
@rjoseph - That's correct, you need to name your texture and never leave the name like "Untitled.png" because the textures can be downloaded when you download the scene on Algobox, but if you have an existing texture downloaded, it can be overwritten if the scene has a texture that has a same name.
@artemvideoalgodoo - You need to pay attention to the little squares that get spun by marbles, overtime the squares may turn into a rainbow, if the square turns rainbow, click on it before it's too late. Frenzy can live up to 60 seconds.
@Xray - I know, but you just add the _ next to the variable, I ain't asking him to put _ at the left side of the "scene.my", so basically for a global variable, you declare the variable like this: scene.my._globalVar; and the local variable like this: _localVar; I hope that helps!
The physics was different than the first-time played scene when the scene was possibly played again. If you do not show us the video of the Algodecathlon, then people click "Download", run the scene, and get the winner and you add a comment about the information when you run a scene in the first place, after that, there will be people complaining that there is a different winner, which is a problem for Algodecathlon. Maybe the solution is to upload the video and post the scene to Algobox for people to try the scene itself, but the physics varies and there will also be a different winner.
To be honest, your scene is good and well-built, I appreciate the way you built and I think you should keep going, also listen to your communities' responses and help each other.
Kind regards,
BlueMoon2607
Last edited at 2023/09/26 21:44:38 by BlueMoon2607
BUG: I noticed that the marble counter said undefined, you defined the text as 'my.scene.marbles', you need to switch the 'my' and the 'scene' otherwise it will say undefined (it should look like this: 'scene.my.marbles'). You also didn't add _ next to the 'marbles', making it temperately, causing variables to be undefined when the scene is saved and then loaded/downloaded. Contact the thyme-script professors (e.g. Xray) to learn more about it.
Last edited at 2023/09/26 21:55:17 by BlueMoon2607
I am learning from the start of this, this is my first scene uploaded in about November 2021. My account was ~3-4 years old when I posted this comment. Now I'm an advanced Algodoo author (maybe) and I'm capable of making a decently quality scene. Hope you enjoy it!