Removed ability to set charge cost limit to 0. Changed max value for multiplier to 100 from integer max.

This commit is contained in:
2022-01-18 21:54:38 +00:00
parent 2c8e0595fc
commit 66bdaa5a30

View File

@ -80,12 +80,11 @@ public final class Config {
"Higher values set the charge cost to static, meaning that this will be the amount of charges needed to revive someone.") "Higher values set the charge cost to static, meaning that this will be the amount of charges needed to revive someone.")
.defineInRange("chargeCost", chargeCost, -1, Integer.MAX_VALUE); .defineInRange("chargeCost", chargeCost, -1, Integer.MAX_VALUE);
CHARGE_COST_LIMIT = builder CHARGE_COST_LIMIT = builder
.comment("The max amount of charge this totem can hold at once.\n" + .comment("The max amount of charge this totem can hold at once. Only works with dynamic cost.")
"0 means unlimited. Only works with dynamic cost.") .defineInRange("chargeCostLimit", chargeCostLimit, 1, Integer.MAX_VALUE);
.defineInRange("chargeCostLimit", chargeCostLimit, 0, Integer.MAX_VALUE);
CHARGE_COST_MULTIPLIER = builder CHARGE_COST_MULTIPLIER = builder
.comment("Charge cost multiplier. 0.5 means the charge cost will be 50% of the original cost. Only works with dynamic cost.") .comment("Charge cost multiplier. 0.5 means the charge cost will be 50% of the original cost. Only works with dynamic cost.")
.defineInRange("chargeCostMultiplier", chargeCostMultiplier, 0.01, Integer.MAX_VALUE); .defineInRange("chargeCostMultiplier", chargeCostMultiplier, 0.01, 100);
CAN_REVIVE_MORE_EXPENSIVE_TARGETS = builder CAN_REVIVE_MORE_EXPENSIVE_TARGETS = builder
.comment("Is the totem able to revive targets that cost more than the totems max charge?\n" + .comment("Is the totem able to revive targets that cost more than the totems max charge?\n" +
"This only applies if the totem is fully charged. (dynamic wont work if limit is 0)") "This only applies if the totem is fully charged. (dynamic wont work if limit is 0)")