Config options for rescaling media costs#1041
Open
Robotgiggle wants to merge 6 commits into
Open
Conversation
Robotgiggle
changed the title
ChuijkYahus
added a commit
to ChuijkYahus/HexMod
that referenced
this pull request
May 11, 2026
Robotgiggle
changed the title
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
1 participant
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.
Adds a list in the config that can be used to rescale the cost of any action. Entries consist of a resource location and a number (ie
hexcasting:explode 2.5) and the cost of the listed action is scaled by the listed number.Also adds a config value with a global scaling factor that will apply to all media costs, if you just want to apply an overall buff or nerf to hex in your pack/server.
Both of these scaling factors apply before the
media_consumption_modifierattribute. The global scaling factor is not applied to anything in thecannot_modify_costtag, so that making everything cheaper doesn't immediately introduce a bunch of exploits. However, entries in the per-action list for actions in that tag do still work, in case for whatever reason you actually do want to rescale one of those patterns.