Cherished Worlds 17.0.0: Pin Worlds on Minecraft 26.2

Minecraft Java world-list safety aid

Cherished Worlds adds a star control to the single-player world and multiplayer server lists. Marked entries stay at the top, and the delete action is unavailable while an entry remains cherished. The current Minecraft 26.2 release is 17.0.0+26.2 for Fabric and NeoForge. It is a client-side convenience guard, not a copy of a world and not a recovery system.

Current 26.2 setup

The project marks the client required and the server unsupported. A pinned multiplayer entry is therefore a local list preference; it does not reserve a slot, protect the remote server, or change another player’s server list. The project page broadly lists other loaders, but the checked 26.2 release feed contained Fabric and NeoForge files.

What the star protects—and what it does not

While a world is marked, Cherished Worlds removes the normal ability to delete it from the selection screen and keeps it above unmarked entries. Multiple marked worlds are ordered by last played date. That reduces an accidental click path, but the underlying world folder can still be deleted, corrupted, overwritten, moved, or lost outside that screen.

A favorite marker also cannot restore chunks after a bad mod update. Before changing loaders, mod versions, or world-generation content, make a restorable copy with the MineBrush modded-world backup checklist. Keep backups outside the active saves folder.

Safe install and marker test

1. Create a tiny disposable world in a working Fabric or NeoForge 26.2 profile. Close Minecraft and copy the profile configuration.
2. Add the matching Cherished Worlds 17.0.0+26.2 file. Fabric players also add Fabric API.
3. Open Select World and click the empty star beside the disposable world. Confirm the visual state changes and the entry moves to the marked section.
4. Select the marked world and inspect the normal delete control without confirming any deletion. It should be unavailable while the marker is active.
5. Restart the client and confirm the star persists. Unmark the disposable world and confirm ordinary list behavior returns.

Repeat with a throwaway multiplayer server entry if that part matters to you. Never use an irreplaceable world as the first test of a UI safety feature.

Fix a missing star, lost marker, or confusing order

If no star appears, confirm the JAR matches 26.2 and the active loader. Check that the file is in this instance’s mods folder rather than another launcher profile. Preserve the latest log and remove duplicate Cherished Worlds versions.

If a marker disappears, record whether the launcher changed the game directory, modpack instance, or configuration folder. Test persistence in the same instance after a clean exit. If marked entries reorder, compare their last-played dates; the project intentionally uses that order among multiple cherished entries. If the delete control remains available on a clearly marked disposable world, stop and capture the screen, versions, loader, and minimal mod list for an issue report.

Use a layered world-safety routine

Marking reduces one accidental deletion route. A separate backup protects against storage failure, corruption, a bad update, or deleting the folder outside Minecraft. Keep at least one recent copy outside the active instance and periodically prove that it can be opened in a controlled profile. A backup that has never been restored is only an assumption.

For shared computers, remember that the star is not an account permission system. Another user with filesystem access can still change or remove the save. Protect the operating-system account and backup location separately.

Rollback and evidence boundary

Unmark important entries first so the list returns to an ordinary state, exit Minecraft, copy the relevant configuration, and remove the mod. Removing Cherished Worlds does not delete the worlds, but it also removes its UI guard. Verify that every save folder and external backup still exists before cleanup.

• Cherished Worlds creator project and releases
• Creator source repository and issues

MineBrush rechecked creator metadata on August 28, 2026. We did not launch the JAR or test deletion controls. Exact marker storage, launcher-instance behavior, shared folders, server-list migration, and modpack compatibility remain unknown until reproduced.