[Server] Autosaver - [Version 3.0.0] - Javascript version??!!! (tba)

[Trogtor]

a cool thing if possible is that bricks that are floating are supported by whatever base plate it's on. So you can delete and add bricks on it without it breaking completely

[Ad Bot]

[Conan]

that i think falls under floating bricks support mods, not the autosaver
what's happening is that when you load the build, all the bricks are loaded as non-hackplanted, so the bricks act like normal loaded floating bricks. once you hackplant a support however it goes back to acting normal.

[Mr Noone]

this is a lot better than the one by zack0wack0
whatever his name was

[Trogtor]

once you hackplant a support however it goes back to acting normal.

actually this does not work

and for some reason my bricks are the only bricks that actually have a support on load

[Conan]

actually this does not work

and for some reason my bricks are the only bricks that actually have a support on load

i'm 100% sure this works; if you're just building a brick on the bottom of the floating bricks its not hackplanted. i use this method to fix the floating status of my cool smile airship and it works fine.

basically i build a brick in midair, then attach this to the coolsmile zone brick. after that i can hammer/whatever normally

[Trogtor]

i tried to get flamecannon to do that he said it didnt work

[Gytyyhgfffff]

you need to reconfigure the default preferences so that someone like me who doesn't configure prefs and leaves the autosaver saving without checking the files once doesn't end up with this

my server said it didn't have enough space or recources on it to write a log or something and i think i figured out why

[Conan]

if you updated to the latest version, it doesn't save the bricks unless a difference in the save file is detected. that doesn't trigger though if the difference is just events or print/color changes; only if the brickcount changes will it trigger. Not sure about changing the bricks in a specific location though.

had the same issue with halloweenfest for a bit.

[Gytyyhgfffff]

if you updated to the latest version, it doesn't save the bricks unless a difference in the save file is detected. that doesn't trigger though if the difference is just events or print/color changes; only if the brickcount changes will it trigger. Not sure about changing the bricks in a specific location though.

had the same issue with halloweenfest for a bit.

i probably have the old version actually
ignore my above post then

[Kyuande]

My apologies for my autosaver eating up your space. Please update it when you can.

The autosaver will save a new file if events or the brickcount changes if you have the pref on as said in the OP.

[TheBlackParrot]

I enabled the addon and it proceeded to spam, trying to save bricks every frame.

[Kyuande]

I enabled the addon and it proceeded to spam, trying to save bricks every frame.

That's odd. Are you sure you updated it to the current version? This doesn't happen to me.

[Dannu]

Console.log would be helpful.

[TheBlackParrot]

I set $Server::AS::Interval and it fixed itself, probably wasn't set ri-
Custom pref system broke it, apparently RTB_registerPref actually sets the variable. wtf

[Kyuande]

Bump. I didn't realize that the autosaver does not restart the interval unless you manually do the command. I am currently testing the update to see if I fixed it. This is caused when it successfully loads a save from the autosaver folder.