TeraCreators Help
Published community documentation
TeraCreators Help started when I needed to report a gameplay bug. The search for a reporting path exposed a larger need. New players needed definitions and stable instructions, but useful answers were spread across Discord discussions, company documents, and other reference material.
I built the guide as a player and contributor. It grew into a public help site for five games.
Problem and audience
The audience was the player community. Experienced players used terms that new players did not know. The same questions appeared often. Answers were useful, but their original locations made them difficult to find and reuse.
Source material and my contribution
I collected company documents, community knowledge, messages gathered with Discrub, gameplay screenshots, and examples from users. I reviewed, structured, explained, published, and maintained this material as a public help system.
Documentation decisions
| Need | Decision |
|---|---|
| Players needed help at different stages | Organize the guides in gameplay order. |
| New players did not know common terms | Define terms where players first needed them. |
| Members linked to the same answers | Create stable pages that people could browse and share. |
| Written steps needed visual context | Add screenshots from gameplay and user examples. |
| Five games needed separate help | Use one documentation system with distinct guide areas. |
Published result
The result is a public Docusaurus site with repeatable page models, navigation based on player tasks, screenshots, and a docs-as-code publishing workflow.
On April 15, 2026, I revised the Havoc Hotel 3 rescue guide. I added direct links from each location name to its instruction section and made the section labels match the list. The recorded change shows the revision.