Creator guide

ATS Mod Publishing Checklist: Files, Screenshots, Compatibility, and Release Notes

Use this pre-publish checklist to package, test, document, and present an American Truck Simulator mod with clear files, screenshots, compatibility, and notes.

Written by Louka, Polyfir Group co-founder

Expert review by Thomas, PolyFir Studios founder and ATS mod creator

Published · 9 min read

A publish-ready ATS mod is more than a working archive. A player must be able to identify it, understand what it changes, confirm compatibility, install it, and know what changed when you update it. Run this checklist on the exact file you plan to distribute, not only your development folder.

1. Freeze and inspect the release package

  • Export a clean release archive with only runtime assets and required metadata.
  • Remove source files, backups, test textures, logs, and operating-system metadata.
  • Give the file a stable name such as creator_mod-name_v1.2.scs.
  • Open the archive once and confirm there is no accidental extra parent folder.
  • Record the file size and keep a copy of the released package for rollback.

SCS recommends directories during development and compressed .zip or .scs packages for release. Its official Mod Manager documentation also defines the manifest fields available to standalone packages.

2. Complete the metadata players see

Check manifest.sii, the icon, and description as a set. The display name, author, package version, category, DLC dependencies, and compatibility declarations should agree with the public listing. Use an exact 276×162 JPG for the Mod Manager icon, as required by SCS.

Worked manifest example:
package_version: "1.2.0"
display_name: "Pacific Chrome Accessories"
author: "Northstar Mods"
category[]: "tuning_parts"

Only declare restrictive compatible_versions when the mod genuinely depends on a game version. SCS warns that unnecessarily narrow declarations can block a mod that still works after a hotfix.

3. Test a clean install

  1. Move your development copy out of the local mod directory.
  2. Install the final archive using the same steps a customer will follow.
  3. Start a clean test profile with only required dependencies and your mod enabled.
  4. Review game.log.txt for errors and warnings after loading and using every changed asset.
  5. Test a representative save, dealership or configuration flow, and a normal drive.
  6. Restart the game and repeat the critical path once.

If you need the player-facing flow, compare your package against our ATS mod installation guide.

4. Build a screenshot set that proves the product

Lead with the clearest complete view, then show the decisions a buyer needs to make. Capture images at a consistent aspect ratio and resolution, without unrelated UI or other creators' assets.

  • Cover: the whole mod in a readable environment.
  • Detail: close-ups of the highest-value modeling or texture work.
  • Variation: configurable options, paint states, lighting, or cabin views.
  • Context: the mod in normal gameplay, not only a studio scene.
  • Limitations: an honest view of any constraint users should understand.

Original example: for a five-option bumper pack, publish one three-quarter truck view, one close detail, a labeled grid of all five options, one night-lighting view, and one in-game configurator view. That set answers more buying questions than five nearly identical beauty shots.

5. State compatibility and requirements precisely

List the tested ATS version, required DLC, required base mod, known conflicts, load-order instruction, supported truck or trailer, and whether convoy use is supported. Say “tested on ATS 1.x” instead of “works on latest.” The former remains auditable after the next update.

6. Write release notes before uploading

A release note should let an existing user decide whether to update and tell support exactly what changed.

Release note template
Version 1.2.0 for ATS 1.x
Added: two paintable accessory variants.
Changed: optimized texture memory use.
Fixed: mirror clipping on day cab configurations.
Compatibility: requires the base truck; no load-order change.
Upgrade note: replace the previous archive; existing saves remain supported.

Final release gate

  • The final archive installs and loads on a clean test profile.
  • The game log has no new release-blocking errors.
  • Listing copy matches the package and visible screenshots.
  • Compatibility, dependencies, conflicts, and load order are explicit.
  • Version number and release notes match everywhere.
  • You retained the shipped file and test evidence.

Once every item is true, the release is ready for review, not merely ready to upload.