Pixel Rewind — Legacy Server Admin

Tables

A table is a matched group of players. It fills first — every seat has to be taken before the battle setup goes out — and then plays. The server relays the match but does not simulate it, so the turn and phase below are the last stamp seen on the players' own traffic.

No tables.

Tic-tac-toe

The FOSS tic-tac-toe is played on the same accounts as everything else, and the server referees it. Games live in memory only: a restart empties this page, and a deploy waits for the open games to finish.

Games in progress

No games.

Waiting for an opponent

Nobody.

Recent games

None since the server started.

Gameplay rules

The whole rule set travels to every client in the battle-setup record at the start of a match, and the client clears its own copy before reading it — so what is published here is what every player plays by. Changes apply to matches that start after you publish; a table already playing keeps the record it was given.

Default rules are what every map plays by. A rule set gives some maps their own changes on top of them — a map of bombs only, say. One publish covers the default rules and every rule set.

Export Import…

Loading…

Not editable here

Two kinds. Settings the game ignores: the rule set has them and the record carries them, but the 2008 game never reads them during a match, so changing them would do nothing — each is listed with how that was established. And what would change the record's length, which the client reads by position and does not check: block shapes and a mask's size. Masks are editable above at their shipped size, and hero, monster and princess stats are fixed-size words; each publish is checked by building the record for every map and player count. Which power a hero has is a fixed-size word too, but swapping powers between heroes has never been tried, so it is not offered. Edit the server's gamedata/rules.json and restart to change any of these.

Loading…

Matchmaking

How searching players are grouped into a table. Applies to the queue straight away; nobody already matched moves.

Sessions & timing

How long the server holds a callback poll open, how long a silent client is kept, and the heartbeat it advertises. The client's own retry budget is 40 seconds, which is why the poll hold is capped below that.

Match

The board every new match is fought on — one of the game's own or one drawn on the tab. It must have a board for every player count the queue can start.

Players

What players can change about themselves from the app's settings.

Logging

What the server writes to its console and to the Log tab. The same two switches are on the Log tab, where they take effect immediately.

Item rulesets

Every set of item rules a match can be played by, each under its own name. Every match records the ruleset it was played by — legacy when it had none, the game's own items — so its statistics can be read against it. A saved ruleset never changes: there is no editing one, here or in the database. To try other rules, save them as a new ruleset under a new name (New from this starts from one below). Item rules and Rooms below only choose among these. How to write one, and every shipped one explained: rg/native-port/docs/ITEM_RULES_AUTHORING.md.

Loading…

New ruleset

Name 1 to 40 plain letters, digits, spaces or punctuation. A name already used cannot be used again.

Description

Rules (JSON)

Item rules

Which saved ruleset (above) drops the items in matches on the native port, decided on every player's game. It is put to a table's players before its match starts and only goes in force when every one of their games says it can run it; otherwise that match plays as the original game did, and is filed as legacy. Nothing about items crosses the network during play. Shadow rulesets decide and report without changing anything — run one that way first and check the live board says the games agree. Applies to matches that start after you save.

Item rules

off

Quick Match

on

Offer item rules to Quick Match tables (ranked and unranked).

Rooms

on

Offer item rules to rooms: Classic ones, and Custom ones that chose no item preset (see Rooms below).

Ruleset

For every table the switches offer item rules to, except where a number of players or a map has its own below. Legacy: none here, so only those below have rules.

Rulesets by number of players A match plays by the ruleset of its number of players (people and bots together) instead of the one above — legacy to play matches of that size with the game's own items. A map's own ruleset below still comes first, and a Custom room's item preset before that.

Rulesets of single maps A map with its own ruleset plays by that one instead of any above, whatever the number of players — legacy to play that map with the game's own items. Maps without one use the ones above. The switches above still apply.

Rooms

What a Custom room offers its creator in the app (Arena → Rooms → Anonymous Room → Custom): the maps, and the item presets. Each is a toggle that cycles through the ones ticked here, in this order; the first is what the menu starts on. The room's choice decides its match: the map is played as chosen, and the preset replaces the item rules above for that match, whatever their switches say. Apps read the lists when they log in, so a change reaches a player at their next login.

Random

on

Offer "Random" first: a draw from the ticked maps at each match.

Maps

Beside each map, tick the modes whose rooms offer it: Classic, Deathmatch, Princess Rush. The Map toggle shows a room only the maps that fit its mode (Random draws from those too). A map that cannot start a room's match (a deathmatch board in a Classic or Princess Rush room, no board for that many players) still gives way to fortress. Princess Rush puts the neutral princess where the map editor drew her, or else on the free cell nearest the middle.

Item presets Untick to keep a preset without offering it. Each plays by a saved ruleset (Item rulesets above); legacy is the game's own items. A name is at most 12 plain letters, digits and punctuation: the game's fonts draw it, and the menu shows "Items: " before it, which on a phone held upright leaves room for about that many.

Chat phrases

What players can say in a match: they pick one of these instead of typing, and everyone reads it in their own language. The emote is the face the speaking hero says it with: happy, neutral or angry. A message that is not one of these keys is dropped by the server. The app gets the list at each login, so a change reaches a player at their next login; a phrase taken out stops being passed on at once. English is required; an empty box falls back to the English text.

Loading…

Online rules

What every player of the app accepts once before playing online, as both app stores expect wherever players meet. The app asks for them before each login, in the player's language, and goes online only once they are accepted; the account keeps which revision it accepted and when (Players tab). Plain text: lines, with a blank line between paragraphs. English is required; an empty box falls back to the English text. Fixing a typo keeps the revision; tick "ask again" for a change players must see, and every player is shown the rules again at their next login. Turned off, nobody is asked.

Loading…

Ask every player to accept them again

Name filter

Names players may not pick: checked when a player changes its own name in the app, and when a new account first logs in. A refused change is answered "name taken"; a new app whose random guest name is refused is registered as "Player" and five digits instead. Names players already have are not touched, and your renames are not checked. One entry per line, a-z and 0-9: a plain entry refuses any name containing it; one starting with = only a name that is that word or has it as a part (split at _, digits and capitals). Exceptions are taken out of a name before the plain entries are looked for (peacock, badminton).

Offensive

Reserved (impersonation)

Exceptions

Board art

What this panel's boards are drawn with: the map editor, the live board, the item drops and the match timeline. The server ships none of the game's art, so they use the panel's own sprites until you import your copy of the N-Gage game here, either the .n-gage download (Nokia's package or the cracked one) or its Game installer (.sis). Then every hero, monster, item, castle, block and floor is drawn as in the game, in each player's colours. The package itself is not kept: only the pictures taken from it are, on the server, and only signed-in admins are shown them. The switch goes back to the panel's own sprites without losing the import, for every admin; removing the import deletes the pictures.

Loading…

Import N-Gage package…

Maps

Draw the board a match is fought on. The server sends the board to every player in the battle setup, so a new map needs nothing installed on the players' side. A map has one board per player count — 2, 3 or 4 — because that is how the game's own quick-match maps work: a full table of three is seated on the 3-player board. Only what an online match actually builds can be drawn here: the board size, one 2x2 castle and one hero start per player, where each princess starts (in her castle, on the board, or not at all), monsters each player starts with, each player's starting territory and the scenery. A board can also be a deathmatch: no castles, so a hero that dies is out and the last one standing wins, as in the campaign's Deathmatch mission.

Pick a map to open it. The built-in maps open read-only — duplicate one to start from its layout.

Matches

Every match this server has formed since it started, newest first. Kept in memory only, so a restart empties it. Click a match for its players, how each one left, and its log.

Loading…

All recorded matches

Every player's matches from the database, so they outlive a restart. Click one for its result, timeline and drops.

Loading…

Server log

Logging Verbose

Follow Download

Loading…

Players

Everyone who has logged in, and what they have done online. A player is its id — the first name its game logged in under, which never changes and is what every match is filed under — and a name, which is what the game shows and which you can change here. A renamed player's game is told the new name the next time it connects, and switches to it before the game shows one; until then it plays under the old name. Players can also change their own name in the app's settings, from the device the account was made on: its device key, a secret the app keeps with its saved data. Forget devices lets the next device that connects take the account over, for a player who lost theirs. Only Ranked counts: matches in Quick Match (unranked) and in rooms are saved but do not add to the record, the fame or the ladder. The record is what the game's own Rankings and Battle Stats screens are answered with, and it is filled from the standings the clients report when a match finishes — the 2008 client has no request for that, so only native-port sends one. A rank needs 6 finished matches, which is the threshold the game itself enforces.

Leavers lose fame

off

On: a player who quits or drops out mid-match loses fame as the game placed them (knocked out on the spot), as the original did. Off: that match is not rated for them, and the others are rated against each other as if they had not been there - kinder to bad connections, the loudest complaint about the 2008 ladder, but a player about to lose can quit to avoid it. A surrender always counts. Changing it re-rates every stored match.

Tick two or more players to merge them into one.

No players yet.

Match statistics

Match totals include every started match. Wins and rescues by seat and hero use reported results; event details cover only matches whose decoded rows are still kept (0 now). Older timelines still open from their stored recordings.

From To Players Ranked Mode Item rules Player

No event logs yet.

Chat phrase usage

Accepted player messages counted once per send, using the match and player filters above. Dates refer to the match start date (UTC). Counts survive phrase edits, removal and resetting the list; changing a key starts a new counter. Admin messages and refused messages are excluded.

Order

Loading…

Admin users

Everyone who can sign in here can manage these accounts. Renaming a user, disabling them or setting their password signs them out at once, and a password you set is theirs only until they choose their own. Nobody can disable or delete their own account, and the last enabled user cannot be removed.

Loading…

Add a user

Your account

Changing your password signs out every other session of yours. Five wrong passwords in a row lock a sign-in for fifteen minutes.

Revision history

Every published rule revision, newest first, with its rule sets. Kept in the settings database, so it survives a restart. Rolling back publishes a new revision with that revision's values and rule sets.

No revisions yet.

Admin log

Every change made in this panel, newest first: who made it, when, and what it changed. Kept in the settings database, so it survives a restart. Failed sign-ins are kept too, the newest 1,000 of them.

Loading…