[Bug]: Farm 1 still doesn't exist in onStartMission!

[HamiltonLockhart42]

Description

Environment

Game: Farming Simulator 25 Dedicated Server

Game version: 1.16.0.2 b37953

ModDesc version: 106

Map: Yukon Back Country

Context: Fresh server reset / brand new savegame, mods re-added from scratch

Issue

On a fresh dedicated server start, UsedPlus logs a warning and then an error during mission startup indicating that Farm 1 does not exist yet.

The server still continues running and saves successfully afterward, but UsedPlus appears to be checking for Farm 1 too early during onStartMission.

Relevant log lines
onStartMission hook fired
2026-03-09 22:11:31.562 [UsedPlus] WARN: Farm check: g_farmManager=true, farm1=false
2026-03-09 22:11:31.563 [UsedPlus] ERROR: CRITICAL: Farm 1 still doesn't exist in onStartMission!

Additional related UsedPlus log lines

UsedPlus continues to hook save operations afterward and reports saving vehicle persistence data with zero farms / zero searches:

2026-03-09 22:41:19.414 [UsedPlus] WARN: saveToXMLFile hook: Saving to C:/SERVICES/ni11909842_2_local/lws25/profile/tempsavegame
2026-03-09 22:41:19.415 [UsedPlus] WARN: VehiclePersistence: Saved 0 searches across 0 farms to C:/SERVICES/ni11909842_2_local/lws25/profile/tempsavegame/usedPlusVehicles.xml
2026-03-09 22:41:19.417 [UsedPlus] WARN: saveToXMLFile hook: Complete
2026-03-09 22:41:28.435 Game saved successfully (savegame1).

These same save warnings repeat on later autosaves as well.

Expected behavior

UsedPlus should wait until farms are fully initialized before checking Farm 1 or initializing farm-based persistence data.

Actual behavior

UsedPlus logs:

Farm check: g_farmManager=true, farm1=false

CRITICAL: Farm 1 still doesn't exist in onStartMission!

Notes

I also saw performance warnings for UsedPlus GUI icon textures being in raw format:

Warning (performance): Texture profile/mods/FS25_UsedPlus/gui/icons/search.png raw format.
Warning (performance): Texture profile/mods/FS25_UsedPlus/gui/icons/sale.png raw format.
Warning (performance): Texture profile/mods/FS25_UsedPlus/gui/icons/inspect.png raw format.

These do not appear to be the main issue, but I’m including them in case they’re useful

Steps to Reproduce

Start a dedicated server with a fresh savegame

Load Yukon Back Country

Enable UsedPlus

Start the server

Check the server log during mission startup

UsedPlus Version

2.14.2.5

Other Mods Installed

FS25_0_MaterialProcessor — v1.3.4.0, FS25_0_TerraFarm — v1.1.2.0, FS25_0_TerraFarmMachines — v1.0.0.2, FS25_fillTypeExtender — v1.0.0.0, FS25_gameplay_Real_Vehicle_Breakdowns — v0.9.6.3, FS25_interactiveControl — v1.2.0.0beta1, FS25_JCB_Fastrac8330 — v1.0.0.0, FS25_JCB_Powerpack — v1.0.0.0, RGC_FS25_EDITS — v1.0.0.1, RGC_Productions — v1.0.0.3, RGC_Yukon_Back_Country_V2 — v2.0.0.1

Game Mode

Multiplayer (host)

Log File

Screenshots

No response

[XelaNull]

Fix Applied (v2.15.4.77)

Hey @RGCDave! Thank you for the detailed report -- the log lines and reproduction steps made this straightforward to diagnose.

Root Cause

In v2.9.0, we added a Farm 1 existence check before loading savegame data, assuming farms would always exist during onStartMission. This is true for singleplayer, but on dedicated servers with a fresh savegame, farms are created when players connect -- not when the server starts. The check blocked all savegame data loading on server startup.

What We Fixed (v2.15.4.77)

Removed the Farm 1 gate entirely. The savegame managers already handle missing files gracefully via XMLFile.loadIfExists -- the gate was unnecessary defensive code that created a bug on dedicated servers.

The CRITICAL: Farm 1 still doesn't exist in onStartMission! error will no longer appear.

Regarding the PNG Texture Warnings

The texture performance warnings:

Warning (performance): Texture profile/mods/FS25_UsedPlus/gui/icons/search.png raw format.

These are cosmetic warnings from the game engine suggesting PNG icons be converted to DDS format. They do not affect functionality and will be addressed in a future quality pass.

Could you please verify?

We believe this should resolve the startup error on your dedicated server. Could you please confirm when you have a chance? Thank you for taking the time to report this!

[XelaNull]

Auto-close notice: This issue has been marked as Fixed.

If the fix does not resolve your issue, please reply to this ticket within 3 days and we will reopen it.

If no response is received, this issue will be automatically closed. You can always reopen it later if needed.

⏰ 3 days remaining

[XelaNull]

⏰ 3 days remaining before this issue is automatically closed.

If the fix does not resolve your issue, please reply to keep it open.

[HamiltonLockhart42]

on further testing with the updated version, i have come across a new bug.
When joining a dedicated server, clients become stuck at the 100% loading screen. The server log reveals a Lua error in the UsedPlusMaintenance specialization during the network synchronization phase.

Error Log Snippet
Plaintext
2026-03-21 03:27:25.281 Warning: StreamWriteTimestamp only is allowed to be called before any other write calls.
2026-03-21 03:27:25.317 Error: Running LUA method 'update'.
profile/mods/FS25_UsedPlus/src/specializations/UsedPlusMaintenance.lua:1284: attempt to call missing method 'writeMaintenanceData' of table
Technical Analysis
The error is caused by a scope mismatch in the networking lifecycle functions. In UsedPlusMaintenance.lua, the helper functions readMaintenanceData and writeMaintenanceData are defined within the UsedPlusMaintenance table.

However, in the event listeners (onReadStream, onWriteStream, onReadUpdateStream, and onWriteUpdateStream), the code attempts to call these functions as methods of the vehicle instance using self:writeMaintenanceData(streamId). Because these functions are not injected into the vehicle's metatable, the vehicle instance does not recognize them, causing the script to crash and desync the network stream.

Proposed Fix
The calls in the synchronization functions should be updated to reference the UsedPlusMaintenance table directly while passing self as the first argument.

Location: UsedPlusMaintenance.lua (approx. lines 1250–1290)

1. Update onReadStream and onWriteStream
   Lua
   function UsedPlusMaintenance:onReadStream(streamId, connection)
   UsedPlusMaintenance.readMaintenanceData(self, streamId)
   UsedPlus.logTrace("UsedPlusMaintenance onReadStream complete")
   end

function UsedPlusMaintenance:onWriteStream(streamId, connection)
UsedPlusMaintenance.writeMaintenanceData(self, streamId)
UsedPlus.logTrace("UsedPlusMaintenance onWriteStream complete")
end
2. Update onReadUpdateStream and onWriteUpdateStream
Lua
function UsedPlusMaintenance:onReadUpdateStream(streamId, timestamp, connection)
if connection:getIsServer() then
if streamReadBool(streamId) then
UsedPlusMaintenance.readMaintenanceData(self, streamId)
end
end
end

function UsedPlusMaintenance:onWriteUpdateStream(streamId, connection, dirtyMask)
if not connection:getIsServer() then
local spec = self.spec_usedPlusMaintenance
if streamWriteBool(streamId, bitAND(dirtyMask, spec.dirtyFlag) ~= 0) then
UsedPlusMaintenance.writeMaintenanceData(self, streamId)
end
end
end

[XelaNull]

Status reopened: @HamiltonLockhart42 replied while this issue was in Fixed status.

Moving back to In Progress for further investigation. The auto-close countdown has been cancelled.

If this issue is resolved again, the countdown will restart fresh.