CCA Compat Fixes — Changelog

[1.7.5]

Fixed

• Crash-on-join (??? ♀ near spawn) — works on both singleplayer and servers — clear_unknown_pokemon is now hooked directly into #minecraft:tick and runs every tick. kill @e on zero matching entities is a no-op (no performance cost), so this is safe. Running every tick guarantees the entity is killed in tick 1 — before the render thread on singleplayer or a connecting multiplayer client ever receives the entity packet. Previously the function was rate-limited to every 200 ticks, which was still too slow: the ??? ♀ entity (Entity ID 16, a persistent CCC fakemon saved in world NBT at -2049, 73, -1972) was being sent to clients during chunk load before the first sweep could fire. Now it dies on tick 1 regardless of context.

[1.7.4]

Fixed

• Generations-Core crash on join — Added data/cca_compat_fixes/function/clear_unknown_pokemon.mcfunction (hooked into #minecraft:load) that kills all cobblemon:pokemon entities named ??? ♀, ??? ♂, or ???. These unresolvable-species entities cause kotlin.UninitializedPropertyAccessException: lateinit property species has not been initialized in Generations-Core's RareCandyBone.renderModel(), crashing the client render thread immediately on join. The function fires on every /reload and server start, clearing any such entity before it can be rendered.
• Tick-based cleanup sweep — Added data/cca_compat_fixes/function/tick_cleanup.mcfunction (hooked into #minecraft:tick) that re-runs the unknown-species sweep once every 24,000 ticks (~20 min) as a persistent safety net in case new unresolvable entities spawn from a bad spawn pool.
• megashowdownores block loot table errors (21 tables) — Added empty stub overrides under data/megashowdownores/loot_table/blocks/ for all 21 megashowdownores:blocks/* ore loot tables that failed to parse on startup (dreadrock_mega_ore, deepsoil_fossil_ore, depthrock_mega_ore, gloomslate_dynite_ore, holystone_dynite_ore, depthrock_zium_ore, dreadrock_zium_ore, shiverstone_mega_ore, sculk_stone_dynite_ore, holystone_zium_ore, shiverstone_zium_ore, dreadrock_dynite_ore, meteoroid_mega_ore, gloomslate_zium_ore, aether_fossil_ore, sculk_stone_mega_ore, holystone_mega_ore, shiverstone_dynite_ore, gloomslate_mega_ore, depthrock_dynite_ore, sculk_stone_zium_ore). Items in these tables referenced megashowdownores:* items that are not registered because mega_showdown is not active.
• megashowdownores cross-mod recipe errors (9 recipes) — Added stub overrides under data/megashowdownores/recipe/ for all cross-mod recipes that referenced cobblemonff:* (Flawless Fossils, not installed), mysticalagriculture:* (not installed), and own ore items that aren't registered. Affected recipes: shapedcrafting/compat/flawlessfossils/shiny_fossil, perfect_fossil, generic_fossil; shapedcrafting/compat/mysticalcustomization/mega, zium, fossil; blasting/meteoroid_mega_shard_blast; smelting/meteoroid_mega_shard_smelt; shapelesscrafting/mms_to_dynite.
• farmingforblockheads:market apricorn seed recipe errors (7 recipes) — Added stub overrides under data/farmingforblockheads/recipe/cobblemon/ for the 7 apricorn seed market recipes (green_apricorn_seed, white_apricorn_seed, pink_apricorn_seed, blue_apricorn_seed, black_apricorn_seed, red_apricorn_seed, yellow_apricorn_seed) that failed because the server does not register the farmingforblockheads:market recipe serializer.
• minecraft:chests/inject/common_loot missing reference — Added an empty stub at data/minecraft/loot_table/chests/inject/common_loot.json to satisfy a loot table reference injected into minecraft:chests/common_loot that caused a validation warning every startup.

Not Actionable (documented)

• cobblemon:nautilus_shell unknown item warning — This item ID is hardcoded in rustlingspots-fabric-4.1.jar's compiled LootPoolService.class. Not fixable via datapack.
• croptopia:botanypots/* recipe errors — These recipes are defined in the Croptopia mod JAR itself, not in any overrideable data path.
• farmersdelight:chests/* loot injection warnings — FarmersDelight JAR-level injection into vanilla loot tables. Cannot be removed without breaking FD clients.