Feature Request: Screen for managing/clearing the voxy cache per server + dimension.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
With #299 and #279 being marked as won't be implemented, the issue still remains that voxy data for temporary worlds (Resource worlds, minigames) or on servers someone no longer visits will remain in the .voxy/saves directory.
It is not possible, to clear these, especially if you want to clear only a particular dimension (Such as a resource mining one).
The internal structure within each save/server folder is a non-human readable hash as shown below:
These hashes also appear to take seed or such into account, as 4 of those folders are generated from our survival server's resource world over the last several weeks.
Since the option as a server owner to be able to mark a world/dimension as "don't map" or to give it it's own unique id that doesn't change with seed etc is not being considered; I would like as a user of the mod to be able to see from within the game, the save data usage, broken down by save/server -> dimension, with human readable names (even if these are the resource keys, they are much more legible than the hash as shown below.) and have the option to clear that particular dimension of a save/server from my local data.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the .voxy/saves directory and how its server and dimension data is represented by the non-human-readable hashes. Done means an in-game screen can show storage usage grouped by server and dimension with human-readable names, and can clear a selected dimension's local data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100