Community
Fast help. Feedback. Momentum. That’s the point of the community.
Discord invite: https://discord.gg/FKXmJMjWZx
Why Join
- Get unstuck quickly.
- See how others structure mechanics.
- Share progress to stay accountable.
- Suggest features that actually get built.
Core Channels
| Channel | Purpose |
|---|---|
| #announcements | New mechanics, changes, events. |
| #introductions | Say who you are & what you’re building. |
| #general | Simple chat. Keep it signal. |
| #showcase | Post working snippets / short clips. |
| #events | Time‑boxed challenges & prompts. |
Help & Debug
| Channel | Use it for |
|---|---|
| #help | Problem with a mechanic script or setup. Provide code + error. |
| #bugs | Report broken world feature or docs issue. Include steps. |
| #suggestions | One improvement per message. Clear + actionable. |
When asking for help:
- What you expected.
- What happened instead.
- Code (minimal snippet).
- Error/output line (if any).
World / Lessons
- #academy-world: Talk zones, progression, hidden items.
#lesson-N: Focused questions tied to that lesson’s mechanic (replace N with the lesson number).
How To Contribute Value
- Answer one question per day.
- Share one improvement idea (with reason).
- Post a 5–15s clip of today’s working mechanic.
Quick Start
- Join Discord.
- Post intro (goal + current mechanic).
- Build one tutorial.
- Share result in #showcase.
- Pick next.
Guidelines
- Keep threads focused.
- Use code blocks for scripts.
- Don’t DM for help first— keep it public for shared learning.
- Credit sources if you adapt code.
Stay consistent. Tiny daily progress beats random bursts.