--forceUpgrade removed/not implemented in 26.1
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Is your feature request related to a problem?
I know chunks are updated on load. But I need to convert 1.14/1.17 worlds to .slime format with AdvancedSlimePaper on 26.1.2, and ASP reads from disk, discarding old chunks. Without forceUpgrade (not implemented in 26.1) and without saving the world, how do I get the updated chunks to disk? i make custom fork plugin from originale source code of Slime-World-Manager native 26.1.2 this is why i need this features if is possible
Describe the solution you'd like.
a input for start bat who convert and upgrade old block from 1.14 to 26.1.2
Describe alternatives you've considered.
--force-upgrade --erase-cache nogui
Other
No response
Contributor guide
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 reproducing the 1.14/1.17 world conversion with AdvancedSlimePaper on 26.1.2, using the proposed --force-upgrade and --erase-cache flags. Review the server's world-loading and chunk-saving entry points to determine where the missing conversion behavior belongs; done means an old world can be converted to .slime with upgraded chunks written to disk without a normal world save.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100