================================================================
 BLUEBOTHER MODPACK - CLIENT MOD VERIFICATION PROMPT
 Paste everything below the line into Claude Code on the PC you
 play Minecraft on. Run it from any folder.
================================================================

I play on a modded Minecraft server and I need you to verify that my client's
mod folder exactly matches what the server expects. Please work through this
carefully and do not change anything until you have shown me a report first.

SERVER DETAILS
  Address        : bluebother.duckdns.org:25565
  Minecraft      : 1.21.1
  Mod loader     : NeoForge 21.1.218
  Pack           : Cobblemon / Create

STEP 1 - Get the authoritative list
Download the manifest:
  https://bluebother.duckdns.org/client-mods-manifest.json

It has four parts:
  required     - every mod I must have, with the exact SHA1 and file size
  client_only  - optional client-side mods the server does not care about
  must_remove  - mods that actively cause problems and should be deleted
  Entries with "match": "sha1" must byte-match. Entries with "match": "name"
  only need the filename to match - read the "note" field, the server
  deliberately runs a modified copy and the difference is expected.

STEP 2 - Find my mods folder
Look for a NeoForge 1.21.1 instance. Common locations on Windows:
  CurseForge  %USERPROFILE%\curseforge\minecraft\Instances\<pack>\mods
  Prism       %APPDATA%\PrismLauncher\instances\<pack>\.minecraft\mods
  MultiMC     <MultiMC>\instances\<pack>\.minecraft\mods
  Modrinth    %APPDATA%\ModrinthApp\profiles\<pack>\mods
  Vanilla     %APPDATA%\.minecraft\mods
If you find more than one candidate, list them and ask me which I use.
Do not guess.

STEP 3 - Compare
Compute the SHA1 of every .jar in my mods folder and compare against the
manifest. Note that PowerShell's Get-FileHash can fail on jars that are
locked by a running game - use a shared-read file handle, or tell me to
close Minecraft first.

STEP 4 - Report before touching anything
Show me a table with four sections. Give exact filenames, and counts:
  MISSING        - in the manifest, not in my folder  (this breaks joining)
  WRONG VERSION  - filename matches but SHA1 differs  (this breaks joining)
  MUST REMOVE    - anything in the manifest's must_remove list
  EXTRA          - jars I have that are not in the manifest at all
For EXTRA, do not assume they are wrong. Client-side-only mods (minimaps,
shaders, FPS mods, QoL tweaks) are usually fine to keep. Tell me which
category you think each one is and let me decide.

STEP 5 - Fix, only after I say go
  - Back up the whole mods folder first (copy it to mods-backup-<date>).
  - Never delete a jar without listing it and getting my explicit yes.
  - For missing mods, the full current mod set is here:
    https://bluebother.duckdns.org/modpack-mods.zip   (350 MB, 152 jars)
    It is rebuilt from the live server and matches the manifest exactly.
    The jars sit at the root of the zip - extract them directly into the
    mods folder, do not nest them in another folder.
    If you would rather not re-download 350 MB, tell me the exact missing
    filenames and I will fetch just those from Modrinth or CurseForge,
    matching NeoForge 1.21.1 and the SHA1 in the manifest.

STEP 6 - Confirm the loader
Check that NeoForge 21.1.218 for Minecraft 1.21.1 is actually installed for
this instance, not just a matching mod list. Tell me the version you find.

Please start with steps 1-4 and show me the report.