- Jam-A-Gram privacy: the inbox's options were taken the wrong way round
- report window: no instruction text over the reason
- the museum's theatre and other unnamed rooms get names; every shop a title
- "How did you hear?" is never offered (its window soft locked the game)
- video spots with nothing to play open a "Your Video" box on the game page;
the trade list's help plays a video; the theatre's box no longer vanishes
- emotes, actions and phrases are limited per player, as typed chat is
- phrases from the menus come in the sender's chat bubble style
- settings: WASD, blocked players and custom items as two-sided switches,
graphics at their best by default, a switch for bubble animations, and
Manage Account beside two-step sign-in opens the account page
- pressing a @mention in a bubble no longer walks the player there
colours from a dump of a beta-era inventory, added after each item's own
so the colours already given keep their place: Rare Eyeball Hat, Creature
Mask, Tiara (two), Arctic Hood, Elf Helmet, Furry Hat and Turquoise Ring.
the shop shows a list's first 8, so these are had from the item givers.
/account/items, linked from the account page and using its sign-in, gives
items to the account signed in:
- clothing: the item's own colours, or four colours of your own as a
picker, #RRGGBB, or AJ's numbers (palette places, or the whole item's
colour id signed or unsigned), converted as you type; hex colours not in
the palette become an exact custom colour
- den items: the variants their art has (lib/den-variants.json, made by
tools/den-variants.sh) and a whole-item tint with a strength, kept in the
item's version above the variant and drawn by DenItemHelper (build 83)
- a preview of each: clothing icons coloured on the page as the game
colours them, den items played by Ruffle in a sandboxed frame through
public/item-preview.swf (tools/preview-host)
a give with a custom colour id that does not exist is refused.
"Sign in with the Burrow client" on the account page's sign-in screen
opens burrow://account?n=<nonce>; the browser asks whether to open
Burrow. The client asks for a ticket with its login token
(POST /account/api/client-ticket) and opens /account/client?ticket= in
the browser, which signs in there. A ticket lasts 2 minutes, is good
once, and signs in only the browser holding the nonce's cookie, so a
burrow:// link from elsewhere signs nobody in and a ticket sent to
someone else opens nothing. The tab that started it follows by itself;
once it has worked in a browser, the page asks for Burrow by itself.
A computer is taken for a banned one, and an account for an alt, only
when they share at least 3 hardware IDs (system, board, disk, the
client's own); one or two in common was too often someone else's.
Network card addresses still do not count. A hardware ban is refused
for an account with fewer than 3 IDs known, as it could match nobody.
MAC-only ("weak") alts no longer exist, so the flag is gone from the
panels.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Since 3423df1 the server followed an animal switch ("as") with that
animal's "ad" and full "il". The client swaps animals partway through the
transform animation: at "hideAvatar" it copies the in-world avatar into the
switcher slot being left, then loads the new animal onto the in-world one.
The extra "ad" arrived before that frame, had no request waiting for it, and
so was applied to the in-world avatar, and the "il" then matched it too. The
slot got a copy of the new animal, the old one was gone from the switcher,
and the other slots drew blank until the next login.
This reverts 3423df1. A newly bought animal's editor not opening until the
next login comes back with it and needs a fix that goes through the
client's own "ad" request.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
publishStatus gave the card players: 0 and rooms: 0, so the public card
always said "0 online • 0 rooms". It now counts world.players() and their
rooms, as /burrow status does.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A recovery link (7dee290) removed 2FA on the email alone, and a password
reset is email alone too, so a player's mailbox was their account, 2FA or
not. For staff, 2FA removed and turned on again with another app made
whoever had the mailbox active staff.
- a 2FA reset by email also takes the account's current password, and is
refused for 7 days after a password reset by email
(emailPasswordResetAt), so the two cannot be chained.
- never for an account with a staff role: they ask the admin, whose
temporary password can turn 2FA off.
- at most three recovery emails an hour for one account, from any address.
The address is still never confirmed, nor shown or changed on the
account page.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Since 7dee290 a Discord account linked to a staff member opened the
moderator panel for 12 hours on Discord's word alone, with no password and
no 2FA code, though the normal sign-in asks for both every time; and since
b11ae1d the bot took /moderate and /burrow commands from that Discord
account alone. The link outlives a new password and "sign out
everywhere", so a taken-over Discord account was enough to act as the
staff member. The admin dashboard's Discord sign-in (adminDashboardAccess)
skipped its password the same way.
- /mod/discord/callback and /admin/discord/callback no longer sign in:
they keep a pending sign-in for 5 minutes (a Strict cookie) and the page
asks for the linked account's 2FA code (POST .../api/discord/code). Five
wrong codes and it must start again at Discord. The admin one also needs
the account to have 2FA on and not be locked.
- the bot's commands and buttons count only for a staff member with a
panel session that took a code (modpanel.discordBot.commandActor): the
password sign-in, or Discord and a code; not the game's token sign-in. A
new password, signing out everywhere or 2FA turned off end those
sessions (forget), and so the bot's use. Whose Discord it is still keeps
linked staff out of /discord moderation, and lets them close tickets.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Players choose how their chat bubble looks, and everyone sees it.
- style: a gradient of 2 to 5 colour stops (linear at any 45° step,
radial, or solid), its strength, text and border colours, outline
thickness 0-4, opacity 25-100%, and an animation (still, pulse, shimmer,
flow, rainbow) at 40-300% speed. lib/chatstyles.js keeps the one
canonical form: forgiving for saved accounts, strict for requests.
- in the game: Settings > Chat Bubble > Customize opens an editor with
presets (Ocean, Sunset, Forest, Midnight, Candy, Rainbow), a palette,
Swap, Random, Reset and Save, and a live preview. "Custom bubbles: Off"
draws everyone's bubbles normally on this computer only.
- on the web: the account page has a Chat bubble section with the same
choices.
- wire: xcs with no fields asks for the saved style, with twelve (or an
older client's 7, 10 or 11) saves it; the reply is the canonical twelve.
A typed line ("uc") carries its sender's style after the stock extra
field, only when it is not the default, so message and type stay where
the game reads them and unpatched clients are unaffected.
ajclient.swf is built with this and the six client commits before it.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Moderators send follow-up cards while helping players. The server skips its
sends-per-ten-minutes limit for them, and the client's per-recipient
session cap (ECardXtCommManager, now in swf-src and built from there) is
skipped for userInfo.isModerator.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Switching animals ("as") changed the active animal, but the client keeps
an editor model of each animal and was never sent the new one's data or
clothes, so an animal bought this session showed in the switcher and its
editor would not open until the next login. The switch is now followed by
its "ad" and its full item list.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- The status card is the players' card now: a title, "Online" and the
admin's message, players and rooms, uptime and memory, an optional banner
image and a "Play Burrow" button. The open report count is staff data and
is no longer on it.
- The admin page's Discord tab takes a banner image URL (http(s), at most 500
characters, blank for none), saved as discordBotStatusBanner and named in
the mod log. GET /burrow-status-banner.png serves a banner of our own.
- The game activity, moderation, bot audit and security logs are one card
shape (logCard): a summary line, a list of fields and when it was logged.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
With a trusted local proxy the address was the last X-Forwarded-For hop,
which behind Cloudflare is Cloudflare's own edge: every visitor shared a
handful of addresses for the rate limits, and the Turnstile check was sent
an edge as remoteip. When that last hop is in Cloudflare's published
ranges (https://www.cloudflare.com/ips/), CF-Connecting-IP is used, if it
is an address. From anywhere else the header is ignored: someone who
reaches the server directly could otherwise name any address, past the
rate limits, address bans and AJ_ADMIN_ALLOW. Neither header is read
unless config.trustedProxy is on and the request came from loopback.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- server: at most config.maxConcurrentCaptchaChecks (AJ_CAPTCHA_MAX_CONCURRENT,
24 by default, 1 to 100) Turnstile checks wait on Cloudflare at once; past
that the answer is captcha_unavailable at once, so a slow Cloudflare cannot
hold thousands of sockets open. The page's policy lets it connect to
challenges.cloudflare.com too.
- page: public/captcha.js gives up on a widget that has not loaded in 15 s,
or that loaded without turnstile.render, instead of waiting for ever, and a
render that throws counts as a failed answer. The game's captcha window says
to check the connection or a content blocker, with a "Try again" button.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
POST /api/register used accounts.register, whose scryptSync froze every
player for as long as each password took, so a burst of sign-ups was felt
in the game. accounts.registerAsync checks the same things, derives the
hash on libuv's pool (hashPasswordAsync), checks the name again after it
(another request may have taken it meanwhile) and inserts the account as
before. The game's own Create Account keeps the sync path.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- server: a typed name the filter (lib/chat-filter.txt) stops is
refused at xrn, with the game's warning and a line in the log; one
saved before is cleared at login (the animal takes the username, the
pet is "Pet"). the game's own word-id names are never looked at.
- client: LocalizationManager.translateAvatarName and translatePetName
pass a typed name through the player's own filter
(AJClient.filterName), wherever the game shows it. a name cannot be
left out, so with "Hide the whole message" its words are starred.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Approving and removing framed paintings was items.approve, which also
judges the items and pictures players make. masterpieces.approve now
guards it, on the server (POST /mod/api/masterpiece) and in the mod
panel's buttons and its "only ones I approved" filter. Moderators and
admins have it by default; seeing the Masterpieces page is still
player.view.
roles.load, once at start (setting permissionSplitMasterpieces): a role
list the admin changed, and a staff member's own grants and denies, that
held items.approve are given masterpieces.approve too, so nobody gains or
loses anything by the split.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
In a theatre, "Browser" puts a web page on the screen for that player
alone, beside "Your Video". The desktop client (1.3.3) draws it in a
sandboxed webview of its own over the game page, which tells it where,
what the game draws over it, and where to go; nothing of it goes to the
server.
- off by default: the admin panel's Debug tab turns it on for everyone
(setting theatreBrowser). the server marks the game page with
data-theatre-browser="on" as it sends it (lib/http.js), and the page
shows the button only when the server allows it and the client says it
can draw it, so older clients never see a button that does nothing.
- the boxes over the screen share one style (.aj-box), and a clicked
button no longer keeps Chromium 87's focus ring.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
b11ae1d made the server load discord.js at start, through lib/discordbot.js,
even with the bot off. update.sh installs no npm packages, so prod had none,
and every start failed with "Cannot find module 'discord.js'".
- lib/discordbot.js loads discord.js when the bot starts (a token and guild
id set), not with the server. without the package the bot stays off, with
a line in the log, and the panel's Start says to run npm ci. the two
message flags cards use are written as numbers, and the slash commands
are made when they are synchronized.
- deploy/update.sh runs npm ci --omit=dev when package-lock.json changed or
node_modules is missing. a failed install leaves the bot off; the game
needs no package.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The admin panel's "What they did" table, in the moderator panel too: the
latest 300 entries. A new permission, staff.log, which moderators and
admins have by default, guards the page and its route.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The account view's Lost access box gives the account a new random password
(12 characters, none that look alike), shown once with a Copy button. It
signs them out everywhere and forgets trusted devices; "Turn off their 2FA
too" is for a lost authenticator. Written to the mod log, without the
password.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The login's Guide option made a player a guide on their own screen only:
the room's avatar packet never said so, so everyone else drew a plain
player. "ac" now sends the guide field (bit 4, after a blend colour of 0),
which gives the guide's name tag and chat bubble on every client.
Guide is now given in the admin panel (Make guide / Remove guide, logged).
Asked for at login by anyone else, it is refused, with a plain message on
arrival. A guide's custom client can still leave it off; the official
launcher asks nothing, and a guide shows as one.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The rules were written into the client, so changing them meant a new
build. GET /rules.txt reads data/rules.txt on every ask (no restart
needed; data/ is what prod keeps between deploys and lets the server
write), making it with "Example" when there is none. The rules window
fetches it each time it opens: a line starting "# " is a heading in the
old rules' heading style, the rest is shown as it is written (escaped,
never HTML). 64 KB at most. buildVersion 75.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- accounts under a day old cannot paint for a frame: the easel's token is
refused and a message box says how long is left
(AJ_MASTERPIECE_MIN_AGE, 86400; the tests use 0).
- 10 new pictures an account in any 24 hours (config.masterpiecesPerDay),
counted in the database (masterpiece_uploads) so a restart does not
forget them; past it HQ says when the next one may go. a picture
approved before is not a new one.
- a picture a moderator or the admin approved is approved again as it is
framed, and the same picture waiting is approved with it, its makers
told: the same file (SHA-256), or the same painting saved and painted
again, which comes back as other bytes. lib/jpegprint.js reads every
8x8 block's average from a baseline JPEG's DC coefficients (~2.6 ms for
the Art Studio's 711x434); the same size with no block more than 2 of
255 apart is the same picture (a saved .ajart painted again: 1).
- staff taking a painting back forgets its picture.
- paintings from before get their hash and fingerprint a few at a time
after start; those a person approved make their pictures approved ones.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A switch in the pet chooser (the settings menu's own On/Off switch, at
the top left of the pet's picture) puts the pet that is out in the
avatar's place, for everyone, as at a Play-As-Your-Pet party: the pet
at the party's size where the avatar stands, turning as it walks, its
name on the name bar, chat balloons and emotes over it, the pet in the
HUD. Hidden at the party itself.
- kept as user var 9008 (9007 is the performance profile), so it holds
through rooms and logins and is kept for the next pet when the pet is
put away. the server tells the room by user communication type 13,
also to players coming in later.
- WorldPet and AvatarWorldView ask the avatar's own form instead of the
room-wide party test; a pet that cannot come into the room leaves the
avatar shown.
- the type-13 handler read a variable it never set, so every client took
every message for "off" and nobody else saw the form.
- the action menu's pet button does the pet's trick again (5c9b2e0 had
made it the switch, which only hid the avatar).
Flying pets keep to the ground's walls (the party lets them over).
buildVersion 74.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A "Music" page in both panels: an MP3 (MPEG layer III frames, 4 KB to
15 MB) becomes a den music track at once, with no restart.
- lib/custommusic.js: a custom den item made from "Jam On" (614) with a
new `audio` column, the file's version. Its abbrName is
CustomMusic<id>_<version>, which the content handler answers from
data/custom-music/<id>-<version>.mp3, so a new upload is a new name and
no game plays an old copy from its cache.
- games get it by "xdi" with no client change; players from the item
finder, or the shop when staff tick "on sale".
- deleting it takes it from every inventory and removes the file.
- /mod/api/music and /admin/api/music: list, play, upload (name, cost,
inShop in the query), delete; 30 uploads an hour per staff member;
"music uploaded"/"music deleted" in the mod log.
- new permission music.upload, on the Admin role by default; a role list
the admin has changed needs it ticked. The panels' CSP allows
media-src 'self' for the preview players.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
"pn" (EggPetHatchedPopup) saved `account`, which that handler never
defined since aa455f5: a ReferenceError after the name was set in
memory, so no reply went out and the game's loading spiral never ended,
and the name was not saved, so the popup came back at every login.
"account is not defined" at lib/pets.js in prod's log several times an
hour since 10-17.
qol.js names the egg it buys and waits for the answer.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A custom item change made the item and name packs again on the next
fetch, on the one thread every game shares: ~360 ms at 5000 items,
~1.6 s at 50000, after every change, players making them many times a
minute. Nearly all of it was the AMF3 writer.
- the writer fills one growing buffer instead of a Buffer per value
(byte-identical output, checked against the old one on every cached
pack): the item pack 230 -> 52 ms at 5000 items, 1524 -> 231 ms at 50000.
- a changed pack is made again at most every AJ_PACK_REMAKE_MS (15 s);
until then the one made before goes out with the custom item version
it has, and customItems.sendAll sends a game logging in what its packs
lack by that version. one remake at a time; deflated on libuv's threads.
- tests make the packs again at once (AJ_PACK_REMAKE_MS=0), and a run of
the items test checks the throttled case.
Busy evening simulated in-process (a change every 3 s, packs fetched
6 a second, 30 s): longest hold-up 329 -> 61 ms at 5000 items, 1648 ->
359 ms at 50000 (p99 240 -> 6 ms).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Every custom item's full def row went to every game at login, though the
item and name packs it fetched minutes before already have them all: with
5000 clothing and 452 den items that was 3.3 MB, 4.2 MB with the colours,
over the send backlog limit (94b8de8 raised it).
- a fetch of the item, den item or name pack notes, per address, how far
the custom items had changed; at login a game is sent the items changed
since, and those with a picture (the packs have no pictures). an address
that fetched nothing lately is sent all, as before.
- "xdi" rows carry the fields the client reads (addItemDef,
addDenItemDef), not the whole base row, and clothing is for any animal
as in the pack.
- accounts keep a digest of the state last written, not a copy of it
(~13 KB an account, ~185 MB on prod).
Measured locally with prod-sized data (20000 colours, 5452 items, 14k
accounts): the login burst 4.2 MB -> 1.5 MB (the colours are most of what
is left), live heap after start 419 -> 297 MB.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Prevent slow or periodic account/player lookup responses from replacing a newer search, make both dashboard layouts usable on narrow screens, and use the unified dashboard masterpiece routes for staff and owner review images. Propagate approved username changes through moderation-facing history and cover report-name propagation with an end-to-end regression test.
Remember a standing avatar's valid action and mirror marker, replay it after avatar creation for players entering or reloading a room, and clear it on movement or exit. Add an end-to-end regression test for late join animation sync.
Add owner/developer room-effect controls and chat shortcuts, staff movement that bypasses full or locked destinations, in-game moderation entry points, theatre video synchronization, and shared room effects.
Restore game and trade popups, reliably award refreshments and game rewards, support pet play outside parties, correct den placement categories, improve den item persistence, and refresh custom-item and masterpiece behavior.
Harden room, party, pet, minigame, and item state handling with matching feature and restored-system regression coverage.
Provide a single /dashboard entry point for owner and staff tools, with Discord OAuth sign-in for approved owner accounts and active staff. Add owner-managed dashboard access grants, staff server health and update visibility, filtering, moderation improvements, item controls, and per-animal clothing restrictions.
Replace staff-triggered password and 2FA resets with email-verified account recovery. Persist validated recovery addresses, use short-lived hashed recovery tokens, expose recovery flows in registration and account pages, and keep mail delivery disabled until its webhook configuration is present.
Cover dashboard aliases, recovery restrictions, Discord access, monitoring, item locks, wear rules, and staff behavior with regression tests.
Every custom colour and item def is written at login before the client
reads; at 20000 colours and 5000 clothing that is ~4.2 MB, over the 4 MB
backlog limit, so every login was cut off right after it succeeded.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
From the 18 October security audit (S-9, S-10).
- the moderator panel only refused a role the actions in its permission
map. hardware bans and lifting them were missing from it, and answering
ban appeals (which lifts the ban, the address's too), name requests,
paintings and reports were checked for player.view alone, so a Helper
could do all of them. each now needs its own permission (address.ban,
player.ban, player.names, items.approve, player.warn), with the rank
check the other actions have, and an action missing from the map is
refused. the page hides what the role cannot do.
- a new password, "Sign out everywhere", locking the account, turning 2FA
off or deleting the account now also ends its moderator panel sessions,
as the admin panel's reset already did, so a stolen panel session does
not outlive them.
- test/staff.js covers both, and fails without either fix.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- Discord: the account page links a player's Discord account through
Discord's sign-in (lib/discord.js); only linked names are shown on cards
(typed ones are cleared). A bot keeps the Server Booster badge on linked
accounts that boost. The game tells the client where the player is, for
the client's Discord rich presence (flashvars discordAppId).
- @username tags in chat, chat balloons and wall posts: only real players'
names (asked of the server, "xmn"), names with spaces too, drawn on a
blue box; a click opens the player's card.
- Settings: separate Music and SFX volume sliders for the old one.
- Device ids required: a launcher that sends none (before 1.3.0) is told
at the game's login "Your client is outdated. Update at
https://burrow.moe/download". AJ_REQUIRE_DEVICE=0 turns it off.
- Panels: clear a player's Jammer Wall posts; turning away masterpieces
and player items asks first.
- Item Giver: negative colour ids (the same colour written signed).
- buildVersion 71; the client rebuilt with Snipzil's sitting fix.
The 133 music files on the game's development CDN that no den item plays,
in public/music/ (78 MB) and lib/extramusic.js (items 6013-6145), each
titled with its file name; the owner's debug track (6012) with them. Files
that already are den items under another name (the same audio, or the
same track by name and length) are left out.
Introduce a bubble system that allows players to signal availability for
specific buddy games. Other players in the same room can click the
bubble to initiate a game. The implementation handles bubble visibility
for new arrivals and ensures bubbles are cleared when players leave
rooms or start other activities.
The game shows a name tag's badge to buddies only, except the News Crew
camera. AvatarWorldView now shows the Owner, Moderator and Verified badges
(def ids 63, 64, 76) to everyone too. ajclient.swf rebuilt with
tools/build-client.sh; buildVersion 61, so clients fetch it (PR #5's client
changes went out under 60 and may still be cached).
- Remove package-lock.json: the server uses no npm packages, which the
invariants check enforces (no supply chain to attack).
- Allow the two hosts the server really calls in .github/allowed-hosts.json:
cdn.jsdelivr.net (Twemoji pictures, lib/emoji.js) and vision.googleapis.com
(the optional SafeSearch check, lib/image-moderation.js). The github.com
mention in lib/emoji.js was only a comment, now reworded.
- logText strips line feeds with .replace(/\n/g, ""), the form CodeQL's
js/log-injection recognises as a sanitiser. The old [\r\n]+ to a space was
just as safe, but not recognised, so every log line using it was flagged
(34 alerts on main, 35 on this branch).
- /authenticate: the saved sign-in is decided by what the server finds for
the refresh token, not by whether the request has one
(js/user-controlled-bypass). A token that is not good is still refused
with error_code 100.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Staff and moderation
- Invisible staff (!invisible, "xiv"): hidden from players, half see-through
to other staff, cannot chat while hidden. New permission staff.invisible.
- Summon and goto land on the player's exact spot ("xgt" before the move).
- Custom warnings (!warn PLAYER custom TEXT), shown in the warning popup.
- Mod notes (!note, !notes; lib/modnotes.js), on the player page and the
dashboard.
- Granular permissions: per-role overrides (setting rolePermissions) and
per-account grants and denies, applied live to staff who are playing
(refreshStaff re-sends "xsp").
- Item control (lib/itemcontrol.js): lock items out of the item finder
(!lock, !unlock, !locked), take an item from a player (!take), delete a
custom item from the game and every inventory.
- GET items/find: search any item by name or id, marked locked, for the
dashboards' quick lock.
Player-made items (lib/playeritems.js, "xcm")
- The Item Maker: make, rename, set the worn look, delete. 5 a day, 20 in all;
names go through the name filter.
- Admin switches: Item Maker on/off, new items wait for approval, and a
separate switch (on by default) that holds every player-uploaded picture
for a moderator. Review queue for items.approve (moderator and up).
- Pictures (lib/itemart.js): PNG, JPEG and GIF cleaned of metadata, BMP
converted to PNG; 512px and 300KB at most once cleaned.
- Worn as the maker chooses: a sticker (the picture) or a texture (the
item's shape painted with the picture).
Picture safety
- A picture waiting for approval is never served publicly: /itemart/ 404s it,
and it is only shown through /account|/mod|/admin/api/itemart to its maker
and to staff who review or make items.
- A picture turned away or taken off is remembered by SHA-256 and cannot be
uploaded again.
- Three strikes: three pictures turned away stops a player's uploads until a
moderator lets them again. Staff can stop or allow uploads by hand.
- Accounts under 24 hours old cannot upload pictures (AJ_ITEM_ART_MIN_HOURS);
uploads capped at 10 a day.
- Optional Google Cloud Vision SafeSearch (lib/image-moderation.js) for item
pictures and Art Studio paintings when AJ_GOOGLE_VISION_API_KEY is set;
fails closed when the scanner is unreachable.
Chat
- Emoji: Twemoji pictures served at /emoji/<codepoints>.png and cached in
data/emoji (lib/emoji.js).
- Smart spam filtering before the word filter (lib/chatspam.js): long runs of
one character, repeated words and lines, huge words and emoji floods are
tidied, and repeats within 20 seconds are dropped.
- Typing indicator: "xty" is passed on to everyone in the room who can see
the player, at most every 2 seconds.
Games (lib/minigames.js)
- Room games can be played together: a MULTIPLAYER table gives a game a
waiting list (Single Player / Multiplayer). Players in the same room are
matched, taken into the game together, and each one's moves are relayed to
the others. Gem Breaker is the first: two players, "pos", "shoot" and
"playerLost" relayed.
- Gem Breaker's start message now lists each player's id. Without it no
player counted as local, so even single player could not aim.
Other
- Players stay connected through the client's new 75-minute AFK limit
(idleTimeoutMs 80 minutes).
- Jam-a-Grams carry custom items and colours; Jammer Wall avatar photos are
validated (walls.js photoParam).
- Weak passwords refused (common words, or containing the username).
- Code-scanning fixes: every logged value goes through logText
(lib/logtext.js) against log injection, HSTS, path-only error logs, a
single file read in lib/names.js.
Tests: items (pictures, approval, strikes, re-upload refusal, the hidden
waiting picture, the dashboard search), staff (invisibility, goto and summon
spots, custom warnings, notes), buddygames (two-player Gem Breaker, the
typing relay), and updates for main's verified badge and spawn rooms.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Hardware bans, panel search and logs, two worlds and the verified badge,
with the branch's staff roles kept: full rooms let in active staff, and
address search stays with the roles that may ban addresses.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
A sign-in without device ids is let in unless AJ_REQUIRE_DEVICE=1. An
account seen on banned hardware is still refused, with the ban's reason,
when its client sends no ids. The privacy policy no longer says the
client cannot sign in without them.
- rooms hold 40 players. a player not starting in their den arrives in
a random room of config.spawnRooms that has space (AJ_SPAWN_ROOMS
overrides); with every one full, the emptiest, over the cap.
- two worlds, Aldan and Congo (AJ_WORLDS sets how many): each its own
copy of every land, dens and parties shared. a player arrives in a
random world with space and keeps it through dens and parties.
- the settings menu's World row is back: the server sends the worlds'
names (generic list 16) and the world list (rm), and the client asks
for the names once at login. a buddy's "go to" leads into their
world, whose name the buddy card shows. "Find Open World" (on by
default) joins a full room in a world with space.
- the panels show the world with the room. the test harness pins one
world and the township. buildVersion 60.