Server-Sided Saving
3 KB, 12 years ago, submitted by
Note: Credited Randy & Ephi for the duplicator code I stole.
What does this do?
Well, simple, it saves every brick, ghosted or not, server-sided. Which also means this will work on a dedicated server.
Usage:
ServerSave(saveName,ownership,events);
example: ServerSave("My Freebuild",1,1);
ServerLoad(saveName);
example: ServerLoad("My Freebuild");
Optional: ServerLoad(saveName,Ownership,Map name,color method,silent);
saveName = the name of your save
ownership = Whether ownership saves/loads or not
events = Determines whether or not brick names and events will save
Map name = That dropdown box that shows up when you load bricks, all slate edits usually use slate
color method = 1 tries to add the missing colors to the end of the current colorset which will most likely fail in all cases you try to use it, 2 just uses the color ID, 3 is the default way of loading which tries to find the closest matches for colors
If there's any bugs, don't just rate it down and post rude comments. Tell me the problem and I'll fix it.
If you found a problem and fixed it yourself already, send it to me so I can update this.
And lastly, feel free to use this as a resource without giving any credit. I believe in allowing people to learn by looking at others work without the hassle of having to figure out who they learned from.
Normally, save bricks button only saves everything you've seen so far, including if you're the host of a dedicated server.
This will save everything that exists, meaning you don't have to walk around and look at everything to save.
serverDirectSaveFileLoad(filename, colormethod, directory name, do ownership, silent)
Also what do you mean by NOEDIT? There is an edit button.
ONTOPIC: Nice. Useful.