Author Topic: Anti-Save  (Read 1478 times)

The first quote says "ice cream" and "panda." That is incredibly old, from back when the forum had curse word censors. "stuff" became "ice cream" and "forget" became "panda." That's where we get our current emotes: What curse words turned into. My point is, I don't remember if Retail was out at the time. Might have been. o.o

Yeah, I noticed that too. The topic was pretty old, I can search it up again.

EDIT: Here is the topic with the quotes.
And here is the topic with the censoring.

And yes, retail was out at the time.
« Last Edit: August 16, 2011, 06:25:50 PM by Awdax »

The first quote says "ice cream" and "panda." That is incredibly old, from back when the forum had curse word censors. "stuff" became "ice cream" and "forget" became "panda." That's where we get our current emotes: What curse words turned into. My point is, I don't remember if Retail was out at the time. Might have been. o.o
aaah the good ol' days.

Alright,  :cookie: and :cookieMonster: makes sense.
 :panda: and  :iceCream: you just explained to me, but what's with the  :nes:?

But the thing i have to say against Badspot is , what's the big deal? why do you hate the idea?
It's not the generic builds that need protection, but I'm talking about things like deathmatches which are to be hosted, but are vunerable to stealing.

Alright,  :cookie: and :cookieMonster: makes sense.
 :panda: and  :iceCream: you just explained to me, but what's with the  :nes:?

I forgot what Nintendo was, but I know it came up. Ice Cream is stuff, Panda is forget... Nintendo is Bitch, maybe?

But the thing i have to say against Badspot is , what's the big deal? why do you hate the idea?
It's not the generic builds that need protection, but I'm talking about things like deathmatches which are to be hosted, but are vunerable to stealing.
By allowing a client to spawn in your server you are giving them all of the brick data in the server.  That is what ghosting is.  You are downloading all the information about every brick, player, and nearby object.  The only thing you can keep clients from saving is wrench events.

Do you know how to read?

Do you know how to read?

Did you even read what i said?
I asked "Badspot, why don't you want people being able to control if their structures can be saved or not?"

Not "Hey, guys, how does loading work? HURR"

Did you even read what i said?
I asked "Badspot, why don't you want people being able to control if their structures can be saved or not?"

Not "Hey, guys, how does loading work? HURR"

You can control if your build can be saved.

Don't let people in your server.  Saving is client sided, there is nothing else you can do about it.
« Last Edit: August 17, 2011, 11:48:04 AM by Nexus »

Yes, and for the second time, i wasn't saying why nobody can make it, i was saying why Badspot is against the idea!

Yes, and for the second time, i wasn't saying why nobody can make it, i was saying why Badspot is against the idea!

Because its impossible to be able to see and interact with the bricks in the server, and not be able to save that information to file.

Besides this, Badspot has like thirty different explainations, including the fact that amazing builds should stay in circulation, and it makes it easier for worthy builds to get around, so there is a much lower chance of the builds being lost forever if a computer crashes or a harddrive gets wiped.

It would be more of a problem than anything. Everyone would bypass it. Even host-only saving would be problematic. In all cases, it's just a problem. You should be flattered your build is good enough to be worth something to anyone else, I know I would.

Locked topic, why cause This is impossible appearntly and I just looked at badspots post so yeah :(