Blog ·
Dakar Desert Rally Roadbook Editor: Build a First Route
By Dakar Rally Game editorial team. Sources and practical guidance; no hands-on benchmark claims.
Begin with a small route you can understand
The easiest first roadbook is a short route with a clear start, a small number of decisions and an obvious finish. Resist the temptation to build a huge expedition immediately. If a long route fails validation or feels confusing to drive, finding the cause is much harder than fixing a short learning exercise.
Saber's editor instructions describe opening Roadbook Editor, choosing Create Roadbook, selecting an area and a game mode, then placing the route. Use those documented controls as your starting point. The design suggestions below are an original practice method for making that first route readable.
Plan three recognizable moments
Choose a starting area where the vehicle can settle before the first decision. Then create one change of direction using a recognizable terrain feature. Finish somewhere distinct enough that you can tell whether the route arrived as intended. You are testing the editor's workflow and your route logic before testing endurance.
Think from the driver's viewpoint. A turn that looks obvious from an elevated editor camera may be difficult to distinguish from two neighboring tracks at ground level. Drive toward the decision before adding more distance. If the player needs to slow down to understand it, give them room to do so rather than placing the decision immediately after a blind crest.
Test the route before decorating it
The official workflow provides Test Drive and a warning panel. Use them during construction, not just at the end. After changing a decision point, test that segment again. Keep a brief note of the reason for each edit: a misleading landmark, an awkward approach or a finish that is hard to recognize.
Separate technical validity from a good driving experience. A route can be understandable to its creator because the creator remembers every placement. During a fresh run, avoid relying on that memory: read what is displayed and follow what the terrain actually communicates. If possible, take a break before the next test so the instructions must do more of the work.
Validate and save a clear version
Saber says to place the start and finish, resolve warnings, run Validate Path and complete AI validation before saving the roadbook. Give the saved version a descriptive name rather than a label such as “test final 7.” A name that identifies the terrain and approximate scope makes later comparisons easier.
For the next version, add only one extra challenge: another junction, a more technical approach or a longer linking section. Preserve the short version as a reference. See our missed-waypoint checklist for diagnosing confusing decisions and the Dakar Desert Rally hub for related guides. A route that communicates well is a better first achievement than a route that is merely long.