Menu
Use when setting up a new FS25 mod for development, creating symlinks to the mods folder, packaging a mod as zip, or configuring modDesc.xml fields like author and descVersion.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when working with I3D files, understanding the I3D scene graph, node types, materials, shapes, user attributes, collision flags, or transform hierarchy.
Use when creating or modifying FS25 map mods, configuring map.xml, terrain, placeables, farmlands, ground types, or fruit types.
Use when debugging FS25 mods, reading log.txt errors, troubleshooting crashes, fixing common mod issues, or using console commands.
Use when working with FS25 textures, DDS formats, normal maps, specular maps, texture naming conventions, or resolution guidelines.
Use when creating or modifying FS25 vehicle mods, configuring vehicle XML, specializations, attacherJoints, wheels, movingTools, movingParts, lights, or sounds.
Use when working with fs-utils CLI tools — decompiling Luau/LuaJIT bytecode, extracting GAR/DLC archives, unlocking shapes files, or formatting XML.
| name | fs25-mod-deploy |
| description | Use when setting up a new FS25 mod for development, creating symlinks to the mods folder, packaging a mod as zip, or configuring modDesc.xml fields like author and descVersion. |
Handles the full lifecycle of deploying FS25 mods: dev links for live editing, correct zip packaging for distribution, and modDesc.xml standards.
| Platform | Path |
|---|---|
| Windows | %USERPROFILE%\Documents\My Games\FarmingSimulator2025\mods\ |
| macOS | ~/Library/Application Support/FarmingSimulator2025/mods/ |
Game log is in the same parent directory as mods/, named log.txt.
Detect the platform and use the correct path automatically.
For active development, link the mod folder into the game's mods directory. Changes are picked up immediately without copying.
macOS:
ln -s /absolute/path/to/FS25_ModName "<MODS_FOLDER>/FS25_ModName"
Windows (requires admin or Developer Mode):
mklink /D "%USERPROFILE%\Documents\My Games\FarmingSimulator2025\mods\FS25_ModName" "C:\path\to\FS25_ModName"
Contents must be at the root level of the zip — no nested folder.
macOS:
cd /path/to/FS25_ModName && zip -r ../FS25_ModName.zip . -x "*.DS_Store"
Windows (PowerShell):
Compress-Archive -Path "C:\path\to\FS25_ModName\*" -DestinationPath "C:\path\to\FS25_ModName.zip"
| Correct | Wrong |
|---|---|
zip root contains modDesc.xml | zip root contains FS25_ModName/modDesc.xml |
Common mistake: Zipping the folder itself instead of its contents creates a nested structure. Always zip the contents, not the folder.
<modDesc descVersion="106">
<author>YOUR NAME HERE</author>
<!-- ... -->
</modDesc>
106 (current as of FS25 patch 1.5)| Task | macOS/Linux | Windows |
|---|---|---|
| Link mod | ln -s /path/to/mod "<MODS>/FS25_Name" | mklink /D "<MODS>\FS25_Name" "C:\path\to\mod" |
| Package zip | cd mod && zip -r ../FS25_Name.zip . -x "*.DS_Store" | Compress-Archive -Path "mod\*" -DestinationPath "FS25_Name.zip" |
| Verify zip | unzip -l FS25_Name.zip | head | Expand-Archive -Path FS25_Name.zip -ShowList (or 7zip) |
| Check log | tail -50 "<MODS>/../log.txt" | Get-Content "<MODS>\..\log.txt" -Tail 50 |
| Remove link | rm "<MODS>/FS25_Name" | rmdir "<MODS>\FS25_Name" |