Author Topic: Stealing my Island ThrowMod Build - Darkmaster/Winner, me!!!, and MARBLE MAN  (Read 3111 times)

I'm starting to think an anti-saving script might not be a bad thing.

I hate it when people snag a build just so they can host exactly the same thing themselves. This screams the person wants to claim it.

I hate it when people snag a build just so they can host exactly the same thing themselves. This screams the person wants to claim it.

If there is any commands that are sent to the server, then we might be able to prevent these from happening.

Is he just saving the build to try it out himself or is he literally saying he made it?

I'm afraid Badspot said he'd personally ban / deactivate anyone who tried to make an anti-save script, didn't he?

I'm afraid Badspot said he'd personally ban / deactivate anyone who tried to make an anti-save script, didn't he?

Never heard of this, he or someone else did say it were impossible to make an anti-save script.


We need Truce to bust this myth.

I'm starting to think an anti-saving script might not be a bad thing.
Nope, not possible.
If it was, it'd be here already.

Nope, not possible.
If it was, it'd be here already.

Until Truce came along.

I'm afraid Badspot said he'd personally ban / deactivate anyone who tried to make an anti-save script, didn't he?

Really? I feel that to be absurd. If you want to host a build, but don't want people stealing it, then an anti-saving script would be great. But, I'll probably forget to even start looking for it anyways, so I probably won't do it.

Until Truce came along.

I was expecting this.

Nope, not possible.
If it was, it'd be here already.

Maybe because you never traced a saving process.

Until Truce came along.
If Truce did it, show me please.
Really? I feel that to be absurd. If you want to host a build, but don't want people stealing it, then an anti-saving script would be great. But, I'll probably forget to even start looking for it anyways, so I probably won't do it.

I was expecting this.

Maybe because you never traced a saving process.
http://forum.blockland.us/index.php?topic=18084.msg253802#msg253802
http://forum.blockland.us/index.php?topic=26418.msg388213#msg388213
Too old for actual quotes, just click it.

And yes, I've traced a server while a client was saving.
When the client requests the events, a function is called, but Badspot has blocked modification of it.

http://forum.blockland.us/index.php?topic=26418.msg388213#msg388213
Too old for actual quotes, just click it.
Quote
On the other issue, I definitely agree that there should be a way to save with brick ownership.  Often you have to restart or something when hosting a server and it'd be great to be able to save off the full state of the server

Ha, it's so old it was during the time when brick ownership didn't exist when saving.

Oh wow I didn't even notice this Drama.
Oh well I don't think that I really have to say anything since Munk showed my PM.

Mandatory brick ownership save when on a server seems like a good compromise.

You can still use the build, just not edit it and others can see the original creator.

It's impossible to prevent saving the bricks. Preventing the saving of events/ownership is possible, at least for Badspot. But because of how it works nobody can prevent saving the bricks themselves.

Mandatory brick ownership save when on a server seems like a good compromise.

You can still use the build, just not edit it and others can see the original creator.
Nope.
You can still just edit the save file manually, and surely automated tools to do this would pop up pretty quickly. Also, it's rather impossible to enforce that you save it that way, you can simply make a custom script that dumps the brick data down to a .bls, just like it works right now.



Well, it might be possible to prevent the client from saving it, but not for anyone except for Badspot, who has clearly said that he encourages sharing builds.

NOEDIT: Also, the host can force trust between IDs.