Apply to both supported tracks: Minecraft 1.21.1 and the Minecraft 26.3 port.
Remove Nether-style biomes from Native biome generation on Cave terrain. Native Cave Ages should select recognized non-Nether cave biomes rather than mixing in Nether biomes merely because Rivencraft recognizes them as valid Cave-terrain authoring choices.
This is a deliberate behavior change from the current 1.21.1 Native Cave pool and the recently ported 26.3 behavior (local 1.0.1.97-beta.1).
Intended behavior
Separate the Native Cave default pool from the broader pool of biomes legally authorable on Cave terrain.
Exclude vanilla Nether biomes and recognized modded Nether-style biomes, using registry tags and the applicable optional integration classification rather than a hardcoded mod-specific list. A biome classified as both Cave and Nether must still be excluded from Native selection.
Retain eligible non-Nether cave biomes, including new vanilla cave biomes and recognized modded cave biomes.
Apply this to an explicit Native controller, an omitted controller that resolves to Native, and a fully random Cave Age that resolves to Native.
Preserve explicit Nether biome authoring on Cave terrain through the supported non-Native controllers. Do not globally remove Nether biome pages, mark them unsupported, or change Nether material rules.
Keep other terrain types and non-Native distribution behavior unchanged unless separately requested.
Acceptance checks
On both versions, newly generated Native Cave pools contain no vanilla or recognized modded Nether-style biomes.
Native Cave still produces multiple eligible cave biomes when available and has a safe non-Nether fallback if its eligible pool is empty or has one entry.
Explicitly authored Nether biome Cave books still bind and generate correctly, with their native materials where supported.
Verify explicit Native, seed-completed Native, fully random Native Cave selection, optional-mod absence, a biome mod with Nether regions, reload/restart, and saved pool persistence.
Document the migration policy for existing frozen Native Cave pools; do not silently conflate this with explicit Single/Tiled/region biome choices.
Update relevant Native/Cave page tooltips, writing documentation and wiki when implemented.
Requested by the user after validating the Native Cave distribution port. This issue records future work only; no implementation change is requested in this turn.
## Scope
Apply to both supported tracks: **Minecraft 1.21.1** and the **Minecraft 26.3 port**.
Remove Nether-style biomes from **Native biome generation on Cave terrain**. Native Cave Ages should select recognized non-Nether cave biomes rather than mixing in Nether biomes merely because Rivencraft recognizes them as valid Cave-terrain authoring choices.
This is a deliberate behavior change from the current 1.21.1 Native Cave pool and the recently ported 26.3 behavior (local 1.0.1.97-beta.1).
## Intended behavior
- Separate the Native Cave default pool from the broader pool of biomes legally authorable on Cave terrain.
- Exclude vanilla Nether biomes and recognized modded Nether-style biomes, using registry tags and the applicable optional integration classification rather than a hardcoded mod-specific list. A biome classified as both Cave and Nether must still be excluded from Native selection.
- Retain eligible non-Nether cave biomes, including new vanilla cave biomes and recognized modded cave biomes.
- Apply this to an explicit Native controller, an omitted controller that resolves to Native, and a fully random Cave Age that resolves to Native.
- Preserve explicit Nether biome authoring on Cave terrain through the supported non-Native controllers. Do not globally remove Nether biome pages, mark them unsupported, or change Nether material rules.
- Keep other terrain types and non-Native distribution behavior unchanged unless separately requested.
## Acceptance checks
- On both versions, newly generated Native Cave pools contain no vanilla or recognized modded Nether-style biomes.
- Native Cave still produces multiple eligible cave biomes when available and has a safe non-Nether fallback if its eligible pool is empty or has one entry.
- Explicitly authored Nether biome Cave books still bind and generate correctly, with their native materials where supported.
- Verify explicit Native, seed-completed Native, fully random Native Cave selection, optional-mod absence, a biome mod with Nether regions, reload/restart, and saved pool persistence.
- Document the migration policy for existing frozen Native Cave pools; do not silently conflate this with explicit Single/Tiled/region biome choices.
- Update relevant Native/Cave page tooltips, writing documentation and wiki when implemented.
Requested by the user after validating the Native Cave distribution port. This issue records future work only; no implementation change is requested in this turn.
dnorberg
added this to the Dual-version support milestone 2026-11-05 14:51:04 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Scope
Apply to both supported tracks: Minecraft 1.21.1 and the Minecraft 26.3 port.
Remove Nether-style biomes from Native biome generation on Cave terrain. Native Cave Ages should select recognized non-Nether cave biomes rather than mixing in Nether biomes merely because Rivencraft recognizes them as valid Cave-terrain authoring choices.
This is a deliberate behavior change from the current 1.21.1 Native Cave pool and the recently ported 26.3 behavior (local 1.0.1.97-beta.1).
Intended behavior
Acceptance checks
Requested by the user after validating the Native Cave distribution port. This issue records future work only; no implementation change is requested in this turn.
Lets also create a Native Nether page and a Native End page with their respective biome generations.