Algodoo

I did not know phunlets could see the scene ID!
I once almost made something similar to this with an AI car scene of mine, where the cars would just sit in place and do nothing if they were in a shared scene other than the AI Cars scene. However, I didnt know you could pull a scene's ID from an object, plus I planned to share multiple scenes with them and that would have been really frustrating.

@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!

@rjpseph - Do you really use this comment section like that?

It has FNF Inside

and towers

This "Scene Plagiarism Checker" is actually useless for three reasons.
1. Scenes and parts of scenes get copied and uploaded to Algobox nearly every day. And because of that, it's impossible to determine who the original maker of a particular scene was. With this Plagiarism Checker, a person can copy someone else's scene, install the checker, and basically brand the scene as their own.
2. It's too complicated to use for the average 10 year old marble race kid who has no idea what a Phunlet is or how to use it.
3. Anyone who knows Thyme Scripting can easily defeat the Plagiarism Checker after downloading the protected scene and then modifying it.

Bottom line, it's more trouble than it's worth.

@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?

@BlueMoon2607 -- I apologize if my prior comment was a little blunt or insulting. Please be assured that it wasn't my intention. I have been dealing with scene plagiarism since I became the Algobox admin back in 2014. It's a real problem but I have reached the sad conclusion that it's unenforceable. I even posted a couple of copy-protection scenes which I originally thought were great, but soon realized how useless they actually are. If you click on my username, you will find them in my list of scenes.

Even though the Algobox rules state that scenes should not be copied and uploaded by someone other than the original maker, I no longer enforce that rule because I cannot spend hours of my time attempting to track down who the original author of a particular scene was. Lord knows I have better ways to spend my time! Another problem is the fact that sometimes only parts of a scene get copied and reused. How can that be enforced? It cannot! So, the bottom line is, I ask people to please do not copy other people's work without permission. If they do plagiarize scenes and make a habit of it, they will get a bad reputation with the Algobox community which no one wants.

You are obviously talented with Thyme scripting, and I hope to see what awesome scenes you'll come up with in the future!

@Xray - Thank you

I like the scene idea. Algobox has been around for 14 years and this is the first scene that tries to prevent plagiarism by using algoboxID. Correct me if I'm wrong, but this scene assumes that scene.algoboxID gets updated when a scene is posted to Algobox. I'm not sure that's the case. My Rotate 3D Cube,which I copied from Xray, has scene.algoboxID = 48330, which is 3D Box by RBS16.

Here's a couple of ideas that could be implemented by Algobox (but don't hold your breath):
1. Highlight all scenes where scene.algoboxID does not match the Algobox ID. This would highlight possible plagiarisms.
2. Set up a web page where a user can delete possible plagiarisms of their work by being able to delete any scene that has scene.algoboxID = their original Algobox ID.
3. Set up a web page where a user can see possible plagiarisms of their work an request that specific scenes be deleted.

P.S. Modified Rotate 3D Cube so that its Scene.algoboxID = 259159, so it doesn't "appear" that I am a plagiarizer.

@BlueMoon2607 and s_noonan -- Both of you have great ideas to prevent plagiarism here on Algobox and I agree with s_noonan that the best way to handle it would be to modify Algodoo and Algobox which only Algoryx can do. They are able to add new features to Algodoo and to Algobox which I have no doubt would resolve this issue. My contact at Algoryx is currently on personal leave from the company, but I will bring this issue to his attention as soon as he is able to deal with it. Just keep in mind that Algodoo is a low priority for the company because it no longer makes a profit, and they are spending nearly all of their resources on developing and supporting new products.

Thanks

This scene was uploaded to Algobox as a phunlet. The scene description starts with "This phunlet ...", so I should have known. If you already have a different scene open, and you download this scene, then the phunlet automatically gets inserted into the original scene. If your original scene has a camera position where this phunlet is not seen, and you don't realize that this scene is a phunlet, then it appears that Algobox has failed to load this scene.

how did you done this

@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.

I stated "it appears that Algobox has failed to load this scene.". The phunlet loads, but a user may not realize it.

@s_noonan - Oh, ok.

what happens if i plagiarize the plagiarism checker

@a_bored_coder - Nothing happens to the checker, but be sure to credit me, or it is against Algobox's Rules.

Opening this "scene" will insert the Plagiarism Checker phunlet into your presently open scene or into your last created scene. I suspect that 99.9% of users who downloaded this scene don't know that.

@Xray, you may be right about my phunlet being 'useless' on the 7th comment of the scene (or you call it phunlet). Although not many people know how to actually modify it, I found the way to modify it (I ain't telling you for the sake of the integrity of Algobox and Algodoo).

However, it isn't useless if many people do not know how to game the system. I would like to keep it for historical purposes anyways.

Cheers!

Please name one of your scenes that use this phunlet. I expect that you would use this phunlet on all your scenes going forward.

If you are confident in your plagiarism phunlet, you could make a scene named "Plagiarize This Scene" and users could try to add plagiarisms of your scene as responses.