Bounded voice controls
Use supported start, status, recording marker, scene, and weather commands in the configured setup.
Record and review
Requires device setupAlaric Alexa Skill
Use supported voice commands with your configured game setup.
Alaric provides a hands-free route to selected table and recording controls. The control map helps the GM see which room and devices are connected, what is waiting, and what is actually recording.
What it helps you do
A recording control map
Follow camera, microphone, room, and mobile-device state without treating a waiting device as an active recording.
Keep the hardware local
Use configured recorder services to own the audio and video, with the browser providing controls and status.
Phone joins with context
Connect supported mobile recording roles through the session’s QR and ownership workflow.
Check the active mode
Use controls appropriate to the recorder mode and devices currently available at your table.
Getting ready
Open the Alexa Control Map and check the active operating mode before choosing commands. The project describes both native or remote recorder controls and a later mobile-import configuration. In mobile-import mode, older start and stop actions can return instructions for importing a completed phone recording instead of starting hardware.
Set camera, microphone, recording storage, capture software, and Scribe destination in the responsible native or local recorder setup. Alaric reads and controls that readiness rather than maintaining a competing set of hardware settings. Voice use additionally requires the configured Alexa skill, account, endpoint, and devices.
How to use Alaric Alexa Skill
Check the room and recorder sources
Use the Control Map’s camera checks, microphone information, and refreshed status. Inspect whether the required sources are ready and producing usable recording evidence. A reachable camera is not proof of video or embedded audio, and a visible microphone does not justify a fabricated battery measurement that its hardware cannot provide.
Select the session and organise phone joins
Check the scheduled game and roster where supported, then open Mobile Recorder in its own tab and use the shared QR workflow. Keep the Control Map available for monitoring. Distinguish waiting or enrolled player slots from sources that are actually recording, and inspect reported failures rather than treating every slot as present audio.
Start the supported recording path
In the configured remote recording mode, use the available start controls or supported voice intent and verify recorder status afterwards. Starting the suite and starting capture are separate results. A simulated development response is not hardware evidence. In mobile-import mode, follow the original phone-file import path and the available test or upload-log controls instead.
Mark important moments and use table commands
During play, request status or add a timestamped marker for a decision, NPC introduction, or important ruling. Use supported scene, map, weather, or season controls only where the connected Viewer implements them. If the room is noisy or a spoken action fails, use the ordinary browser, recorder, mouse, or keyboard controls.
Let clean stopping finish
For an active native recording, request a clean stop and follow the returned operation. It can pass through accepted, stopping cameras, finalising files, and complete or error states. A brief spoken acknowledgment means stopping began, not that all files are closed and verified. Keep the surrounding apps available until the recorder confirms a successful terminal result.
Check the archive and Scribe handoff
After finalisation, inspect the recording or import receipt and request the permitted Scribe delivery. Follow that handoff separately from capture. In the documented import configuration, Review upload logs helps distinguish phone-reported events, received parts, archive completion, and receipt publication. Check the actual operating mode rather than applying old instructions blindly.
Local handoff example: receiving the recording is followed by alignment review, transcription, and notes. Follow the individual stages after ending the session.
A game example
Mark a promise while keeping the game moving
For example, verify the configured room recording before play. When the party makes an agreement that will matter next week, add a supported marker and continue the scene. At the end, request clean stopping and check the operation until files are finalised. Hand the accepted recording to Scribe and use the marker to locate the agreement during review. If that setup is running in mobile-import mode, preserve and upload the completed phone original through its assigned session instead.
What you keep
Useful control feedback
Recorder, room-device, and supported mobile-slot state with the active mode and next action kept visible.
Tracked operations and markers
The supported command result, timestamped markers, and asynchronous stop status owned by the configured recorder.
A checked delivery path
Recording or import receipt information and a separately confirmed Scribe handoff for the intended session.
How it fits with the other apps
Mobile Recorder
Follow a joined phone and its recording or import status.
About this appAdventure Scribe Notes Keeper
Pass completed recordings into the notes workflow through the configured services.
About this appDQ GM Runtime
Use voice and recording controls alongside the live GM workspace.
About this appCommon questions
Is an Alexa device required to run the table?
The command layer also supports browser and established local controls. Voice is a convenience; ordinary mouse, keyboard, buttons, and recorder controls remain important. Opening the Control Map does not install or certify an Amazon Alexa skill.
Why did End session return while processing was still happening?
Stopping is asynchronous because long recordings need camera closure, metadata, hashing, and verification. Inspect the existing operation rather than repeatedly creating another stop. A failure should leave the relevant apps available for recovery, rather than shutting them down as if recording had completed.
Usage guide based on the 7 October 2026 project summary, reviewed 8 October 2026. Examples illustrate possible games. Some connected features require sign-in, GM permissions, or a configured local table.