FoXyStarterKit
Current Version: 1.1 ⚠️ SERVER-SIDE MOD ONLY Subscribe on the Workshop, then copy the mod folder to your server and add it to your -serverMod= launch parameter - NOT -mod=. Players do NOT need to download this mod. What is FoXyStarterKit? FoXyStarterKit gives new players a one-time starter kit claimed via a simple chat command. Define exactly what players receive - containers, tools, weapons, base building supplies… (more)
Current Version: 1.1 ⚠️ SERVER-SIDE MOD ONLY Subscribe on the Workshop, then copy the mod folder to your server and add it to your -serverMod= launch parameter - NOT -mod=. Players do NOT need to download this mod. What is FoXyStarterKit? FoXyStarterKit gives new players a one-time starter kit claimed via a simple chat command. Define exactly what players receive - containers, tools, weapons, base building supplies - with full control over every item, attachment, and nested sub-item. Usage is tracked per SteamID so each player can only claim once. Loadout Modes Two ways to define what players receive: Custom Loadout - Define items directly in the JSON config with full control over classnames, attachments, sub-items, health, quantity, liquid type, temperature, local position, and rotation. Supports nested containers (e.g. a Sea Chest filled with tools and a flag kit). This is the default mode and requires no other mods. CoT Loadout - Point the config at any saved Community Online Tools loadout file by name. If the CoT file is missing or fails, the mod automatically falls back to the custom loadout. Admins can type !loadouts in chat to list all available CoT loadout files on the server. Safety Checks Before spawning a kit, the mod verifies the player is: • Not inside a vehicle • Standing on solid ground (not swimming or airborne) • Not inside a custom restricted zone (configurable by name, position, and radius) All checks produce clear in-game notifications explaining why the kit was denied. Expansion Integration Optional Expansion checks, each independently toggled: • Block kit use inside Expansion territories • Block kit use inside Expansion safe zones • Block kit use inside Expansion no-build zones • Block kit use near active Expansion airdrops When Expansion is not installed these checks are safely skipped. Notifications automatically use Expansion toast style when available, otherwise vanilla notifications are used. Discord Integration Real-time webhook notifications when a player claims their kit: • Player name, SteamID, and coordinates • Full list of items spawned and any that failed • Loadout source (Custom or CoT loadout name) • Configurable bot name, embed color, and logo URL • Rich embeds or plain text - individual fields can each be shown or hidden In-Game Admin Commands Manage everything in-game without editing files or restarting the server. Only whitelisted Steam IDs and CoT permission holders can use commands. • !foxystarterkit reload - Hot-reload config without restarting • !foxystarterkit delete <SteamID> - Reset a player's kit claim • !foxystarterkit wipe - Reset all kit claims (full database wipe) • !loadouts - List all available CoT loadout files Admin access via SteamID list in config and optionally CoT permissions (StarterKit.Admin). Configuration Config: $profile:\FoXyMods\FoXyStarterKit.json Logs: $profile:\FoXyMods\Logs\FoXyStarterKit.log Auto-generated with sensible defaults on first run. Key settings include customizable chat command prefix and name, minimum playtime requirement, unlimited custom restricted zones, fully customizable notification messages, and adjustable logging level. The JSON configuration auto-updates between mod versions - your settings are preserved automatically. Setup 1. Add FoXyStarterKit to your server mod list 2. Start the server once to generate the default config 3. Edit FoXyStarterKit.json to configure your loadout, zones, Discord webhook, and preferences 4. Restart or use !foxystarterkit reload to apply changes No map-specific dependencies. Works on any map. No required mods - Expansion and CoT integration is optional and auto-detected. Help FAQ - http:
Not analyzed yet
modperf has not read this mod's scripts, so there is no report and it is left out of any stack it appears in. 1 live server in the crawl publishes it.
The worker downloads the mod from the Workshop and reads its Enforce Script — nothing is executed. Usually a few minutes. This page then shows the report.