Blog

Six guides, two reference pages, and a warning

2026-09-07

The site now covers the whole path from "I have never run this" to "I am hosting a world I built with an avatar I made":

• Using the client and the modified one — including the parts of the interface nobody explains, like why the avatar list matters more than the avatar.
• Running a server — build, configure, moderate, host content, go public.
• Writing a mod, now with a crash course in Lua itself, so it works if you have never written a line of it.
• The Shaper, with every panel, menu and widget documented one by one.
• RWX avatars.
• The protocol and inside the client — the explanations, not the byte tables. Those stay in docs/.

And Trust & safety, which is the one to read first. An unmodified Worlds client will run code any server hands it. That is not a bug in somebody's build, it is how WorldScripts were designed, and it has been true the entire time.

This site exists now

2026-09-07

The documentation has been sitting in Markdown inside the repositories, where approximately nobody reads it. So: Neocities, hand-written HTML, a repeating background, the whole thing.

The reference documentation stays in docs/. This is the part that says why, and the part with the guides in it.

Where the project is

2026-09-07

A summary for anyone arriving new. Three programs, all running:

• WorldServer — the preserved server. Original protocol, nothing added.
• AikoWorlds — the same code with a capability announcement and SQLite, all switchable back off.
• WorldsClient — the client modification: chat encryption, a server selector, Lua mods, bots, and the fix for the downloaded-code hole.

Next: inventory and shared object state. Both have a thread to pull; neither is blocked.