Mobile

The same client, in your pocket

The phone app runs the same scripting engine as the desktop client, so your aliases, triggers and maps behave the same in both places. Set yourself up once on the desktop, scan a QR code, and the whole lot is on your phone.

Shared engine

One setup, two screens

Transfer

Sent across by QR code

Open Send to phone on the desktop and scan the code. Your characters, aliases, triggers, variables, macros and maps go over your own Wi-Fi, encrypted, straight from the one device to the other.

Parity

The same scripts run

Both clients share one engine, so a trigger written on the desktop fires the same way on the phone. Fix something in one place and the fix belongs to both.

Built for thumbs

A keypad, not a keyboard

A direction pad and macro buttons sit under the text, so ordinary movement and your common commands never need the on-screen keyboard at all.

Mapping

Three ways to keep the map on screen

A phone has no room for a docked map panel next to everything else, so the map has three modes. Switch between them as you play: one for reading the map, one for glancing at it, and one for when you want the text and the map in the same space.

The phone app with the map filling the top half of the screen and game text below it. — **Split** The map takes the top of the screen and the game text sits below, with a handle between them so you can drag the split to whatever suits. Best when you are exploring somewhere new and reading the map properly.

The map as a small floating panel over the game text, with a direction keypad below. — **Floating** The map hovers over the text as a small panel you can move out of the way. You keep a full screen of game text and still see where you are at a glance.

The map drawn faintly behind the game text, filling the whole screen. — **Behind the text** The map is drawn faintly across the whole screen with the text on top. Nothing is covered and nothing is shrunk, and your position still moves as you walk.

In action

Walking the map

Ten seconds of ordinary play. Each move is a tap on the direction pad, the room text arrives, and the mapper works out where you are and moves the marker without being told.

This is the same mapper as the desktop client, reading the same map file. A map you built or imported on the desktop arrives on the phone already drawn, already linked up, and already knowing your speedwalks.

Your setup, intact

Everything copies across

Nothing is trimmed down for the small screen. A full setup, classes and all, arrives whole and stays editable on the phone.

The settings editor on the phone, listing over a thousand items grouped into classes with on and off toggles. — **The settings editor** The same tree as the desktop, with search, filters by type, and your classes as folders you can switch on and off. The setup in this shot carries well over a thousand items, imported from zMUD and sent across by QR code. Tap anything to edit it on the spot.

Two floating command buttons labelled heal and swing sitting over the game text, above a keypad of named macros. — **Buttons where you want them** Macros become real buttons: name them, colour them, and drag them anywhere on the screen. The keypad at the bottom holds the ones you always want in the same place, and the floating pair sit wherever your thumb already is.

Getting it

Closed beta

The mobile app is still in closed beta, but let us know if you wish to join: email support [at] akamud [dot] com, or ask in the AKAMud channel on the Akanbar Discord.