Author Topic: Working Binary Save Format Released --- eh im just gonna release this  (Read 618 times)

I remade the topic cause that one started about something else.
I'm eventually going to lock this one too and post in add-ons.

Pros:
  • Saves are 70 to 75 percent of their original size.
        Save name    Default size     Binary Size     Final Size
        ACM city     719kb     527.5kb     73.3%
        ATC fort     263.6kb     192.3kb     72.9%
        Sirrus Military Compound     777.7kb     550.2kb     70%
        Goldengate     1.9mb     1.4mb     73.6%
        Crysta Castle     507.1kb     385.6kb     76%
        Afghan DM     582.4kb     432.8kb     74.3%
  • Ownership is saved for every single brick. This fixes many issues where bricks would load with the loaders ownership no matter what.
  • Server-side saving. Can easily be used for an autosaver.
  • Possibility of adding support soon for brick persistence. (saving variables to bricks)
  • Saves bricks by datablock name and not uiname. There have been a few instances of developers changing their bricks display names and screwing up saves. (I had to deal with this personally with the wedge bricks)

Cons: (Stuff that will hopefully be fixed eventually)
  • Longer loading times. Loading golden gate takes about 72 seconds on my computer. Hoping to add non-blocking saving and loading to make this a non-issue.   Now non-blocking, meaning it shouldn't lag/stop the server when loading or saving. Still takes a bit longer though.
  • No options currently to disable saving events or ownership. This is planned however.
  • Not a client side format, you have to be the host of the server to save the bricks like this. I could plan on adding a client side mod but it'd most likely only work (or work better enough to consider using) on servers with the server mod.
  • While future versions of the mod will be backwards compatible (able to load saves from previous versions), the mod may be updated frequently, meaning you might want to wait until some of the planned features are added.

Installation:
  • Just unzip both server_binarysave and it's requirement support_binary to your add-ons folder.


Download:


Usage:
  • /loadBinarySave <path>   ---   Must be a complete path (e.g. "saves/test.bin" is okay, but "test.bin" is not) must be admin to use.
  • /saveBinarySave <path>   ---   Same as above
  • /binarySaveCancel    ---   Admin only, cancels any saving or loading from the add-on.
« Last Edit: August 27, 2014, 05:14:43 PM by DrenDran »


This is good progress, a great improvement on your last saving system.

This is good progress, a great improvement on your last saving system.
Thanks!
Is it working for you so far?