Modpack and Server Config

This page is for modpack authors, server admins, and players who want to tune RTSBuilding survival rules.

Regular players can start with RTS Plugins and Survival Balance and RTS Home and Range.

Know Which Settings Screen You Are Using

The gear button inside the RTS interface is for personal control and visual preferences. It mainly changes camera feel, UI scale, auto-store, preview animations, and other local player settings.

Modpack and server rules are not edited from that RTS gear panel. They live in the RTSBuilding mod configuration.

There are two config entry points:

• In game: open Minecraft's Mods list, choose RTSBuilding, then open its Config page.
• File: edit config/rtsbuilding-common.toml in the instance or dedicated server folder.

On multiplayer servers, the server's config/rtsbuilding-common.toml is authoritative. A client-side local file only affects singleplayer or local testing and does not override server rules.

After editing the dedicated server file, restart the server so all players use the same rules.

Key Rule Options

The mod config page or rtsbuilding-common.toml can tune these rules:

• enableSurvivalProgression: enables survival balancing, RTS plugin unlocks, RTS Home, and radius limits.
• shareSurvivalProgressionWithTeams: shares RTS Home and team plugins with multiplayer teams. It prefers FTB Teams, then Open Parties and Claims parties, then vanilla scoreboard teams.
• maxActionRadiusBlocks: maximum RTS action radius. The current range is 48 to 512 blocks.
• enableBlueprints: enables the blueprint library, local blueprint upload, and server-side blueprint placement.
• maxBlueprintBlocks: maximum non-air blocks allowed in one blueprint import, capture, or placement job.

When shipping both a client pack and a server pack, put the server-side rules into the server pack's config/rtsbuilding-common.toml. Do not rely on the client instance alone.

Tune Plugin Acquisition

The current survival system uses real items to control abilities. Modpack authors should decide when players receive plugins through recipes, quest rewards, shops, or loot tables.

Each plugin is a normal item, for example:

• rtsbuilding:rts_control_core
• rtsbuilding:remote_control_plugin
• rtsbuilding:storage_integration_plugin
• rtsbuilding:blueprint_plugin
• rtsbuilding:range_culling_plugin
• rtsbuilding:range_extension_i
• rtsbuilding:range_extension_ii
• rtsbuilding:range_extension_iii
• rtsbuilding:range_extension_max

To tune progression pace, edit these plugin item recipes first, or award plugins through your quest system. The current production flow is based on plugin items.

Only one range extension can be installed at a time, so modpacks can treat them as mutually exclusive upgrade tiers.

OpenPAC and Claim Protection

If Open Parties and Claims is installed, RTSBuilding tries to use OpenPAC for:

• party-based team sharing.
• claim checks for RTS placement, breaking, block interaction, and entity interaction.

This means players cannot use remote RTS building to bypass someone else's claim. If OpenPAC is not installed, these checks are skipped naturally and normal singleplayer or no-claim servers keep working.