Waystones

Waystones

123M Downloads

Config file not working?

Lalo611 opened this issue ยท 5 comments

commented

Minecraft Version

1.17

Mod Loader

Forge

Mod Loader Version

37.0.103

Mod Version

8.1.4

Describe the Issue

I've read that in previews versions of the mod users didn't really read the full config file. I hope that it is not my case.
It doesn't matter how many times I use the command /reload or I restart the server I can't remove the xp withdraw from interdimensional warp through waystones or for warps for 1000+ blocks.

[xpCost]
	#Range: > 0
	blocksPerXpLevel = 0
	#Range: 0.0 ~ 1.7976931348623157E308
	globalWaystoneXpCostMultiplier = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	waystoneXpCostMultiplier = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	maximumBaseXpCost = 0.0
	#Range: > 0
	xpCostPerLeashed = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	portstoneXpCostMultiplier = 0.0
	#Range: > 0
	dimensionalWarpXpCost = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	warpStoneXpCostMultiplier = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	minimumBaseXpCost = 0.0
	inverseXpCost = false
	#Range: 0.0 ~ 1.7976931348623157E308
	sharestoneXpCostMultiplier = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	warpPlateXpCostMultiplier = 0.0
	#Range: 0.0 ~ 1.7976931348623157E308
	inventoryButtonXpCostMultiplier = 0.0

Logs

No response

Do you use any performance-enhancing mods (e.g. OptiFine)?

No response

commented

same thing for me with latest version of mod(waystones-8.2.0+0 for 1.17.1 forge) including blam mod(balm-1.8.0+0)

its like the config file is not even being read, and loading default values for all config... havent checked the world gen tho, i know before the waystones were not generating even being forced to generate... i think that issue was resolved in the update

commented

Got the same Bug. I believe sometimes when I set it everything to 0 and restart the server it just generated the default values in the config right next to my changed value.

commented

I am also fighting the same thing on my server, I just spent a couple hours with a support team trying to figure this out. I am running 8.2.0 for forge 1.17.1 and balm 1.8.0.

commented

i am having similar thing happen on my server

commented

Fixed in Balm 1.8.1