Multi Village Selector

What's New

Apply your generated config from chat

/mvs generate now ends with an [Apply changes now] button, so you no longer have to find the file and copy it by hand.

1. /mvs generate writes the config to local/mvs/multivillageselector.json5 and shows the button.
2. Clicking it runs /mvs generate do-confirm, which warns you to review the list first (it is a best guess and can be wrong) and offers [Confirm, move now].
3. That runs /mvs generate apply, which moves the file into config/. If the generated file isn't there, it tells you.

If your existing config is still the untouched default MVS created, it is simply replaced. If it has your own changes, it is saved first as multivillageselector.json5.bak (only the latest backup is kept). Restart Minecraft afterwards. Copying the file yourself still works.

Under the hood

• Mappings are now Mojang + Parchment.
• Gradle build migrated to the Kotlin DSL; NeoForge entry point moved to its own package.
• JaCoCo coverage report for the common module, with a regression floor enforced in check.
• CI: Gradle wrapper validation, Gradle caching via setup-gradle, concurrency control, coverage report artifact.
• Docs updated for the new flow.

No config format changes. Drop-in upgrade from 0.4.2.

Full Changelog: v0.4.2…v0.4.3