Wiki

Reference material for questions that deserve more than disappearing Discord messages. Start with the practical guide paths if you have a build, rights, or feedback question. Every article works like a wiki: spot something wrong or out of date, report it from the page, and good corrections get you credited on the article. Pages with fast-moving facts carry the date they were last checked.

16 source-linked articles16 cited sourcesLatest check: 2026-08-29Corrections openNo referral linksNo tracking

Make it think

  • Install Ollama, pull a small local model, and wire one self-contained HTML file to its API to get a character talking back to you, no account, no cloud.

  • Finite state machines, behavior trees, and utility AI cover most shipped game AI. Here is how each one works, when to use it, and where it breaks down.

  • The production tradeoffs for LLM-driven NPC dialogue: local vs cloud costs, keeping NPCs in character, and the four failure modes that block a ship.

  • The budget mindset for shipping AI in games: frame time vs request latency, quantization tradeoffs, on-device memory limits, and cloud cost math.

Make it look and sound

Ship it safely

Show your work

  • How to format a showcase forum post so it renders correctly on the site: thread title, screenshot rules, description length, and what happens automatically.

  • How jams work here: enter by posting in the submissions forum with the jam's tag, vote by emoji reaction, and see winners on the podium at /jams/.

  • How the community's feedback loop works: name a specific moment, explain the effect it had, and leave a builder with a useful next question to test.

  • Every slash command, every background system, and how Discord activity becomes curated site content — the full map of how it all connects together.