Repository navigation
·
10 commits
to main
since this release
Replace the jar and restart. Your config is kept as it is.
Added
- A developer API, like CoreProtect's, so other plugins can work with xRewind: they can log the blocks and items they change (so a plot reset shows in lookups and can be undone), look up the history, preview, apply and undo rollbacks and restores, and hold the writer for a moment while a backup copies the database. Plugins' lookups and rollbacks run like yours: in the background, a few milliseconds per tick, one rollback at a time. See Developer API. It costs nothing unless a plugin uses it.
- Plugins can listen for rollbacks (and stop one before it starts), and for lookups, to keep an audit log of who looked up what, staff commands included. A staff member whose rollback, apply or undo another plugin stopped is told so.
- A purge or a CoreProtect import that the server stops partway says so, with how many changes the purge deleted by then.
Fixed
- Clicking Next page below a lookup's results shows the next page. It ran
<next>instead, which isn't a command. - After a purge, the space is handed back to the disk a few thousand pages at a time, so logging never waits on all of it at once.
- A CoreProtect import can't wait forever for its last rows when one of them is a change the database won't take.
/xrewind reloadworks on an empty server. Paper pauses a server that's been empty for a minute, and the reload waited for the next player to join.- A rollback or restore typed in the console of an empty server runs straight away, not when the next player joins.
- On MySQL, a connection whose database stops answering gives up after five minutes, or ten seconds to connect, instead of holding the writer forever.