Yet Another Config (YACL) On Servers

Client Settings Versus Server Settings

Client settings govern your own experience: interface behaviour, visual options, and local preferences. They live in your instance and travel with you between servers, because they describe your game, not the world.

Server settings govern gameplay that everyone shares, such as feature switches and balance values. Those live on the server, and your local file cannot override them, however carefully you edit it.

Key points:

• Client settings: interface, visuals, local preferences
• Server settings: shared gameplay rules and feature switches
• Your client file cannot override a server rule

What The Library Does On A Server

On a server, the library gives mods a consistent way to load and manage their configuration without a graphical screen. There is no menu on a headless server; the configuration file itself is the interface.

Server owners edit those files directly, restart or reload as the mod instructs, and the values apply to everyone who joins. The YACL configuration guide explains the file formats most mods use.

Do Players Need It To Join A Server?

Joining a server never requires this library by itself. You need it in your own folder only when a client side mod you run depends on it, which is the same rule as single player.

If the server requires certain mods, its instructions list their dependencies too. Match those versions to the server Minecraft version, not to your single player setup, when the two differ.

When Settings Sync, And When They Cannot

Some mods sync selected values from server to client so gameplay matches for everyone. When a value is synced, your local change may appear to revert, because the server copy wins at join time.

That behaviour is correct, not a bug. The settings not saving guide helps separate genuine saving faults from server sync doing its job.

Advice For Server Owners

Change configuration on a stopped server or follow the mod reload instructions exactly, keep a dated backup of the config folder, and announce gameplay affecting changes to your players.

Test configuration changes on a local copy with the same mod list before they reach the live server. Most configuration disasters come from untested edits on a running world, not from the library.

Configuration Etiquette For Players And Owners

Players can help their server by reporting configuration surprises with specifics: which menu, which setting, and what the server did instead. Owners can help players by publishing the gameplay settings that differ from single player defaults, so nobody tunes against a rule that was never theirs to change.

Yet Another Config keeps the technical boundary clean between client and server. Clear communication keeps the social boundary just as clean, and together they prevent most configuration arguments before they start.