module-uo's half of ENGAGEMENT.md Phase 11: every trigger DECLARATION, the
wire-kind mapping that fires them, and the three registered audiences. No rule
and no template is seeded here -- that is 11b -- so nothing this adds sends
anybody anything until an operator writes a rule.
server/config/shardTriggers.js declares the 24, grouped by the audience kind
each family exercises, and every variable carries the `example` the template
editor previews and test-sends with. Ceilings: 10 `owner`, 2 `members`, 7
`authenticated`, 2 `staff`, 3 `admin` (the value core adds in the same window).
`uo.cheat.detected` at `staff` is the declaration the lattice exists for.
server/utils/shardEngagement.js maps the wire to those ids, hung off
shardIngest.ingest beside the SSE broadcast and the push tickle, and reads like
shardPush.js on purpose -- owner resolution is why neither can be a pure mapper.
Three things live here because a rule cannot express them:
* Transitions. champ.update and city.update are full-state upserts, so without
a per-process tracker a sidecar reconnect reads as twenty spawns starting.
A FIRST sighting is never a transition.
* Thresholds. conditions.js compares a declared variable against a LITERAL, so
"within 24 hours of dismissal" is not expressible; and vendor.listing is a
sweep frame re-emitted on any price change, so per-frame would flood. The
crossing is tracked here and `hoursRemaining` is declared so an operator can
still narrow with `is at most`.
* The members audience. "The members of THIS guild" differs every firing, so
it travels on the envelope as recipientUserIds (Phase 6 decision 2).
**The fan-out runs BEFORE the state write, and that ordering is load-bearing.**
account.unlinked drops the shard_account_links row that names the one person who
needs to be told; house.remove drops the house whose stored ownerAcct is the only
place a collapsed house's owner appears; guild.leave/remove need the roster and
board mirrors to name who left. Resolving afterwards finds nobody, every time.
Four rows of 8.6 deliberately do not ship, each with its reason recorded in
docs (docs#194): uo.market.item_listed (a saved search, no per-user query store),
uo.guild.joined (core's team.member.joined already fires for it -- a UO guild IS
a Team and this module is the provider), uo.link.requested (no addressable
recipient by construction, ~5-minute TTL), and uo.points.rank_changed's personal
half (top[] names a serial, links are keyed by account).
coreApi -> ^1.8.0: the module now calls registerEventTriggers and declares
`ceiling: 'admin'`, so a 1.7.0 core would refuse the ceiling and a 1.6.0 one
would not have the method at all.
39 new tests; 509/509 pass. check:imports, check:bundle and check:swagger clean.
Co-Authored-By: Claude <noreply@anthropic.com>
95 lines
3.6 KiB
JavaScript
95 lines
3.6 KiB
JavaScript
const { query } = require('../../core')
|
|
|
|
const COLS = 'account, user_id, char_name, linked_at'
|
|
|
|
// Upsert a link. account is the PK, so a re-link moves the account to the new
|
|
// user (the sidecar already treats /link/confirm as authoritative).
|
|
async function upsert({ account, userId, charName }) {
|
|
await query(
|
|
`INSERT INTO shard_account_links (account, user_id, char_name)
|
|
VALUES (?, ?, ?)
|
|
ON DUPLICATE KEY UPDATE user_id = VALUES(user_id), char_name = VALUES(char_name)`,
|
|
[account, userId, charName || null],
|
|
)
|
|
return getByAccount(account)
|
|
}
|
|
|
|
async function getByAccount(account) {
|
|
const rows = await query(`SELECT ${COLS} FROM shard_account_links WHERE account = ? LIMIT 1`, [account])
|
|
return rows[0] || null
|
|
}
|
|
|
|
const listByUser = (userId) =>
|
|
query(`SELECT ${COLS} FROM shard_account_links WHERE user_id = ? ORDER BY linked_at DESC`, [userId])
|
|
|
|
async function isOwnedBy(account, userId) {
|
|
const rows = await query(
|
|
'SELECT 1 FROM shard_account_links WHERE account = ? AND user_id = ? LIMIT 1',
|
|
[account, userId],
|
|
)
|
|
return rows.length > 0
|
|
}
|
|
|
|
const remove = (account, userId) =>
|
|
query('DELETE FROM shard_account_links WHERE account = ? AND user_id = ?', [account, userId])
|
|
|
|
// Drop the mirror for an account regardless of which user held it — used to
|
|
// reconcile when the tie is severed at the source (an in-game [unlink →
|
|
// account.unlinked event, or a site-side DELETE /link/{account}).
|
|
const removeByAccount = (account) =>
|
|
query('DELETE FROM shard_account_links WHERE account = ?', [account])
|
|
|
|
|
|
// A bound on every "resolve a set of people" read below. It mirrors core's own
|
|
// `MAX_AUDIENCE` (engagementRecipients.db.js) rather than importing it: a module
|
|
// cannot reach into core's models, and the number this file has to respect is
|
|
// "no more ids than core will accept" whatever core calls it.
|
|
const MAX_AUDIENCE = 5000
|
|
|
|
// **Website user ids for a set of game accounts.** The bulk form of
|
|
// `getByAccount`, and the one the engagement mapper needs: a guild event's
|
|
// audience is its members, and turning a roster into a set of people is one join
|
|
// rather than one query per member (Phase 11).
|
|
//
|
|
// DISTINCT because two characters on one guild roster can share an account, and
|
|
// the caller wants people rather than characters.
|
|
async function userIdsForAccounts(accounts) {
|
|
const wanted = [...new Set((accounts || []).filter((a) => typeof a === 'string' && a))]
|
|
if (!wanted.length) return []
|
|
const capped = wanted.slice(0, MAX_AUDIENCE)
|
|
const marks = capped.map(() => '?').join(', ')
|
|
const rows = await query(
|
|
`SELECT DISTINCT user_id FROM shard_account_links WHERE account IN (${marks})`,
|
|
capped,
|
|
)
|
|
return rows.map((r) => Number(r.user_id)).filter((n) => Number.isInteger(n) && n > 0)
|
|
}
|
|
|
|
// **Every website user with a linked game account** — the `uo.linked.accounts`
|
|
// audience (ENGAGEMENT.md §5.1a). The set an operator reaches for first, and the
|
|
// one a `not` composes against ("everyone who has NOT linked").
|
|
//
|
|
// It returns ids and nothing else: §5.1a rule 2 is that a module's resolver
|
|
// never sees an address, a channel or a template, and core maps ids to addresses
|
|
// on its own side after preferences, suppression and the verification gate.
|
|
async function allLinkedUserIds(limit = MAX_AUDIENCE) {
|
|
const rows = await query(
|
|
'SELECT DISTINCT user_id FROM shard_account_links ORDER BY user_id LIMIT ?',
|
|
[limit],
|
|
)
|
|
return rows.map((r) => Number(r.user_id)).filter((n) => Number.isInteger(n) && n > 0)
|
|
}
|
|
|
|
module.exports = {
|
|
upsert,
|
|
getByAccount,
|
|
listByUser,
|
|
isOwnedBy,
|
|
remove,
|
|
removeByAccount,
|
|
userIdsForAccounts,
|
|
allLinkedUserIds,
|
|
MAX_AUDIENCE,
|
|
}
|
|
|