All the Mods 10 - ATM10

All the Mods 10 - ATM10

Modpacks
166k Downloads

[Bug]: Time wand cannot go to max speed with current config

jpenilla opened this issue ยท 4 comments

commented

Possible Fixes

Yes

Modpack Version

0.41

What happened?

The time wand from JDT cannot go to the max 256x multiplier (mentioned in the dire book) with the current config, it maxes out at 128x.
This is because in the config energy use is set to 750rf, which means for 128x it uses 96,000 rf, and for 256x it would need 192,000 rf. However, the max storage of the wand is set to 100,000 rf. My suggestion is to raise the max rf in the wand to 200,000 rf or higher.

ATM-10/config/justdirethings-common.toml

Lines 191 to 201 in b9810eb

#Time Wand
[time_wand]
#The maximum amount of Forge Energy the Time Wand can hold in its buffer
#Range: > 1
time_wand_rf_capacity = 100000
#The Forge Energy cost to use the Time wand. This value is multiplied by the acceleration amount. For example, when you go from 128 to 256, it will charge 256 x <this value> in FE cost.
#Range: > 0
time_wand_rf_cost = 750
#The Time Fluid cost to use the time wand. This value is multiplied by the acceleration amount. For example, when you go from 128 to 256, it will charge 256 x <this value> in Time Fluid.
#Range: 0.0 ~ 1.7976931348623157E308
time_wand_fluid_cost = 0.5

latest.log

No response

Developer reports

No response

commented

JDT v1.2.3 includes my PR adding a time_wand_max_multiplier config option, this should allow the ATM team to nerf the wand without the book and renderer becoming inaccurate.

commented

Maybe it would be good to open a feature request at JDT for a dedicated max multiplier config then, to avoid confusion with the book not matching in-world behavior.

Or could have JDT do the math to determine the real max from the other options.

commented

The reason for the config change was to nerf the max acceleration to 128x...