Reduce ore density on the maze danger ore maps#1577
Merged
Conversation
:scale_richness(multiplier[, ore_name]) multiplies the start and richness curves of a main-ores config, so presets can tune ore density relative to their shared source config instead of restating curves. Factory.patches() is a fluent builder for resource patches configs with the same contract as the main-ores API: add_patch appends a pure-resource perlin patch, scale adjusts richness and patch size, and an existing plain config can be wrapped for scaling without modifying it. The Omnimatter ore config moves to the factory (it mirrored the scrap config) so its presets can use the fluent API too. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Scrapworld and Omnimatter maze: main ore density to 25%, mining out room for the factory took too long. - Scrapworld maze: add occasional dense pure-stone patches. The big lakes are hard to fill with the small amounts of stone recovered from scrap (a 5% chance per mined unit, competing with rail and brick demand), so give groups a stone supply to mine for landfill. - Coal maze: halve the richness of the dense iron/copper/stone patches and double their size; the coal itself is fine. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Playtest tuning for the maze danger ore variants. The core problem: the ore field is so rich that groups never need to push more than a few corridors out — the maze layout ends up having no say in the gameplay. Lower density means more mining outward, more corridors explored, and the maze actually shaping the run.
Player feedback from the current maps:
Changes
Implementation
First commit extends the fluent main-ores factory so the presets can express all of this relative to their shared configs instead of restating curve numbers:
:scale_richness(multiplier[, ore_name])multiplies the start and richness curves of a main-ores config.Factory.patches()— a fluent builder for resource patches configs with the same contract as the main-ores API:add_patchappends a pure-resource perlin patch,:scale{richness=, size=}adjusts existing configs (wrapping shared plain configs without modifying them).Covered by new cases in the standalone
ore_configs.test.luaharness (all passing), and verified in-game on new maps for all three presets.🤖 Generated with Claude Code