Files
burrow-server/lib/colours.js
T
SnipzilandClaude Opus 5.5 e05565787f feat(server): staff tools, player-made items, picture safety, chat, multiplayer games
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]>
2026-10-17 21:44:10 -04:00

75 lines
2.9 KiB
JavaScript

"use strict";
const {logText} = require("./logtext.js");
const accounts = require("./accounts.js");
// custom colours. the game stores a colour as four palette indexes packed in
// one number, which leaves no room for "any hex colour". so a number in a
// range no real colour uses (CUSTOM_BASE and up) is instead the id of an
// entry here: the four RGB values that layer is drawn with. the patched
// client keeps the same table (PaletteHelper.customColors); the server sends
// it at login and announces every new entry to everyone before anybody can
// receive a colour that uses it.
const CUSTOM_BASE = 0xFD000000; // top byte 0xFD: unused by every item and animal def
const config = require("../config.js");
const MAX_ID = 0xFDFFFFFF; // the last id with the top byte 0xFD
const MAX_RGB = 0xFFFFFF;
const SCHEMA = "CREATE TABLE IF NOT EXISTS custom_colours (id INTEGER PRIMARY KEY, rgb TEXT NOT NULL UNIQUE)";
const byKey = new Map(); // "r1,r2,r3,r4" -> id
const entries = new Map(); // id -> [r1, r2, r3, r4]
let nextId = CUSTOM_BASE; // one past the highest id ever given: ids are never used twice
const load = () => {
const db = accounts.database();
db.exec(SCHEMA);
for (const row of db.prepare("SELECT id, rgb FROM custom_colours").all()) {
byKey.set(row.rgb, row.id);
entries.set(row.id, row.rgb.split(",").map(Number));
nextId = Math.max(nextId, row.id + 1);
}
console.log(`[colours] ${logText(entries.size)} custom colours`);
};
const valid = rgbs => rgbs.length === 4 && rgbs.every(value => Number.isInteger(value) && value >= 0 && value <= MAX_RGB);
// the id for these four RGB values, making the entry if it is new and
// `mayCreate` is not false. returns {id, rgbs, created}; null when the
// values are bad, and {full: true} when a new entry would be needed and may
// not be made (the table is full, or the asker has made enough today).
const allocate = (rgbs, mayCreate = true) => {
if (!valid(rgbs)) {
return null;
}
const key = rgbs.join(",");
if (byKey.has(key)) {
return {id: byKey.get(key), rgbs, created: false};
}
if (!mayCreate || entries.size >= config.maxCustomColours || nextId > MAX_ID) {
return {full: true};
}
const id = nextId++;
accounts.database().prepare("INSERT INTO custom_colours (id, rgb) VALUES (?, ?)").run(id, key);
byKey.set(key, id);
entries.set(id, rgbs);
return {id, rgbs, created: true};
};
// [id, r1, r2, r3, r4] for every entry, in groups small enough for one message.
const chunks = (size = 200) => {
const all = [...entries].map(([id, rgbs]) => [id, ...rgbs]);
const out = [];
for (let i = 0; i < all.length; i += size) {
out.push(all.slice(i, i + size));
}
return out;
};
// is this number a colour the game can draw: one of its own (anything below
// the custom range), or an entry of the table?
const known = id => id < CUSTOM_BASE || id > MAX_ID || entries.has(id);
module.exports = {load, allocate, chunks, known, count: () => entries.size};