Record roads or connected city paths, save landmark notes and add your own quick marks. Works with a local AAEmu 1.2 server; the full PlayerBots mod is not required.
The simple guide is included in the ZIP. New releases appear here; there is no automatic update checker.
Before you start
A working AAEmu setup comes first.
Start with AAEmu 1.2 and an ArcheAge r208022 client, running on the same Windows PC as the recorder. Use an online GM character with command access level 100. The full PlayerBots mod is not required.
The download includes the recorder, its small server extension and an offline setup guide. It does not include AAEmu, game files or a database.
Other compatible revisions can be tried with an experimental warning. Enter your actual Client build in the connection section; the recorder saves that declaration with your data. A successful connection checks that positions can be read, not that every feature on that build is supported. If problems persist, use the matching r208022 setup. Live r208088 compatibility remains unverified.
Which AAEmu revision was checked?
The recorder bridge was validated against AAEmu source 62e3eb1 for 1.2 r208022. Other revisions are experimental. The installer checks the server folder layout; it does not detect or certify the server or client revision.
One-time setup
Connect the recorder to your server.
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.
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.
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.
Already used the standalone recorder?
Extract the new download and click Check connection. If it works, you are ready. Reinstall the extension only if it is missing or you now run Game from a different output folder. Your quick mark buttons stay saved on this Windows account.
Everyday use
Connect. Name the walk. Record.
Check connection
Log into the game, open the recorder, enter your exact GM character name and click Check connection. Enter your Client build in the same section so the export identifies your data correctly.
Choose a road or city survey
For Landmark-to-landmark route, enter From / to landmarks, such as Village gate → East bridge. For City / area network, enter the area name and use the junction steps below.
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.
Connected paths
Map a city one junction at a time.
Choose City / area network
Enter an Area name, then start recording.
Name the junctions you visit
At a gate, fork or other connection, use City junctions → Mark junction. When you return to the same spot, choose its existing name. Use different names for separate floors or nearby doorways.
Walk each branch, then export
Try Gate → Market → Merchant → Market → Mail → Market → Gate. Mark each place on arrival. Walk a connection in both directions if both are usable; the tool only records the directions you walked.
Pause before teleporting or skipping a section. Pauses, disconnects and large jumps separate paths. Crossings do not become connected junctions just because they are close together. Named junctions belong to one survey; keep separate survey ZIPs for review.
City exports include the usual route.json, a network.json and files for the navigation extractor. These are observations for review, not a ready-to-install bot navigation map.
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.
Contribute on your own time
Make the next route easier to follow.
Short town exits, forks, bridges and road connections are good first trips. City surveys are especially useful for doors, stairs between floors, blocked approaches, normal detours and one-way drops. 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 its .sha256 file. Exports go to Documents\ArcheAge Routes\exports by default.
Review your notes for names 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.
I cannot find AAEmu.Game.exe
It belongs to the built AAEmu server, not the client launcher. If you only have AAEmu.Launcher.exe, follow the AAEmu setup wiki or ask the AAEmu community for help setting up a compatible 1.2 server. The recorder requires that local server to read positions.
Check connection fails or no sample appears
Confirm Game restarted after installation and the named GM character is online. In game, /playerrouteposition sample should return PLAYER_ROUTE_SAMPLE_V1. Unknown command means the extension did not load; insufficient privileges means the character lacks the required command access.
Read the specific error beside your character name and in the bottom log. Check the Local API address under Server setup against your Game server configuration. The usual address is http://127.0.0.1:1280.
The Game server’s active Config.json should have WebApiNetwork host 127.0.0.1 and port 1280. Keep this administrator API on loopback. The installer does not edit settings; restart Game normally after a configuration change.
The installer reports a conflicting extension
Keep the existing file intact and ask the server owner to compare versions. Do not install a second copy of the same command under a different name. A matching standalone copy is reused automatically.
The recorder will not open, or the route will not export
Run the EXE from the fully extracted folder. Startup diagnostics are under %LOCALAPPDATA%\ArcheAge Route Recorder\logs. For an empty export, walk farther and check the sample count and bottom log. Stationary-only recordings may have no traversable segment; raw files remain under working-recordings.
Changelog & history
Updates live here.
Route recording highlights and previous downloads. Bookmark this page for newer versions. To update, extract a new version into its own folder and open its EXE. A working position extension needs no reinstall for 1.6.0.
1.6.0 · Latest
City / area network mode adds named junctions, branching paths and closed loops. Each connection records the direction you actually walked.
Connection checks show useful character, permission, API and extension-load errors.
Declare your client build and try other compatible AAEmu revisions with an experimental warning. r208022 remains the tested baseline; live r208088 compatibility is unverified.
Exports keep the existing route format and add city network data plus navigation-extractor inputs. Pauses, disconnects and large jumps separate walked sections.
The setup guide covers road and city surveys. A working position extension does not need reinstalling for this update.
Refreshed the included installation guide with the website’s gold and charcoal design, clear first-time and everyday steps, and official AAEmu setup links.
Recorder and server extension behavior is unchanged from 1.5.0.
Added a website download page and manual version history. No automatic update checker.