The only features this add-on provides by default is the ability for admins and super admins to make the server save the build to itself (rather than downloadng and making a save on the client as normal) and to load said saved builds. I'm sure there's another add-on out there that does that already, however this does so in a format not completly compatable with normal save files. Much like say, player persistance, this allows mod makers and server hosts to add variables that the add-on should save along with it. For example, if you were hosting unlimited mining, you'd want the health and value of each brick to be saved.
The commands are:
/bvssSave %filename %description
/bvssLoad %filename
All saves are by default saved to saves/bvss/<name>.bls to keep them separate from normal saves.
Note, the description can not have any spaces, and the bricks will always belong to the client that uploaded them, though I plan to fix these two problems.
The function to be used by hosts or mod makers is simply this:
BVSS_addVar(%name,%condition);The %name is the name of the variable, if you wanted to save %brick.health then the argument would be "health".
The %condition is the name of a variable to check to determine if the value should save, for example, if you wanted to only save the health of mineable bricks, you'd put "isMineable". And the add-on would only save "health" for bricks where %brick.isMineable is true. Alternativly you can leave it blank, and it will save for all bricks, ignoring the condition.
For example, to make unlimted mining work with this, all you have to do is add three or four lines to the server.cs:
exec("./mining.cs");
exec("add-ons/server_brickvalues/server.cs"); //make sure the add-ons already loaded
BVSS_addVar("type","isMineable");
BVSS_addVar("health","isMineable"); //add our values, but only to be saved if they're minable bricks
BVSS_addVar("isMineable","isMineable");
The add-on:
http://www.filedropper.com/serverbrickvaluesExample save of unlimited mining:
http://www.filedropper.com/mining
