FIELD JOURNAL / STANDALONE EDITION

Record routes on base AAEmu.

A small Windows tool for recording your normal walks through ArcheAge. You do not need to install PlayerBots.

AAEmu 1.2 · ArcheAge r208022 · same PC

Your everyday steps

  1. Connect. Log into the game. Open PlayerRouteRecorder.exe, enter your GM character's name and click Check connection.
  2. Name the walk. Enter From / to, such as Village gate → East bridge. The tool makes the walk name for you; you can enter your own if you prefer. Tick Take game photos while recording for Street View.
  3. Record. Click Start recording, return to the game and walk. Finish with Stop & export. Click Show export for the route ZIP or View photos to review your Street View.

First time? Complete the one-time setup below. Try a two-minute walk before a long trip.

Defaults: a route point every 2 seconds; an F9 photo every 5 seconds when photos are enabled. Ctrl+Alt+R pauses/resumes both. Road type, direction and frequency are in Route settings; photo options are in Photo settings.

First time: install the small server extension

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.

Use a local GM character with command access level 100. The recorder does not change permissions.

Already installed a standalone recorder extension? Use Check connection; if it works, skip installation. If you later run Game from a different output folder, install the extension there too.

First time: check game screenshots
  1. In the game, press F9 once. Confirm a new picture appears in Documents\ArcheAge\ScreenShots. This is the default listed in ArcheAge's official 2014 screenshot instructions; your client's binding may differ.
  2. If your key or folder is different, set it in Photo settings. The usual key and Documents folder are filled in already.
  3. On Record a route, tick Take game photos while recording. A single open ArcheAge window is selected automatically. If you have several, choose yours in Photo settings.

Start recording and keep the game in front. The recorder presses your screenshot key and collects each new completed picture. Original screenshots stay in the game folder. Switching away or pausing skips photos.

At a landmark, stand still, turn the camera and press/release Ctrl+Alt+P for an extra view. These are separate photos, not a stitched 360 panorama. Position is approximate: it is sampled when the screenshot is requested.

No new photos? Check the key and folder manually. Photo source → Visible window capture is an alternative for windowed/borderless play. Detailed photo guide and limits.

What to send back

Click Show export. Send the route ZIP and, if you took photos, the separate -street-view.zip, plus their .sha256 files. Everything is under Documents\ArcheAge Routes\exports by default. Review pictures for names/chat before sharing.

To browse the photos, extract the entire Street View ZIP and open index.html. It works offline.

Useful optional settings and notes

Route settings keeps road type, direction, sample frequency, duration, notes and save folder. A walk defaults to from-to; record the reverse separately before calling a road bidirectional.

At a bridge, gate or obstacle, enter a short note beside Bridge, gate, snag and click Mark location. A failed note stays in the field.

Photo settings controls frequency (5 seconds), image width (1600 pixels) and storage limit (512 MB). Keep space for originals, collected copies and exports. The photo guide explains the limits.

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

Connection or setup trouble

Wrong folder: select the built AAEmu.Game.exe. Its folder must contain AAEmu.Game.dll, dependency/runtime files and Scripts/Commands/GetPosition.cs. The installer checks the layout, not the exact binary revision; use AAEmu 1.2 r208022.

Different recorder already installed: keep it intact. Ask the server owner to compare versions. Do not add a second copy of the same command under another name.

No sample: verify the Game server was restarted after installation and your GM character is online. In game, /playerrouteposition sample should return PLAYER_ROUTE_SAMPLE_V1. Unknown command means the extension was not loaded; insufficient privileges means the character needs the server's existing GM access.

Cannot connect: 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.

No window: launch from the extracted folder, not the ZIP. Startup errors show a message; diagnostic logs are under %LOCALAPPDATA%\ArcheAge Route Recorder\logs.

No export: walk farther and watch the sample count. Stationary-only or interrupted recordings may have no traversable segment. Raw files remain under working-recordings; the bottom log explains what happened.

What this version changes

The standalone extension adds only Scripts/Commands/PlayerRoutePositionCommand.cs to your chosen Game folder. It reads the invoking character's server position. It does not edit the client, change permissions, add bots, apply host patches, configure a database, or control the server.

Validated host source: AAEmu/AAEmu 62e3eb1d87da01194802ac886cd500134facad28. Other revisions need their own compatibility check. Existing route formats are retained for PlayerBots research tools; the moduleVersion metadata field identifies this recorder-only package, not a detected server mod. Put the actual server build in your field notes.

The recorder uploads nothing automatically. Review free-text notes and separate screenshots before sharing. Record transport and swimming separately, and never use teleports or injected quest credit as evidence of a working route.