Players
Players lists everyone who signed in to the environment chosen in the header, newest first. Each environment has its own players. Search by a player id or a device id, whole, or by the start of a nickname.
The card
Section titled “The card”The header of a player’s card shows its profile (nickname, avatar, language, region, when it was created and last seen), the devices it signs in with, its balance in every currency with Adjust, its timers that wait and those whose handler failed, and its last failed call, which opens the Timeline with only the failures. Three tabs follow.
Overview
Section titled “Overview”A card per module the player has, in the terms of the module: the items of the inventory, the offers it bought with the limit used and the stock left, each quest with its status and a progress bar per objective. A module puts its own view here (see Dashboard pages), with its actions: an action of a row, such as Take on an item or Reset on a quest, fills its arguments from the row and asks for the rest; an action of the module, such as Grant, sits at the top of its card. After an action the card reads the data again. A module without a view shows its data as it keeps it, under “This module has no player view; showing its data”.
Timeline
Section titled “Timeline”Everything that happened to the player, newest first and by day: every call that changed something (its own calls from the game, the calls and the actions of your game server, its timers and events, and the actions of operators), and between them the calls that failed and changed nothing, marked “failed · changed nothing” with their error code and the lines the module logged. Filter by module, or show Only failures.
Each change says who (the client, the game server, a timer, an event, or the operator by name), what (the module and function, with its arguments) and what it changed in the terms of the module: balances with their amounts, items, fields, records, scores of a board, events sent, timers scheduled or cancelled. Open it for the release it ran with and every change in full.
This is how support answers “I bought the pack and got nothing”: the entry of the purchase shows the gems paid and every item granted, or a failed purchase that changed nothing, with why.
Failed calls cover the last 10 000 calls of the environment; the history of changes is kept whole.
Raw data for debugging: every field, record and timer each module keeps for the player, as the module declared them, a module per card.
Actions
Section titled “Actions”Each action is an entry of the Timeline with who took it: the operator, or your game server.
| Action | What it does |
|---|---|
| Adjust a balance | Credits or debits a currency, with a reason. A debit below zero is refused. |
| An action of a module | Calls a function of the module for this player, such as Grant in Inventory or Take on an item, with a form of the arguments the row does not give. Functions marked server included. |
| Ban | For a time or forever, with a reason. The game client is refused at sign-in and on every call; the game server, timers and events keep working. |
| Lift the ban | |
| Edit the profile | Renames the player or changes its avatar. A sign-in sets them only while they are empty, so a rename stays. |
| Unlink an account | The next sign-in of that device starts a new player. The last account stays. |
| Delete | Every call for the player is refused and its timers and events wait. Everything it has is erased in 7 days; until then Restore takes it back. |
Your game server takes the profile and ban actions itself through the server SDK.
Reading is open to every role, the views of the modules included. The owner and support take actions and call mutations; an editor calls queries only.