Michiyo.me 1.21.1 — folder-driven Packwiz setup

AUTHORITATIVE MOD FOLDERS

    files/mods/common/   -> installed on clients AND servers
    files/mods/client/   -> installed only on clients
    files/mods/server/   -> installed only on dedicated servers

Generated .pw.toml metadata lives in mods/ and points to the JARs above on
git.pc-logix.com.

No CurseForge API.
No Modrinth API.
No side override JSON list to maintain.


ONE-TIME MIGRATION

1. Put packwiz-folders.py and packwiz-folders.json in the repo root next to
   pack.toml.

2. Make sure this old directory is gone if it exists:

       mods/.index/

3. Keep this in .gitattributes:

       * -text

4. Run:

       python packwiz-folders.py

   On first run, existing mods/*.jar files are moved automatically:
   - known current client-only mods -> files/mods/client/
   - BlueMap pattern -> files/mods/server/
   - everything else -> files/mods/common/

   The known client-only classification comes from the working client/server
   lists supplied during setup.

5. BlueMap was present on the working server but not in the current client repo.
   Copy bluemap-5.7-neoforge.jar into:

       files/mods/server/

   Then rerun the script.

6. Xaero Minimap's client/server version mismatch was known to be accidental.
   The script does NOT classify Xaero Minimap as client-only. Keep only the
   version you actually want in files/mods/common/.


FUTURE WORKFLOW

Normal mod used by both:
    copy/update/delete JAR in files/mods/common/

Client-only mod:
    copy/update/delete JAR in files/mods/client/

Server-only mod:
    copy/update/delete JAR in files/mods/server/

Then run:

    python packwiz-folders.py
    git add -A
    git commit -m "Update pack"
    git push

That is the entire side-classification workflow. The folder is the side.


CLIENT PRE-LAUNCH

    "$INST_JAVA" -jar packwiz-installer-bootstrap.jar https://git.pc-logix.com/Michiyo/Michiyo.me-1.21.1/raw/branch/main/pack.toml


SERVER UPDATE

    java -jar packwiz-installer-bootstrap.jar -g -s server https://git.pc-logix.com/Michiyo/Michiyo.me-1.21.1/raw/branch/main/pack.toml


IMPORTANT

files/mods/ is added to .packwizignore because those JARs are source/download
payloads. Packwiz should install them through the generated side-aware
mods/*.pw.toml files, not as ordinary internal pack files.

config/, kubejs/, etc. remain ordinary Packwiz files and therefore go to both
sides. The side split here is specifically for mod JARs.