Community-managed game server configuration data for the NexLink Core Panel. This repository powers the configuration options, mod mappings, and error detection in the server management panel.
Anyone can contribute! Submit a pull request to update configurations, add new mod creatures, flag new map mods, or add startup error patterns. An admin will review and merge your changes.
game-config-data/
palworld/
settings/ # PalWorldSettings.ini OptionSettings (split by group)
01-server.yaml
02-world.yaml
03-combat-pvp.yaml
04-survival.yaml
05-capture-pals.yaml
06-gathering-drops.yaml
07-base-guild.yaml
08-network-misc.yaml
startup-errors.json # Console error detection patterns
path-of-titans/
game-ini/ # Game.ini settings (split by section)
01-general-server.yaml
02-quest-system.yaml
03-waystone.yaml
04-chat-communication.yaml
05-map-navigation.yaml
06-whitelist-permissions.yaml
07-growth-survival.yaml
08-nesting-family.yaml
09-death-respawn.yaml
10-critters-burrows.yaml
11-home-cave.yaml
12-player-lifecycle-security.yaml
13-character-management.yaml
14-weather-system.yaml
15-water-environmental.yaml
16-network.yaml
server-variables-schema.yaml # Server startup variable schema
map-mods.txt # List of mods that are map replacements
mod-creatures.csv # Mod creature name-to-author mapping
startup-errors.json # Console error detection patterns
Each YAML file defines the settings for one section of the Game.ini configuration editor. Files are numbered to control display order — rename the prefix to reorder sections.
# Example: 01-general-server.yaml
settings:
- property: ServerMap # INI property name
label: Server Map # Display name in the UI
type: select # Input type: select, number, text, checkbox
default: Island # Default value
helpText: The map to use # Help text shown to users
section: "[/Script/PathOfTitans.IGameSession]" # INI section
accordion: General Server Settings # UI grouping
accordionOrder: 0 # Group display order
order: 0 # Setting display order within group
options: # For select type only
- Island
- PanjuraSupported types: select, number, text, checkbox
Optional fields: min, max, step (for numbers), options (for selects), repeatable, fullWidth, dependsOn
To add a new setting: Edit the appropriate section file and add a new entry to the settings array.
To reorder sections: Rename the number prefix (e.g., rename 05- to 03- to move it earlier).
To add a new section: Create a new numbered YAML file (e.g., 17-new-section.yaml) with the same format.
Same YAML format as the Path of Titans game-ini/*.yaml files, but the settings
map into Palworld's single OptionSettings=(...) line under
[/Script/Pal.PalGameWorldSettings] in PalWorldSettings.ini. You only list
each property (the OptionSettings key) — the panel's Palworld parser handles
packing them into that line.
# Example: palworld/settings/02-world.yaml
name: World & Progression
settings:
- property: ExpRate
section: "[/Script/Pal.PalGameWorldSettings]"
label: EXP Rate
type: number
default: 1
step: 0.1
min: 0.1
max: 20
helpText: Multiplier for all experience gained.Server variables vs. OptionSettings: entries tagged configType: server-variable
are Pterodactyl startup variables (Server Name, passwords, Max Players, Auto
Update), not OptionSettings.
⚠ Do not add OptionSettings for
ServerName,ServerDescription,ServerPassword,AdminPassword,ServerPlayerMaxNum,PublicPort, or the RCON fields. The server image'sPalworldServerConfigParserinjects those intoPalWorldSettings.inifrom the startup variables on every boot, so any value set in the.inieditor would be overwritten. They are exposed as startup variables instead.
Defines server startup variables (like server name, slots, password).
serverVariables:
- property: SERVER_NAME # Variable name
label: Server Name # Display name
type: text # text or number
default: My Server # Default value
helptext: Your server name # Help text
accordion: Server Settings # UI grouping
accordionOrder: 0
order: 0Same field types as game-ini files but uses serverVariables: as the root key.
Simple list of mod SKUs that are map replacement mods (one per line). These mods appear in the ServerMap dropdown instead of the regular Mods tab.
# Mods listed here appear in the ServerMap dropdown
UGC_M_Y250G15EVZ_SK
UGC_M_DYV7XD5EGX_SK
To add a new map mod: Add the mod's SKU on a new line.
Maps mod creature names to their author/mod pack and SKU. Used by the Growth Calculator to filter creatures by enabled mods.
creature,author,sku
AbsentiaAcro,Absentia,UGC_M_NV57RV2EJD_SK
Camarasaurus,Ancient Gods,UGC_M_DYV7XQ60GX_SKTo add a new creature: Add a new row with CreatureName,AuthorName,SKU.
Patterns matched against server console output during startup. When a match is found, users see the configured warning/error message.
[
{
"id": "pot-restricted-mod",
"patternSource": "Mod .* is restricted",
"message": "A restricted mod was detected. Remove it from your mod list.",
"severity": "error",
"helpUrl": "https://docs.example.com/restricted-mods",
"games": ["path-of-titans"]
}
]Fields:
id- Unique identifier (usepot-prefix for Path of Titans)patternSource- Regex pattern to match in console output (escape special characters)message- User-friendly message shown when pattern matchesseverity-"error","warning", or"info"helpUrl- (optional) Link to documentation or help pagegames- Array of game IDs this pattern applies to
- Fork this repository
- Edit the relevant file(s)
- Submit a pull request with a description of your changes
- An admin will review and merge
- Keep YAML files properly indented (2 spaces)
- Keep JSON files valid (use a linter if unsure)
- For mod creatures, use the exact creature name as it appears in-game
- For startup errors, test your regex pattern against real console output
- One change per pull request when possible (easier to review)
Mod SKUs follow the pattern UGC_M_<CODE>_SK. You can find them:
- In your
GameUserSettings.iniunder[ServerGameMode] - In the mod details on the Alderon Games mod browser
- In the server's Mods tab in the panel
The NexLink Core Panel fetches these files directly from this repository (via raw.githubusercontent.com). Changes are cached for up to 1 hour, and admins can manually refresh the cache from the panel.
This means your contributions are live within an hour of being merged, with no code deployment needed.