@Toteler - Read the scene description next time, open the MEMORY GEAR INPUT DOOR you MUST insert the MEMORY GEAR in the MEMORY GEAR INPUT DOOR and close it, then you click the red button. Use the ink containers to refuel. How do you forget the function of this scene?
@Little - Not really, there are some different assets and functions, and I didn't take Innovation Inc.'s assets and functions. At some point, I have not cloned Innovation Inc., and the title of the scene says "Blue Moon's Algodoo Facility 2". It was not inspired by Innovation Inc., correct me if I am wrong...
I discovered an issue, the elapsed time is not right and it ticks per 2 seconds to add 1 to the time second units and tens. When I put the simulation speed high, it won't change. It's absolutely weird with the time, please correct it. Thx!
The objects are cluttered up when I run the scene, you have NOT glued any of the objects which don't make sense, pretty good story BTW, but can you make your scene better by glueing the objects and making necessary objects and scripts? I rate 5/10, to be honest...
@MyNameIsThis - Already? There is so many people uploaded "Phun" thingys, what if they were abondoned there Algobox account? What if Algodoo Forum dies? Are they stopped working on Algodoo?
TEXTURE BUG: I encountered an unexpected moment when the texture in the scene was changed, it happens when you put a texture in the scene with the same name as a different old scene, in that scene, textures will be messed up. I have found an asset that has been changed to the following: OPERATIONAL & UNSTABLE screen asset. I will be updating the different scene that has the same name on this scene. When putting textures in the scene, make sure that the name is not "Untitled", or "Capture" or has the same name as the different scene, because this scene or another scene has occupied it. Thank you for understanding and HAPPY NEW YEAR!!
UPDATE: The bug has been resolved, you might need to reset the configuration after this, just to make sure that the texture doesn't have the same name as the different scene.
Last edited at 2023/01/28 10:12:45 by BlueMoon2607
@Little - This phunlet uses scene.algoboxID to check the plagiarism, this variable is stored on your published scene with numbers on representing the Scene ID. You don't have to read the instructions all over again when you create and share your scene, if you knew the instructions, you can do it quickly and that will not make you more frustrating. I hope that helps!
@Xray - I'm sorry for your unsatisfaction, you said this phunlet was "useless" for a specific reason, I am a little bit good at coding on Algodoo but I cannot do anything about it, I clearly don't know how to close windows and stop editing indefinitely using scripts but I can use the app.mousePos and pos to make it "disappear". This phunlet was made for the original scene, not the copied scene. You said that it was hard to determine who is actually the original author, but there is a date and time for when the scene gets published, it might be the solution to your problems. Once you see the person who copied the original, you check the date and time for when it gets published, if the copied scene was published later than the original scene, then you ban the copied scene. Another way to the solution is the Scene IDs, you check the URL of the scene, and if the copied scene has an ID number greater than the original scene's ID number, then you also ban the copied scene. I tried my best, OK?
Last edited at 2023/04/15 17:42:57 by BlueMoon2607
@s_noonan - It is technically unclear how the scene cannot be loaded.
@rjoseph - scene.algoboxID has some quotes (it is required), anyways if the _algoboxID is the same as the scene.algoboxID, it will mark as OK, otherwise it will trigger a warning message by using app.gui.showMessage with a _triggerMessage text.
Last edited at 2023/07/29 08:40:01 by BlueMoon2607