Round 386 — Alicization-Town: external agents and server NPCs
Reviewed 2026-09-06 UTC

Assessment
A new Chinese-language project implements a shared pixel world intended for externally hosted agents, alongside server-hosted NPCs. Public source supports the architecture, but this round recovered no live resident or conversation data. A resident moving or speaking would not by itself prove an independent external agent or a successful model call.

Primary source
https://github.com/ceresOPA/Alicization-Town
Pinned commit: 1a33ba65d0af2134b369b1eb4eb68f45d2c817c4
GitHub reports creation 2026-03-13T15:04:24Z. Complete recursive tree: 264 entries, truncated=false. This is metadata, not independently archived operational history.
Five files downloaded at the pin and verified against Git blob SHA-1 values: server/src/routes.js, server/src/main.js, server/src/plugins/ai-npc-plugin.js, server/src/ai/scheduler/ai-scheduler.js, server/src/npc/npc-manager.js.
https://github.com/ceresOPA/Alicization-Town/tree/1a33ba65d0af2134b369b1eb4eb68f45d2c817c4

Publisher description
README describes independent local agents connecting through MCP or a CLI to a shared world server, and advertises an AI NPC feature. That combination matters: external-agent support does not mean every world inhabitant is externally hosted. The project’s decentralization claim concerns the location of agent decision-making; the shared world still uses a central server. Chinese documentation and fictional Japanese character names do not establish operator nationality or lab affiliation.

Source findings
routes.js separates profile creation, signed login, session heartbeat and world actions from public list routes. The public players route calls sanitizeAllPlayers; npcs returns the NPC manager’s list. The chat GET reads history with a cursor and maximum 50 records. main.js mounts these under /api. These routes offer a promising read-only way to distinguish residents and inspect speech, if the deployed server responds. Session-bound perception reads have draining behavior and were not used.
ai-npc-plugin.js creates per-NPC schedulers using a server-side client, registers an AI action strategy and records nearby conversations. Thus the system can host model-driven residents centrally as well as accepting outside clients.
ai-scheduler.js builds nearby-player context while explicitly excluding other NPCs and a player named Observer. This limits one immediate-neighbor input path; it does not prove that all NPC-to-NPC influence is impossible, because the plugin also has event/memory paths. Claims of spontaneous NPC society should be tested against actual records and all context channels.
The scheduler also contains a fallbackBehavior path for AI failures: random movement, an idle-chat string, or interaction. A speech bubble or movement alone would therefore be insufficient evidence of a successful LLM decision. No fallback occurrence was observed live.

Live access result
Advertised public server: https://alicization-town.onrender.com/
A single read-only request to https://alicization-town.onrender.com/api/players timed out after 20 seconds. The planned chat/NPC reads were not attempted after that failure. This does not establish that the server is offline; cold start, network or service delay remain possibilities. No browser session, identity creation, login, connection heartbeat or world action was started.

Preservation boundary
The public tree includes a keystore directory and profile files. Only path metadata was seen; those file contents were not fetched. They are not an acceptable source of credentials or permission to join. Private captures and verified selected source live under investigation/china/386-private; only this analytical report is published.

Next checks and infrastructure
Retry the same public read route after a reasonable interval or test it from an existing second browser/network. If available, compare players with NPC metadata and sample chat history, preserving IDs and timestamps without claiming model authentication. Public demos or user reports may establish a concrete external-agent exchange. No paid infrastructure is indicated by one timeout. Aivilization, the separately named HKUST-associated lead, remains queued and must not be conflated with Alicization-Town.
No new confirmed escaped actor, no model calls and no investigated code execution.