Nether Ore Generation is Hardcoded Despite Data-Driven Support in Bedrock Edition

Nether ores (e.g., ancient debris, nether quartz) currently use hardcoded generation rules in Bedrock Edition, even though the engine fully supports data-driven feature generation through stable behavior pack APIs. This limitation forces marketplace content creators to work around inflexible systems instead of using standardized JSON-based feature definitions.

How to Reproduce:

1. Inspect definitions/features and definitions/feature_rules folders

2. Note the absence of JSON files for nether ore generation

3. Compare with overworld ore generation which uses proper data-driven systems

Observed Result:

• No data-driven feature rules exist for nether ores

• All nether ore generation controlled by engine hardcoding

• Marketplace packs cannot modify ore generation through standard systems

Expected Result:
Nether ore generation should use data-driven feature rules like overworld ores, with proper definitions in:

• definitions/features/netherxxx

• definitions/feature_rules/netherxxx