#Limit Revision Option
8 messages · Page 1 of 1 (latest)
i think it was planned to have some sort of revision manager
This is a great idea. For now you can just save as a new world (i think? lmk if im wrong) as a workaround.
My recommendation for such a revision manager is for the limit to instead remove alternative revisions rather than oldest.
For example, say the limit is 5:
a
b
c
d
e
revision f & g are created:
a
c
e
f
g
(revision b and d were removed)
This would mean we retain historical saves should we want to use them, such as to compare the progression of a world, but less saves around the same period are kept as newer saves are created.
This would still require some memory to indicate where saves have been removed for the iteration code, but it would be very negligible and could be optimised.
for that you can just manually remove revisions yourself based on date
which will not be prone to behaving unexpectedly
that would be a LOT of work for someone especially a server with frequent autosaves. It would be extremely valuable to have it automated.
We also have no ui to interact with revisions so there is no way you can expect it to be reasonable to manually do this, especially with no way to mass delete
you just select everything except for the last or first in a day