Algobox - Copy-Protect Your Scenes!

Browse

Popular

Upload

Rules

User list

Search:

Copy-Protect Your Scenes!

Image:

Author: Xray

Group: Default

Filesize: 0.66 MB

Date added: 2014-09-07

Rating: 5.6

Downloads: 2008

Comments: 19

Ratings: 2

Times favored: 0

Made with: Algodoo v2.1.0

Tags:

Every now and then I get reports of scene stealing, or parts of scenes being stolen (for example, "This guy stole my car!"). So, I have developed two methods that will help to bust the bad-guys who steal scenes or parts of scenes by uploading them as if the scenes were theirs.

One method (explained in the left panel in this scene) forces the user name of your scene to be YOUR name no matter what name someone else uses to save it.

The other method (explained in the right panel in this scene) saves a hidden text message in your scenes. Whenever another user tries to save and then upload your scene with a different user name, a message will pop up after 30 seconds which says that the scene was stolen from "Your Name"!

Both of these methods are only effective if the thief doesn't know Thyme scripting, because they can be easily defeated if they do.

Let me know in the comments if you have any questions or suggestions about these methods.

Please log in to rate this scene

Similar scenes

Protect the fort!

TheBest14Ever

Rating:

Our turrets Protect earth

Lester12345

Rating:

Guess the Weapon!

Strv-7

Rating:

Simple Ceiling ....ble scenes! v.2

FenX2012

Rating:

Jet Engine

Xray

Rating:

Panel Meter (configurable)

Xray

Rating:

faytree

2014/09/07 01:43:06

Good,Idea! now i want to try it on my new scene!

Xray

2014/09/07 02:21:43

I hope it works for everyone who uses it!

Thanks, faytree!

s_noonan

2014/09/07 08:10:17

Interesting. This brings up some other ideas:

1. Change the Name or Title to "I'm a jerk who stole this from Xray".
2. Automatically quit the application if author doesn't match.
3. Spawn the textbox that says "This scene was stolen from Xray" from another location.
4. Delete every nth object if author doesn't match.
5. For other users: Make an incredibly lame scene and put the "This scene was stolen from Xray" box in it.

lololoer

2014/09/07 17:07:45

Xray I think that it is possible to make the script to be invencible, first you put that script in update event and do the same in controllerAcc, eg ({script};11.0) then you put an if statment for asking update event to be euqal to the script message and a current script asking for controller acc for script and currwnt update event I hope you understood the method

Xray

2014/09/07 17:37:07

Thanks guys for your suggestions!

Yes, these ideas can be extended and modified in many ways. It just depends on how much effort a person wants to put into protecting their scenes from pilferage.

MrLucasManSwe

2014/09/07 22:17:26

What if the person saves for example a car as a Phunlet from a scene and put it in another scene.. will it still work?

lompilomp

2014/09/07 23:18:13

Umm yeah but now that you showed us this, I think that people with some knowledge would be able to delete the script. I'm not a good scripter but I'd be able to, probably.

s_noonan

2014/09/07 23:41:46

This is a great scene. I can see why you would want to copy protect it.

faytree

2014/09/08 01:50:25

Hey,Xray!
I have a brilliant idea! Let's say that a "copier" knows where the "anti-theft scene" sensor and tries to delete it,so no one knew that the "copier" steals someone's scene.To avoid it,we can use the onDie command,when the "copier" deletes the sensor,the onDie command will clear all the scene and telling that the sensor is deleted!

Xray

2014/09/08 02:27:28

Great idea, faytree! Go ahead and try it to see how well it works! :tup:

lompilomp

2014/09/08 21:18:30

*Deletes onDie command first, then the anti-theft script*

faytree

2014/09/09 00:49:06

Hmmm,time to make an advanced scripting! back to the workshop!

Jimmyfisherman

2014/09/26 01:43:08

I got an idea! Make the box on the update event, randomize its position every step. Then make it spawn a new box when it is deleted!

A Lucas

2014/10/12 21:44:00

i steal things all the time i admit it, but i normaly dont put the stuff in my scenes
i normaly just like to screw around with them (copy a bunch of crashable vehichles and SMARSH ERM' TOGETHAR

)

A Lucas

2014/10/12 21:46:35

oh and uh...i used a brush to look at the rest of the girl...yeah shes a GIANT box O_O

Xray

2014/10/12 23:35:14

Copying other people's scenes is not "stealing". In fact, we encourage it! What better way is there to learn how to do things than to copy other people's scenes to see how they did certain things? It becomes "stealing" when you copy someone's scene or parts of their scene, and then upload it without permission as if you were the original author. Some people do not have a problem with that, and other people go completely bananas when you do that. I receive more complaints about "scene stealing" than any other issue.

Thanks

VietCreator

2014/12/14 04:27:25

Wow Xray, I never knew you could copy protect scenes like this.
I don't use scripting (in general I never used it) but I will go back to this scene
to read this again to copy protect my scenes.

T'wind

2015/07/24 19:46:43

Place this code in the update event and check the box immortal
Scene.cloneEntityTo(Scene.entityByID(entityID), Pos);
scene.removeEntity(Scene.entityByID(entityID))
Now the geometry won't be selectable. But it's laggy if you don't use a timer.

Last edited at 2015/07/24 19:46:55 by T'wind

Xray

2015/07/24 20:37:02

T'wind - That's a very ingenious way to prevent someone from selecting the geometry and then modifying its code! Another way, which does not cause any lag at all, is simply to move the geometry to another layer (say, layer-1) and select layer-0 as the active layer. You can hide a tiny geometry (such as a tiny sliver) by placing it on some far away x,y position where no one would ever accidentally find it.