MODHUB / Forum

FS25: testing, optimization, and a pre-publication checklist for a mod

BackCreationsEnglishVisible
pEDITORIAL

Editorial check before release

MODHUB guide; sources checked on 26.10.2026. Below is a practical editorial checklist, not a promise of official approval by the GIANTS ModHub. For your own tests, record the actual result; don’t mark “verified” if the launch wasn’t performed.

1. Save a reproducible test setup

  • Record the exact game version, the mod version, and tool versions, the platform, and a list of active dependencies.
  • Test on a separate save. Do the initial baseline test launch without other mods, then add the required dependencies.
  • Check the actual release ZIP, not only the unpacked working folder. Don’t leave two active copies of the same mod.
  • Verify save/load, buying or placing, selling or deleting—only the actions your mod is supposed to support.

2. Read the log from the first related error

After a clean launch, find messages that relate to your package. An error about a missing resource or XML can cause following problems; dozens of identical lines do not mean dozens of different causes. Fix the cause, not just hide the messages. Before publishing the excerpt, remove the username, private paths, IP, tokens, and other personal data.

  • Mod is not visible: check the game, the ZIP structure, the availability of modDesc.xml, required dependencies, and the specific loading error.
  • Texture is missing: verify the path, the filename’s letter case, that the file exists inside the ZIP, and the material settings.
  • The object is offset or physics behaves strangely: check the parent transformations, pivot, and the parameters of the relevant nodes.
  • The problem only occurs with a third-party set: add mods in small groups to narrow down the conflict; don’t blame someone else’s mod without reproduction.

3. Optimize based on measurements

Compare the same scene, camera position, weather, and settings. Write down the difference between the baseline launch and the launch with your object. Average FPS without context does not explain what causes a drop. We don’t promise a universal “correct” polygon count or texture size: the budget depends on the mod type and the scene.

  • Check materials, duplicated textures, and the number of small separate objects—not just the overall ZIP size.
  • Plan LOD and rendering distances where it provides measurable benefit. Reducing complexity should not break the silhouette or the gameplay function.
  • Don’t make collision as detailed as a decorative model without a real need.
  • Don’t automatically upgrade all textures to 4K: check from what distance the player sees the surface.

4. Automatic checks and multiplayer

Run a compatible GIANTS TestRunner and analyze its report. As of the verification date, 0.9.23 requires FS25 1.25.0+, while 0.9.22 in the directory indicates 1.24.0+. Choose the tool based on the requirements. The absence of issues in an automatic test does not replace gameplay verification.

For a multiplayer claim, verify the same archive, compatible game versions, and dependencies on both client and server; second-player connection, required actions, and re-entry. If you write Lua, study the FS25 API and the client/server model; a local single-player launch does not prove network synchronization. Don’t claim console compatibility just because the mod works on PC: separate platform rules and the platform’s requirements apply.

5. A release that can be understood and reproduced

  • State the author, mod version, verified game version, dependencies, functions, and known limitations.
  • Add your own screenshots showing the real state of the mod. An AI illustration might be a concept, but it is not proof of how the mod looks in the game.
  • Describe the installation of your specific package. A ready single-mod ZIP and an assembly with multiple ZIPs are different cases; don’t recommend unpacking everything without exception.
  • Leave the required resources in the ZIP; remove backup copies, personal files, secrets, and unnecessary working materials.
  • Write a short changelog: what changed, how to verify the fixes, and whether actions with a save are required. Don’t promise compatibility with old saves without verification.

Bug report message template

Game / exact version:
Mod / version / source:
Platform and required dependencies:
Reproduction steps: 1) ... 2) ...
Expected result:
Actual result:
Cleaned log excerpt:
Result on a separate save:

Share one reproducible case and what you’ve already checked. At the start, one clear issue is more useful than a list of unverified accusations. Publishing a ready mod in our community is done via the mod-addition page; it is not an automatic publication on the official GIANTS ModHub.

Sign in