Mod integration

[skynyrd47]

Love what your team has come up with and excited to get to use it and watch it evolve. I have always used FS25_ContractorMod. It gives me more of a management style of play that is addicting. I set each worker up with their own vehicles and give them "houses" (i just park them at what a in map house). Any way there is a lot of role play involved and keeps me entertained and coming back.

Your mod fills the loneliness void of the game but can you see a way of integrating the contractor mod or something similar with some management or a way to hire and control, just use as a worker? If so could we go as far as picking uniforms, etc.

Just a thought, either way keep up the amazing work on these scripts. I just made on for native strobes and it kicked my butt. I ended up settling with what I got. So koodoos for getting this put together!

[XelaNull]

@skynyrd47 I appreciate the tip on this. We do have a TODO item for exploring cross-mod compatibility.

@TheCodingDad-TisonK Please assign this one to me and I'll draft you up an integration proposal to review and approve before any coding gets written for this. This seems like high value opportunity.

[TheCodingDad-TisonK]

Seems like a good TODO indeed :)

[TheCodingDad-TisonK]

@XelaNull Can we add this? Or at least a a small start (not as prio)

[TheCodingDad-TisonK]

@XelaNull — went ahead and built an initial implementation based on the ContractorMod API surface.

What was built (Phase 1 + 2):

• New module: src/scripts/ContractorModBridge.lua
• Detects g_contractormod on mission load — zero cost if ContractorMod isn't present
• Each active contractor worker is automatically registered as a named NPC in the favor system (acquaintance-level relationship to start, since they're hired crew not strangers)
• Worker positions sync every 5 s by polling g_contractormod.workers (no event hooks exist in ContractorMod)
• No duplicate 3D models — ContractorMod owns the visuals; we only layer on favor/relationship
• Relationship data persists across saves via stable uniqueId (contractor_<idx>_<name>)
• Workers added/removed from ContractorMod are reflected automatically

Phase 3 (interaction triggers) is still open — proximity/vehicle events generating favor changes. That's the interesting gameplay layer and a good next scope for you to define if you want to take it.

ContractorMod API ref: g_contractormod.workers (table), worker.name, worker.x/y/z, worker.currentVehicle, worker.active, cm:isEnabled().

[TheCodingDad-TisonK]

[TheCodingDad-TisonK]

[TheCodingDad-TisonK]

Phase 3 implemented — committed to development (ed8a7e3).

Two interaction triggers are now live in ContractorModBridge.lua:

Co-work proximity (contractor_cowork)
Player in a vehicle within 60m of an active worker → +1 relationship every 30 seconds of sustained proximity. Capped at +5/day per worker. Accumulator resets if the player leaves range or exits the vehicle, so drive-bys don't count — you need to actually be working alongside them.

Daily greeting (contractor_greeting)
Player on foot within 8m of a worker → +2 relationship, once per game-day per worker. Natural reward for walking out to check on your crew.

Both triggers route through NPCRelationshipManager:updateRelationship() so mood modifiers, floating text, level-up notifications, and history logging all work automatically. Debug output gated behind debugMode.

Phase 3 scope is done. Leaving open in case you want to define follow-up triggers (e.g. worker completes a field job → favor event, worker crashes a vehicle → relationship penalty).

[TheCodingDad-TisonK]

Follow-up triggers added in 1f7215b. Closing.

Job completion (contractor_job_complete)
syncWorkers() now always syncs currentVehicle state (was sticky before — only ever set to non-nil, never cleared). The non-nil → nil transition fires onWorkerJobComplete: +3 relationship, capped at 3x/day per worker.

Vehicle crash (contractor_crash)
updatePhase3() checks vehicle:getDamageAmount() each second. If damage spikes from below 0.5 to ≥ 0.5 in a single poll cycle, it fires onWorkerCrash: -3 relationship. Fires once per vehicle assignment — reset when the worker gets a new vehicle.

Bug fixed along the way: npc.currentVehicle was never cleared when a worker stopped working, so job-complete detection would have been impossible. Fixed to always mirror worker.currentVehicle (nil included).

[skynyrd47]

This is awesome! How did I miss all this progress, thank you for tying these two mods together. I will give it a go as soon as I get back in town,