The (Near) Solution to Build Stealing

[Altered]

Difference between 'kissing ass' and directly insulting him.

Because obviously Badspot was in this thread and I directly to-his-face insulted him.
http://en.wiktionary.org/wiki/directly

You can own them if you play singleplayer. The moment someone joins and ghosts, they've downloaded your build, whether or not they decide to store it on their hard drive.

And I'm supposed to know they download it to their hard drive how...?

If it's good enough and you let people know about it, then you wont have to worry about that.

But if it's only good enough I will have to worry because someone is going to download what is good and post it as theirs.

[Ad Bot]

[YourBuddyBill]

Because obviously Badspot was in this thread and I directly to-his-face insulted him.
http://en.wiktionary.org/wiki/directly

And I'm supposed to know they download it to their hard drive how...?

But if it's only good enough I will have to worry because someone is going to download what is good and post it as theirs.

Simmer down, bro. The instant I find out that a build I am visiting is stolen and uncredited, I start slaying the thief and I write down his ID so I can ban him from my servers whenever.

[DrenDran]

So I'm not allowed to own my builds?
Genius!

No, you're not.

[Hazmat]

what about not being able to load without ownership? There can be an option to be able to edit these bricks like a separate trust level. but anyone who painted or wrenched the bricks would see the real owner.

[Gamefandan]

I just thought of a very simple process.

Convert your base bricks and downloaded bricks into ones with different names.
The bricks will now be different from the standard bricks.
Therefore, upon saving and loading these bricks, it wouldn't load anything unless the person owned the exact files.

[YourBuddyBill]

I just thought of a very simple process.

Convert your base bricks and downloaded bricks into ones with different names.
The bricks will now be different from the standard bricks.
Therefore, upon saving and loading these bricks, it wouldn't load anything unless the person owned the exact files.

This is kinda what I was saying before.

what about not being able to load without ownership? There can be an option to be able to edit these bricks like a separate trust level. but anyone who painted or wrenched the bricks would see the real owner.

You can turn off Save Brick Ownership in the save menu. Then it saves ALL brix as the savers brix.

[Demian]

I just thought of a very simple process.

Convert your base bricks and downloaded bricks into ones with different names.
The bricks will now be different from the standard bricks.
Therefore, upon saving and loading these bricks, it wouldn't load anything unless the person owned the exact files.

Through the many years this build stealing prevention thing has been suggested, this is the only way to do it as far as I know.

[-Jetz-]

I just thought of a very simple process.

Convert your base bricks and downloaded bricks into ones with different names.
The bricks will now be different from the standard bricks.
Therefore, upon saving and loading these bricks, it wouldn't load anything unless the person owned the exact files.

Wouldn't that also mean you'd have problems loading your own saves that used default brick names?

[Gamefandan]

Wouldn't that also mean you'd have problems loading your own saves that used default brick names?

It would.

What one could do is create a script that, upon loading something that uses the old brick names, it sets the new names equal to the old names. Something like that; I haven't scripted anything in like four months so I'm pretty much talking out of my ass here.

[-Jetz-]

It would.

What one could do is create a script that, upon loading something that uses the old brick names, it sets the new names equal to the old names. Something like that; I haven't scripted anything in like four months so I'm pretty much talking out of my ass here.

Badspot said that if something managed to successfully disable a client's ability to save, he'd do something to break such a script. Let's not give anyone ideas that could lead to our modding capacity being further restricted in exchange for a couple months of semi-protected builds on select servers.

[Chrono]

Because obviously Badspot was in this thread and I directly to-his-face insulted him.
http://en.wiktionary.org/wiki/directly

Way to dodge the important point!

And I'm supposed to know they download it to their hard drive how...?

You don't. Which is why you can't stop them.

But if it's only good enough I will have to worry because someone is going to download what is good and post it as theirs.

Then let people know about it, or make a topic before they do.

It would.

What one could do is create a script that, upon loading something that uses the old brick names, it sets the new names equal to the old names. Something like that; I haven't scripted anything in like four months so I'm pretty much talking out of my ass here.

And then I would personally make something to reverse the process and then release any builds saved like this to the public.

[YourBuddyBill]

...
And then I would personally make something to reverse the process and then release any builds saved like this to the public.

You are now officially awesome.

[Gamefandan]

And then I would personally make something to reverse the process and then release any builds saved like this to the public.

Each person would of course have their own method of saving like this, thus completely neutralizing this statement.

You are now officially awesome.

Someone who is already awesome cannot be declared awesome by someone that is not awesome.

[YourBuddyBill]

Each person would of course have their own method of saving like this, thus completely neutralizing this statement.

Someone who is already awesome cannot be declared awesome by someone that is not awesome.

I have some friends who are much more awesome than me. Awesome enough to declare it for me at least. Back to the topic: Badspot would probably break the responsible mod, thus further restricting our modding capabilities cause a few jackasses went and stole builds and the owners flipped out.

[Jerkface]

The mod wouldn't be an addon.  It would be an executable program that would run WITH Blockland to transfer the data.

Badspot can't bypass this.  Once released, if at all, every person can change the .exe name of the program and it would be untraceable.  (Of course, change the save location as well - at the very least it would be a pain in the ass to try to block it based on how it acts within the game.)