CREATE'A COLONY 1.1 — REMAINING ISSUES
Reviewed 11 October 2026. These are observed in the pinned original mods.

The server boots and accepts the original client, but it does not have a clean
startup log. The final restart recorded 312 ERROR-level lines versus 341 in the
unmodified server selection. A repeated message is not necessarily a separate
bug. Errors have not been hidden or logging disabled.

FIXED IN THE SEPARATE SERVER DATAPACK
13 JSON resources restore four recipes, three Tracks loot tables, effective
Tracks block tags, and the parsing of 20 ammunition selectors plus two
propellant selectors. The final run loaded 139 projectile mappings and 46
propellant entries without rejection. This proves data loading, not every
cannon's in-game behavior. All original mod JARs remain byte-for-byte unchanged.

Tracks registers one block, tracks:track_mount. Its drive and suspension
variants are items backed by that block. The datapack corrects uppercase IDs
and maps block-tag references to the actual block. Runtime commands confirmed
the axe, pickaxe and safe_nbt tags, retained vanilla pickaxe membership, and
all three loot-table results. The three original malformed tag files still
log parsing errors because Minecraft reads tag contributions from each pack;
the valid additive contributions supply the intended effective tags.

REMAINING ORIGINAL-MOD ISSUES
1. Aeronautics:No Horizon 1.0.3 throws a duplicate track_tool_kit exception
   during MineColonies' creative-tab scan. MineColonies catches it and continues
   discovering other items. Exact class inspection confirms the custom tab
   enumerates items also registered for automatic tab insertion. This can
   impair discovery of this mod's items by MineColonies. See VALIDATION.txt
   for the separate real-client inventory test; do not assume all integrations
   are correct merely because the client can join.

2. Four recipes remain rejected:
   cbc_at:munition/rocket/rocket_fuzing — missing recipe serializer
   cbc_at:rocket_munition_fuzing. This recipe is unavailable. Restoring custom
   fuzing behavior requires a compatible mod-code fix, not an invented recipe.
   midgard:malachite_block and midgard:malachite_from_block — reference items
   absent from this version. s_a_b:glassarmor — targets deleted_mod_element.
   No replacement gameplay or substitute items have been invented.

3. Linear Bearing contains a block-physics object duplicated under dimension
   physics, where it lacks a dimension field. That dimension record is skipped.
   AeroCopycats references removed copycat_step and copycat_catwalk blocks.
   Eight Sable error lines occur across these records/dimension initialization.
   Test actual bearing and Copycats vehicle behavior before relying on it.

4. Steam 'n' Rails contains 276 loot tables referencing absent optional track
   variants (for example Twilight Forest, BYG and Quark). They fail because
   the corresponding items are not registered. Adding unrelated mods just to
   silence these messages would change the pack. Existing train behavior still
   needs gameplay testing. Two more stale loot tables refer to unregistered
   midgard:conifer_topsoil and minecolonies_compatibility:citizen_grid items.

5. Midgard contains one world-generation filename with a space ('1 copy.json');
   Minecraft ignores that invalid resource. Its intended content cannot be
   inferred safely from its filename alone.

6. Sixteen client-class probe errors appear while retained shared mods apply
   mixins on a dedicated server. They are non-fatal in these runs. Removing
   shared content mods to silence them would risk client/world mismatch.

7. C2ME logs a failed optional FastNoise/Lithostitched binding. Inspection of
   its code confirms the exception is caught and the binding marked unavailable.
   Startup, limited generation and saves passed; broad threaded world-generation
   stability is not proven. C2ME is retained at the original version.

8. The original client logged repeated GLFW 65539 Invalid key -1 errors
   during play, plus JEI empty-item and some asset-loading errors. The player
   remained connected and confirmed the Creative tab/block test passed. The
   responsible keybinding/mod has not been isolated; no client settings were
   edited. Investigate this client-side log spam separately if it persists.

RELEASE LIMITS
This is a validated local baseline for staging on Pterodactyl. It is not a
guarantee against crashes. Linux execution, cloud UDP connectivity, multiple
remote clients, loaded colonies, assembled vehicles and sustained load require
testing on the actual host. Keep backups and do not auto-update individual mods.
If a later mod fix is adopted, update shared client/server content together and
repeat the tests in a separate server copy. Do not edit JARs in place.
