Minecraft Version

1.19.3

Mod Loader

Forge

Mod Loader Version

44.1.17

Mod Version

12.2.0

Balm Version

5.0.0

Describe the Issue

I am hosting a 1.19.3 modded server. There is no serverconfig waystones file. Only the waystones-common.toml. So whatever xp cost or cooldowns that I set in the file do not apply to all clients unless they receive an updated copy of the config. They are also able to make these changes themselves, which could result in some undesirable effects. Is it possible to please make a mcserver/world/serverconfig/waystones-server.toml ? That way the players will have the settings that I have set without having to go an extra step and send them the config aswell. This way they can't make these teleports cheaper and what not.

Logs

No logs needed as there is no crash any everything works.

Do you use any performance-enhancing mods (e.g. OptiFine) or custom server distributions (e.g. SpongeForge)?

Optifine yes, no issue just no server-enforced config file per world.

This is incorrect, relevant options from waystones-common.toml are synced to clients and the server holds authority on those options, though your Balm version is outdated and should be updated to fix some unrelated issues regarding the config sync.

Issue fixed temporarily but it is back regenerating a new waystones-common file as of tonight, nothing has changed about the server since we fixed it by updating the balm version.

That seems to be a completely different issue than what was first described.

Configs reset to their default if they are deemed "corrupt", i.e. not matching the config spec. Waystones uses Forge's config system, so any resetting is done by Forge and Waystones has no control over it. I suggest checking the logs for mentions of "correcting" and see if the log gives any hints as to when and why it happens.

That seems to be a completely different issue than what was first described.

Configs reset to their default if they are deemed "corrupt", i.e. not matching the config spec. Waystones uses Forge's config system, so any resetting is done by Forge and Waystones has no control over it. I suggest checking the logs for mentions of "correcting" and see if the log gives any hints as to when and why it happens.

Yeah, I don't see anything in there. This is still going on, I've had the players delete their configs. Also the waystones-common file should be in the config folder yeah or the world config folder or ?.... Because this is just getting annoying for them.

The players configs match the server's it's just not syncing properly or something.

By the way can this be server side or do all the clients need the mod?

Does this have anything to do with this?
[07Apr2023 16:00:20.795] [main/WARN] [net.minecraft.server.packs.repository.Pack/]: Missing metadata in pack t_and_t_waystones_patch_1.19.2.zip

we're not even on 1.19.2

The mod needs to be installed on both client and server and both Balm and Waystones versions should match between client and server. The config file should be within the normal config folder, Waystones does not use the world config folder. t_and_t_waystones_patch_1.19.2.zip seems to be an optional datapack adding Waystones to structures, but it wouldn't have any effect on the configs.