- 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 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]>
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]>
- 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.
- the client (1.3.0) sends one-way hashes of the device's ids at
sign-in; the server keys them again with a secret of its own
(data/device-key) and keeps them per account (lib/devices.js). a
sign-in without them is refused with 426 (AJ_REQUIRE_DEVICE=0 lets it
in), so 1.2 clients cannot sign in.
- hardware bans: every device an account used in the last 90 days.
any id but a network card blocks sign-in, sign-up and the game, on
any account. a network card match, ids that look altered, or a device
shared with a banned player raise hardware alerts instead.
- both panels: hardware ban and lift, the account's hardware ids,
search by hardware id, other accounts by device or address, a
timeline (bans, staff actions, reports, alerts), and hardware bans
and alerts in the bans tab.
- jam-a-grams and wall posts go into the chat log, the filtered ones
marked not sent. chat search filters by kind, by what the filter
stopped, and from a time back; each player's page lists their
jam-a-grams and wall posts, sent and received.
- account search runs on the server and ranks exact names first, then
names starting with the search; the admin panel no longer downloads
every account. hidden tabs only refresh the waiting counts in the
title. masterpieces can be searched by maker, approved ones too.
reports can show the reported player's chat at the time. links follow
the open tab and player.
- admin actions on accounts go into the moderator log.
- privacy policy covers hardware hashes and the new logs.
- the buddy list and last-seen times ("bl", "xls") come unasked at login
- the den owner is sent the den's items on a switch
- a clothing gift goes by its picture's id; the shop page is the Item giver
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Staff with the new items.create permission (admins, and the new Developer
role) make clothing and den items from the game's own art: an existing
item under a new id (50000 on), name, price, members-only flag and choice
of its colours. No restart of the server or of anyone's game:
- lib/customitems.js keeps them (custom_items table) and puts them into
the server's tables and the packs new games fetch (defpacks.setCustomItem)
- games already playing get the def rows in "xdi"; so does every game at
login. The client adds them (ItemXtCommManager.addItemDefs,
DenXtCommManager.addDenItemDefs, both now in swf-src; rebuild with
tools/build-client.sh)
- they are sold first in the two shops of oddities and found by the item
finder; an item can be renamed, repriced, recoloured and taken off sale,
never deleted (players may own it)
- the moderator panel has an Items page; in game, "!item clothing|den ID
NAME" and "!item list"
- the Developer role holds only staff.list and items.create. The panel's
pages that show players (players, chat, reports, requests, bans,
paintings) now need player.view, which helpers and up have
test/items.js covers it end to end, including a restart (withServer can
keep its database for that).
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The smoke, features, account and qol tests had fallen behind the server
and failed before reaching their end. Each now checks what the server
does on purpose today:
- harness: the chat filter messages the server sends unasked ("xfl"
after every login, "xfa" on the first room) are set aside like "zs".
- smoke: a banned account's sign-in is refused with "account_banned", so
the login-choices check uses a fresh account instead of the banned Carol.
- features: a shop's name comes from its room file, read the first time
anyone goes in (the first visitor sees a name made from the path). A
scout goes in first until the file is read, so the check no longer
depends on what an earlier run left in cache/.
- account: a deleted account's name is held for NAME_HELD_DAYS, so taking
it again right away is "username_taken".
- qol: the commands page sets what to type in italics.
And on Windows: withServer waits for the server process to exit before
removing its data directory, and retries; the database stays locked until
the process is gone, and the cleanup's EPERM hid the test's own result.
All seven test files pass (smoke, features, account, qol, buddygames,
restored, and staff in the next commit).
Co-Authored-By: Claude Opus 5.5 <[email protected]>