Record routes on base AAEmu.

1. Set up once

You need a working AAEmu 1.2 Game/Login server and matching client on this PC. This ZIP supplies the recorder and one position-reading script. It does not supply the emulator, game files or databases.

1. Extract this entire ZIP to a normal folder such as Documents. Keep the files together.
2. Close the Game server normally. Use its usual graceful shutdown command. The installer will not stop it.
3. Open PlayerRouteRecorder.exe and select the Server setup tab.
4. Click Choose Game EXE... and select the AAEmu.Game.exe you normally run. If you build from source, it is usually under AAEmu.Game\bin\Debug\net10.0 or Release\net10.0. Choose the built server program. AAEmu.Launcher.exe opens the game client and is different; some builds add x64 between bin and Debug/Release.
5. Click Install extension. It copies one file into Scripts\Commands. A matching existing copy is reused; conflicting files are preserved.
6. Start Game normally again. AAEmu compiles the extension during startup. No server rebuild, PlayerBots patch or database migration is needed.

If you later run Game from a different output folder, install the extension there too. Rebuilds/publishing tools may omit this separately installed script; verify it remains in the folder you actually run.

2. Record a short walk

1. Log in with your local GM character. Stock AAEmu requires command access level 100; the recorder does not change permissions.
2. Open Record a route, enter that character's exact name and click Check connection.
3. Enter a Path name and From / to landmarks. For example: “Haranya — village gate to east bridge”.
4. In Settings, choose the road type and direction. Sample seconds controls frequency (default 2). A single walk defaults to from-to; record the reverse separately before calling it bidirectional.
5. Click Start recording and walk normally. Ctrl+Alt+R pauses/resumes from the game. Try two minutes first.
6. At a bridge, gate, obstacle or useful interaction point, type a short note beside Bridge, gate, snag and click Mark location. It samples your current position; a failed note stays in the field.
7. Click Stop & export, then Show export. Share the ZIP and its matching .sha256 file with the project owner.

Frequency, road type, direction, auto-stop, session notes and output folder remain available in Settings. Default output is Documents\ArcheAge Routes.

3. Add Street View photos (optional)

1. Enter the game in windowed or borderless mode. In the recorder, open Photos and enable Take game photos while recording.
2. Click Refresh game windows and select the ArcheAge client window. Set Photo seconds (default 5); this is separate from position frequency.
3. Start recording and switch back to the game. Only the selected visible game area is captured. Switching away skips photos; pausing recording pauses photos too.
4. At a landmark, stop walking, turn the camera yourself, and press Ctrl+Alt+P for extra views. Camera direction is not measured, so these remain separate photos rather than a stitched 360 panorama.
5. Click Stop & export, then View photos. Step along the images or click the trace to jump to a location. Review photos before sharing the separate -street-view.zip. Names, chat and overlays can be visible.

Recipients extract that entire ZIP and open index.html. The viewer works offline. Default photos are JPEG, up to 1600 pixels wide, capped at 512 MB per session. Keep extra space for the exported folder and ZIP. Photo guide, capture limits and 360 feasibility.

Good first assignments

Walk short Haranya town exits, road connections and bridges. Keep each trip separate. Record failed crossings and ordinary detours, not just successful routes. Terrain and interaction evidence is more useful than manually copying item or skill tables.

Fieldwork assignments · Fill-in notes