Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

webfort-level autosaves? #38

Open
Alloyed opened this issue Nov 23, 2014 · 1 comment
Open

webfort-level autosaves? #38

Alloyed opened this issue Nov 23, 2014 · 1 comment
Labels

Comments

@Alloyed
Copy link
Collaborator

Alloyed commented Nov 23, 2014

so quicksaving itself isn't too hard, and I think it'd be nice to have webfort manage its own saves so nobody needs to be around to babysit it. The question is, when to save?

  • At the beginning of players turns, to act as a safety net for bad decisions? (nofun.jpg)
  • If the game has been idle for a bit, so nobody has to wait through saves?
  • Other times?
  • A combination?
@Dragoon209
Copy link

While it would be nice to save before each turn, the time it takes to complete the save makes it impractical. Even with SSDs, the delay is annoyingly long.

I think a mixture of a few times would be best: At start of fort (Embark), Seasonally, on idle of 15 minutes, and on admin demand.

This might be a bit overkill, but I think it makes a good match of ensuring history is recorded accurately even when an admin isn't active 24/7, and preventing player annoyance.

This sounds good in my head - thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants