Is your feature request related to a problem?
When dealing with a recent player issue I ran into a case where a player had about 350 pages worth of logs. We don't want to blindly roll everything back and prefer to search for player actions, tp to the area, preview a rollback, and apply if it seems appropriate.
However there are a lot of pages. After being rolled back, the entries show up crossed out, but still contribute to 350ish pages of logs.
Describe the solution you'd like.
Adding a filter such as rollbackStatus = (boolean or equivalent to "default, rolled back, reverted") to a search query would allow for very easy exclusion of the search results which have already been rolled back (or reverted).
Describe alternatives you've considered.
- Paging through every result and ignoring rolled back actions
- Blindly rolling back all block place or break actions
- Only inspecting changes via search, not visually
- Filtering chronologically in 15 minute increments
Agreements
Other
Per request on Discord
Is your feature request related to a problem?
When dealing with a recent player issue I ran into a case where a player had about 350 pages worth of logs. We don't want to blindly roll everything back and prefer to search for player actions, tp to the area, preview a rollback, and apply if it seems appropriate.
However there are a lot of pages. After being rolled back, the entries show up crossed out, but still contribute to 350ish pages of logs.
Describe the solution you'd like.
Adding a filter such as rollbackStatus = (boolean or equivalent to "default, rolled back, reverted") to a search query would allow for very easy exclusion of the search results which have already been rolled back (or reverted).
Describe alternatives you've considered.
Agreements
Other
Per request on Discord