Default Server Properties in FTB StoneBlock 4

Same as in the FTB Skies 2 1.22.0 guide

Default Server Properties is a very small utility mod, and it's built for modpack developers rather than players. It uses a mixin to let a pack ship its own default-server.properties file in the root folder of the pack. That file overrides how the game creates server.properties the first time.^[1]

The nice part is that the file only needs the properties the developer wants to change, like a default level type. The game's native loading fills in everything else.^[1]

How it works

If there is no default-used.marker in the local folder, the mod loads the data from default-server.properties and injects it into the normal creation of server.properties. That's the whole job.^[1]

In this pack

The pack includes version 21.0.1, shipped as the NeoForge jar default-server-properties-neoforge-21.0.1.jar.^[2]

You don't craft, unlock or set anything up with this mod. It only affects how a fresh server.properties gets created, so it matters if you host a server from the pack and want to know where the starting settings come from. It has no quests in this pack, and it isn't on the ATM Star path.^[1][2]

Unverified The sources don't say which specific properties this pack sets in its default-server.properties, so check that file in your own install if you need to know the starting values.

Same as in the FTB Skies 2 1.22.0 guide

Good news: there's nothing to craft for this one. Default Server Properties is a very simple mod that hooks into the game so a modpack developer can define a default-server.properties file in the root of the pack. That file overrides the normal creation of the server.properties file. It's typically used for things like a default level type.^[1]

The project page describes a configuration file, not items, so there is no crafting order to follow and no recipe to show you here.^[1]

What to do first

1. Create a default-server.properties file in the game's root folder.^[1]
2. Put in only the properties you want to change by default. The game's native loading takes care of the rest, so you don't need to copy the whole file.^[1]
3. Check that there is no default-used.marker in the local folder. If there isn't one, the mod attempts to load your default data and injects it into the normal creation of server.properties.^[1]

Same as in the FTB Skies 2 1.22.0 guide

This mod has no machines, multiblocks, power, fluids or item automation. It adds no items or blocks for you to handle. It's a very small mod that hooks into the game with mixins, and everything it does happens when a server's settings file is first created.^[1]

What it actually does

A modpack developer can put a file called default-server.properties in the root folder of the pack. The mod then overrides the game's normal creation of the server.properties file. The project page gives a default level type as a typical use.^[1]

The developer only has to list the properties they want to change. The game's own native loading takes care of every other setting, so the file doesn't need to be a full copy of server.properties.^[1]

How the setup works

1. Create a default-server.properties file in the game's root folder.^[1]
2. Check the local folder for a default-used.marker file. If there is none, the mod attempts to load the data from your default file.^[1]
3. The mod injects that data into the normal default creation of server.properties, and the game fills in the remaining properties itself.^[1]

Unverified The sources don't say which properties this pack sets in its default-server.properties, and no config files for this mod are available. They also don't say when the marker file is created or whether the mod writes it itself. Check the pack's own files if you need the exact values.

StoneBlock 4 1.21.0 ships Default Server Properties 21.0.1, and the mod has been in the pack since 1.0.0 or earlier. Here are the entries from the mod's own changelogs.^[3]

21.0.0

• The mod was ported to 1.21.^[4]
• It switched to the NeoForge version scheme, so its version number went from 86.0.0 to 21.0.0. The changelog apologises for the confusion, so don't be thrown if the number looks like it went backwards.^[4]

21.0.1

• Fixed issue #3, where the server marked the client as incompatible if the mod was not present on the client.^[5]

Unverified Pack changelog entries for this mod were not available to the sources here, so this history only covers the mod's own changelogs.