Campfire rules
Keep the fire useful.
Ant Trail’s community space should make bugs easier to fix, ideas easier to understand, and player history safer to share.
Accounts
Read publicly. Post through a verified identity.
Campfire viewing stays public. Creating posts or replies requires a verified Ant Trail account and a public trail handle. Email addresses remain private.
Useful reports
Describe the path to the problem.
Do
Say what you were doing, what you expected, what happened instead, and which Ant Trail/WoW versions were involved.
Do
Include redacted Lua errors, screenshots, and exact reproduction steps when they genuinely help.
Avoid
“It broke” with no context, repeated bump posts, or opening a new thread for every symptom of the same known issue.
Avoid
Posting accusations about another player when the issue can be explained without naming them.
Player history
Public support is not a file dump.
Never post passwords, authentication tokens, account identifiers, or a full SavedVariables file to a public thread. Ant Trail’s own history can include character and social context that is unrelated to a bug.
If a maintainer genuinely needs a raw recovery file, the project should provide a private support path with explicit instructions. Until that exists, keep the file local and preserve an untouched backup.
Around the fire
Disagree with ideas, not with people.
- No harassment, threats, hate speech, impersonation, or doxxing.
- No posting private information about another player.
- No spam, scams, malware, or unrelated promotion.
- No instructions for cheating, botting, exploiting hidden game data, or bypassing Blizzard restrictions.
- Keep bug threads focused enough that someone can reproduce and resolve them.
Maintainer tools
Moderation should leave a trail too.
When the shared Campfire goes live, moderator actions should use clear statuses rather than silently rewriting history. A practical production board should support closing, merging, marking duplicates, marking fixed/answered, removing private information, and handling abuse reports.
Internal moderation logs may be appropriate for abuse prevention, but they should not become public player dossiers.
Known Tracks
Duplicates can strengthen one report.
If several players encounter the same problem, the long-term design should let maintainers merge or link those reports into a Known Track. The goal is to preserve evidence and discussion without fragmenting the same bug across ten threads.