(17-08-2017, 05:11 AM)Knight Wrote: Why not increase the wait time before the dupe is removed to say 10 minutes?
Because there will always be someone who needs more time, in the end people will ask for it to be stored persistent.
Again, this is a safety net in case you lost connection or something, it's not the supposed way of saving your work.
(16-08-2017, 09:41 PM)Kosmos Wrote: Side note: If you join the server and remain AFK (unless joining takes at least 10 minutes) it's pretty much your own fault. Storing a dupe for every player ever needs space you see.
Why not increase the wait time before the dupe is removed to say 10 minutes? It could possibly stop people from losing their ship and I understand how annoying that can be when all you did was go to get a drink while waiting for the server to load.
I could order 2 pizzas from 2 different places and they would get to my house before I load into the server (takes 30+ mins for me)
Are you running the game on a toaster?
Nah, I just dont have a good connection to the server (usually abouts 120 ping on server)
gotta say that being an aussie with 320ping all the time, never experienced waiting anything longer than 10mins and that's if I was downloading the stuff again. possible slow hard drive loading the addons/models?
5 minutes pass after you rejoin the server and you've actually sent any input to the server (so it assumes you've finished loading and are active).
Roughly 1 day after the autosave is created.
So if you're going to go AFK, don't move around and then go AFK or it will start the expiry timer.
Saving a local file has a couple of problems:
Where does the file get saved?
What naming convention does it use?
Does it overwrite an old file or create a new one?
How can a player know it's there?
What if they don't want it?
All of these are solvable, but they add complexity and time to a feature that is just a safety net to get you back on your feet.
You should always be saving your work, and if your work is that important to you and the autosave is the only thing left, you should prioritise spawning it/loading it so you can get it permanently saved. Otherwise don't join the server again until you're ready to do so to prevent it triggering the expiry.
When the server crashes you can't save dupes anymore. The server is already dead, it won't continue running Lua scripts.
And autosaving every (few?) minute(s) is too much performance wasted on the off-chance of needing it.
If the server had already saved an autosave before it crashed, then it will still exist when it restarts. They only get deleted if the server is still running at the 5 minute mark after rejoining and being active.