Your route starts here.

Before you start

A working AAEmu setup comes first.

You need a working local AAEmu Game server and an online GM character with command access level 100. The full PlayerBots mod is not required. AAEmu 1.2 r208022 is the tested baseline. Other revisions, including r208088, are experimental and can be tried when Check connection returns a valid position. If problems persist, use a matching r208022 server/client setup.

The download includes the recorder, its small server extension and this guide. It does not include AAEmu, game files or a database.

One-time setup

Connect the recorder to your server.

1. Extract the entire ZIP

   Right-click the downloaded ZIP → Extract All. Keep all its files together in a normal folder, such as Documents. Open PlayerRouteRecorder.exe from that folder.

2. Choose your Game server

   Close the Game server using its normal graceful shutdown. In the recorder, open Server setup → Choose Game EXE… and select the AAEmu.Game.exe you normally run.

   AAEmu.Game.exe is the server. AAEmu.Launcher.exe opens the game client. If you built AAEmu yourself, look under AAEmu.Game\bin\Debug\net10.0\ or Release\net10.0\; some builds also have an x64 folder. Select the actual output you use to start Game.

3. Install the extension, then start Game

   Click Install extension. It adds one position-reading script to Scripts\Commands. Start Game normally again, then log into your GM character. AAEmu loads the extension during startup; an already built server needs no rebuild or database migration.

Everyday use

Connect. Name the walk. Record.

1. Check connection

   Log into the game, open the recorder, enter your exact GM character name and your Client build (for example ArcheAge 1.2 r208088), then click Check connection. The build is your declaration, not an automatic detection.

2. Enter From / to

   Use landmarks, for example Village gate → East bridge. The walk name fills itself in. Enable Take game photos while recording if you want photos too.

3. Start recording and walk

   Return to the game and travel normally. Finish with Stop & export, then click Show export. Try a two-minute walk before a long trip.

Route settings keeps road type, direction and frequency. The default is one point every 2 seconds. Press Ctrl + Alt + R to pause or resume. Keep separate routes for walking, swimming and transport; only mark a road bidirectional after checking both directions.

Mark what you find

A useful note in one click.

While recording, scroll below the note field to 4. Quick mark options. Click Quest, Fork, Merchant or Mail to save that label at your current location.

To make your own button, enter a word or short phrase in New button and click Add quick mark, or press Enter. Use the small x beside a button to remove it. You can keep 24 labels of up to 40 characters each; your choices survive closing the tool and extracting a newer version.

Quick marks preserve any longer note you are typing in section 3. Marking is disabled while paused. If the connection fails, the recorder tells you to retry; it does not save a made-up location.

Explore a town

Connect streets at named junctions.

1. Choose City / area network

   Enter the area name in Area name. From / to is unnecessary. Start recording.

2. Mark each junction

   In City junctions, name the place and click Mark junction. Walk to the next place and mark it too.

3. Return and explore another branch

   At the same junction, choose its existing name and mark it again. Use a different name for a different floor. The tool joins explicit matching junctions within 1.5 metres horizontally and 0.75 metres vertically; it never guesses connections from map crossings.

4. Stop & export

   The ZIP includes route.json, network.json and navigation-prior files for the extractor. Loops stay intact. Only walked directions become edges. Pause before any unrecorded move.

Example: Gate → Market → Merchant → Market → Mail → Market → Gate. Keep Quest, Merchant, Mail and obstacle notes in Quick marks. See the network data guide for fieldwork and export details. These exports are collection evidence; they do not install themselves into bots.

Optional photos

Collect a view along the route.

Tick Take game photos while recording. Photos use their own interval, every 5 seconds by default. A single open ArcheAge window is selected automatically; choose your window in Photo settings if several are open.

Keep the game in front while recording; switching away or pausing skips photos. At a landmark, stand still, turn the camera and press Ctrl + Alt + P for an extra view. These are separate photos along your walk, not a stitched 360° panorama. Photo positions are approximate.

Use View photos to review the result. Photo settings also controls image width and storage limits. Keep space for screenshots, collected copies and exports.

Contribute on your own time

Make the next route easier to follow.

Short town exits, forks, bridges and road connections are good first trips. Mark quest interactions, merchants, mailboxes, obstacles and places where a crossing fails. Include the zone, nearby landmarks and what you observed. Failed attempts and normal detours are useful too.

Click Show export. Keep the route ZIP and, if you took photos, the separate -street-view.zip, along with their .sha256 files. Exports go to Documents\ArcheAge Routes\exports by default. To browse photos offline, extract the entire Street View ZIP and open its index.html.

Review pictures and notes for names, chat or anything private before sharing. Contact Over1ander in the AAEmu Discord to arrange sending your recordings. The recorder does not upload automatically, and this website does not accept direct uploads.

If something gets stuck

A few quick checks.