Big map. Big network. Fewer excuses.

Lesson 01

Design A Network You Can Explain

Large networks need an architecture. Divide the map mentally into regions: farms, towns, productions, field blocks, industrial areas and long-distance corridors.

Keep the main transport spine simple. Branch local traffic off it. Do not make every farm lane a shortcut between opposite corners of the map.

Lesson 02

Destination Folders

AutoDrive can organise destinations into folders. On a large map this is not cosmetic. It is navigation infrastructure.

Current AutoDrive can also cycle targets in folders for supported workflows. A logical folder structure therefore helps both humans and automation.

Lesson 03

Route Manager

The Route Manager lets you save, load and manage route-network data. Use it to move from “one fragile savegame” to an actual maintainable network workflow.

Give exported routes useful names and keep a clean master copy before major edits.

Lesson 04

Backups, Creator And Version

Large networks are assets. Treat them like assets.

1. Keep a known-good master.
2. Back up before large deletions or junction redesigns.
3. Record which map version the route belongs to.
4. Test a copy before replacing the working network.
5. Document major changes.

Current AutoDrive route data can store route version and creator information. Use that. “No idea which one this is” is not a versioning strategy.

Lesson 05

Multiplayer-Friendly Routing

Multiplayer adds drivers, latency, different vehicle choices and creative human decisions to a network that already had enough problems.

• Use obvious destination names.
• Keep shared yards predictable.
• Avoid routes that depend on one player's private parking habits.
• Test editing permissions and route sync before a long session.
• Agree who is allowed to make structural edits.

AutoDrive synchronises network data in multiplayer, but governance remains stubbornly non-automated.

Lesson 06

Multiple Targets And Repeated Logistics

AutoDrive supports multiple-target workflows and synchronisation options for drivers using the same folder. This becomes useful for repeated pickup/delivery work across productions and storage points.

Design the folder and destinations around the job: pickup locations together, delivery locations together, sensible parking at the end.

Lesson 07

Combine And Harvester Logistics

Current AutoDrive includes dedicated combine-unloader behaviour: following harvesters, approaching the pipe, unloading, exiting fields and delivering when fill thresholds are reached.

Settings include follow distance, pre-call level, field-exit behaviour, fruit avoidance, active unloading and options for additional unloaders.

Build the network around the job

• Safe field entry
• Clear field exit
• Delivery destination
• Return route
• Parking destination
• Enough room for full trailers

Combine logistics is where bad field access stops being a minor annoyance and becomes an all-day queue.

Lesson 08

Courseplay And AI Handoff

AutoDrive can hand vehicles to the Giants helper or Courseplay, and the current builds include specific cooperation improvements for refilling, parking and job transitions.

Think of the division of labour clearly: AutoDrive handles transport over the road network; Courseplay can handle fieldwork. The handoff point must be reachable, safe and appropriate for the field course.

Lesson 09

Automatic Refuel, Repair And Parking

AutoDrive can send vehicles to refuel or repair destinations when configured thresholds are reached, and can park vehicles at the end of supported jobs.

These service points must be reachable from the network and positioned close enough to the relevant trigger. Test them with the vehicles that will use them, not just the smallest tractor in the fleet.

Job → Service if required → Continue / Park

Lesson 10

Surviving Map Updates

Map updates can move roads, gates, triggers, productions or collision objects. Never assume an old route network remains valid because the XML still loads.

1. Back up the old working network.
2. Read the map changelog.
3. Check changed areas visually.
4. Run AutoDrive route debugging.
5. Test major corridors and every changed production or field access.
6. Update route version/notes before distribution.

On very large maps, test by region. Driving every road personally is admirable, but there are only so many hours in a human lifespan.

Route Doctor / Network Engineer

Large-Network Triage

Everyone reports different failures

Verify they are using the same map and route-network version first.

Destination missing

Check folder structure, sync state and whether the marker still exists after the map update.

Jobs queue at one trigger

Review approach geometry and unload-management behaviour; current AutoDrive can sequence vehicles approaching the same unload destination when configured.

Server behaves differently

Confirm the feature is supported on dedicated server and reproduce with a minimal route.

CP/AD transition fails

Test each system separately, then the handoff point.

Network feels slow or confusing

Remove redundant shortcuts, organise destinations and simplify regional routing before inventing more settings.

Proving Grounds Challenge

Network Engineer Licence Test

1. Split a large network into a documented regional structure.
2. Organise destinations into sensible folders.
3. Create a versioned backup before editing.
4. Export or manage the route through the Route Manager where your environment supports it.
5. Test one repeated pickup/delivery workflow.
6. Test one service action: parking, refuel or repair.
7. Prove one combine/unloader or AutoDrive-to-Courseplay workflow.
8. Run a multiplayer/server sanity check if that network will be shared.
9. Document what changed and what map version the network targets.