An event is a reason to open the site on a date, and a page that is still useful on Tuesday. It is not a plugin, a new subforum, or a Discord voice channel you forgot to write down. Most “dead after the AMA” boards did not fail at marketing. They failed at leftover: the guest left, the sticky stayed, the temporary node stayed empty, and the next stranger landed in a hallway named after last month.
This is logistics. It is not the XenForo engagement tour (What’s New, watches, thread types). It is not the member 30-day calendar. It is not how you grow DAU. Those articles already told you that a contest rents a week of posts. This one is how you run the week so the rent buys an artefact: an AMA transcript, a patch-note article, a seasonal recap, a prefix people can filter next year.
XenForo stock will not run raffles or “post of the month” for you. The engagement article already said that. Discourse’s official Calendar plugin will put a dynamic calendar in a topic; the 2026 hosted Business grid also names Events as a plan feature. Neither product will invent an owner, a date, or a staff reply budget. If you cannot name those three, do not buy a calendar.
Community notebooks we queried for XenForo operator practice did not contain an AMA or contest playbook. What they did contain is the furniture this article will keep using: do not post casually as the root Admin account, and do not spawn a node for a temporary mood. Broad rooms plus prefixes beat a deep tree of empty event forums. The rest is operational practice, labelled as such.
What an event actually is
Write the sentence before you create a thread.
| Sentence | That is an event | That is not |
|---|---|---|
| “On Thursday at 19:00, this person answers questions in this thread” | An AMA | A Discord stage you never transcribe |
| “For ten days, post X, we pick Y, leftover is a gallery” | A contest | A prize with no prompt and no end date |
| “Version 3.2 shipped; this article is canon; discussion lives next door” | A patch-note edition | A 40-reply argument titled “new update??” |
| “Until the season ends, this prefix and this weekly thread are the room” | A season | A new category you will not delete in October |
| “Every Friday we ask a question a stranger can answer” | A ritual | An event. Do not staff it like one |
An event has a start, a stop, an owner, and a leftover. A ritual has a cadence and no leftover to archive. Mix them and you will “close” Friday Links in a panic because someone called it a campaign.
If the leftover is “we had fun,” you ran a party. Parties are allowed. They are not how you keep a room alive when the hype fades. If the leftover is a searchable thread with a prefix people will still use, you ran an event.
Four types, four leftovers
Pick the type. The chrome follows.
1. AMA — a person, a clock, a transcript
An AMA is one human (or a small panel) answering in public for a defined window. The leftover is the thread, not the vibe.
What works. A guest the room already wanted. A start time in the title. A first post that says who they are, what is on the table, what is off, and when the window closes. Staff who host (queue, merge dupes, pin a late answer) rather than perform. Answers in the thread, not “we covered that in voice, you had to be there.”
What fails. Surprise AMAs with no watchers on the room. Guests who only speak on Discord. A root Admin account asking “so what do you all think??” in the same voice it uses for bans. XenForo community practice is blunt: casual posts from a badge that can suspend people shrink the room. Official announcements stay on the system-like account. The AMA host should be a personal profile — staff if they must be identifiable, unbadged if they are just another member asking the first question.
XenForo shape. One discussion thread in the room that already moves. Prefix AMA (or Live, then flip to AMA when it closes). Sticky for the window only. One Block notice for people who can actually attend, with a page criterion if you can target the forum. Feature it if guests should see it on the door; unfeature the day after. Do not create Forums → Events → July AMA. That node will be empty in August and still appear in the tree.
Discourse shape. One topic in the category people already watch. Tag ama. If you have the official Calendar plugin (hosted listing: Business and Enterprise; self-host is the plugin, not a core toggle), put the session on the topic calendar so local time is honest. Pin for the window. Do not invent a fifth category named Events.
Leftover. Change the prefix/tag to a closed state. Edit the first post with a two-paragraph recap and links to the three answers you will quote for a year. Unsticky. Unfeature. Leave the thread open for slow questions or lock it if the guest is gone — pick one and say so.
2. Contest — a prompt, a rule, an end, a gallery
A contest is a prompt with a stop date. The leftover is a gallery or a shortlist, not a winner announcement that 404s.
The engagement article already warned you: contests attract entries, not members. Active-user growth said the same in metric language: count the spike separately; if next week returns to baseline, you rented reach. That is allowed for a launch. It is not a retention system. Design the leftover so the rental leaves a room people still browse.
Rules that prevent a mess.
- One prompt a stranger can finish without lore. “Show the desk you work at” beats “best 2014 raid screenshot.”
- One entry per person, in that thread or with a dedicated prefix. Do not invent a contest forum.
- Staff-judged or member-voted. If voted, say what you will do with the result. Then do it. An unanswered official poll is worse than no poll.
- Prize that does not require a shop. A 0-point trophy, a banner for a month, a feature, a mention in the recap. The ranks article is the trophy design. A points economy is a different product; do not stand one up for a screenshot contest.
- End date in the first post and on the notice. When it ends, you end it.
XenForo. Prefix Contest on the live thread; Gallery or Complete when you recap. If entries need to be separate threads (builds, characters), they still live in the existing creative forum with that prefix — not in Contests / July. Article type for the recap if it is a long artefact; discussion for the prompt. One Floating or Block notice, dismissible, dead on the end date.
Discourse. Tag contest. Calendar event on the topic if you have Calendar and the close date matters. Recap as a new post in the same topic, or a linked topic staff edit into the first post. ?solved=yes is the wrong tool; this is not a support question.
Leftover. Recap thread or recap post with the shortlist and a sentence about what you will run next, or that you will not. Unsticky. Turn the notice off the same hour. If you awarded a reversible banner, set a calendar reminder to take it off. Trophies are not reversible; do not trophy “entered July contest.”
3. Patch notes — canon next to conversation
Patch notes are an edition. The newsroom article already split the jobs: the long artefact is an article thread; the door this week is a feature; the 72-hour strip is a notice; “read this before you post in Support” is a sticky in that room. Do not rebuild that table. Use it.
What this article adds is the event version of a ship day.
- T-minus: a short staff post in the live room: date, what will change, where discussion will live. Not the notes themselves.
- Ship: the article (XenForo article forum, or a Discourse topic in Announcements). Feature it. Notice for 48–72 hours. Link the discussion thread under it.
- Plus one day: staff answer the three questions that actually appeared. Then stop performing.
- Plus one week: unfeature. Leave the article. Move leftover argument to the discussion thread. If the game has a season, the notes stay canon; they do not stay on the door.
Game and RP boards already have a place for this. The XenForo gaming architecture piece hung lore and play on a tree. The Discourse gaming fit test is honest that many of those boards stay on XenForo. Either way: patch notes are a document. Discord can hype the hour. The forum owns the URL you will paste in November.
4. Seasonal events — a prefix, not a building
A season is a date range with a theme: summer map, holiday build-off, expansion month, academic term. The failure mode is architecture. XenForo community practice: a deep tree of temporary rooms looks empty, costs a permission-cache rebuild when you add the node, and trains people to ignore the tree. Broad node + prefix is the recommended shape. Prefixes use ordinary indexes. They do not multiply nodes.
Do this. One prefix (S3, Holiday, Launch week) in the rooms that already move. One weekly ritual thread a stranger can answer. One recap at the end. Maybe one contest, not four.
Do not do this. Holiday 2026 as a category with five empty children. A Discord category that is the real event and a forum node that is a press release. A landing page that outlives the season and still says “happening now.”
When the season ends, the prefix stays as a filter. The weekly thread gets a recap and loses its sticky. You do not delete the year. You stop adding rooms. The post-hype article is the habit version of that sentence.
The logistics sheet (paste into staff)
If a row is blank, you are not ready.
| Field | Write this |
|---|---|
| Type | AMA / contest / patch notes / season / other (one) |
| Owner | One human who can cancel it |
| Host account | Personal profile for conversation; system Admin only for the official post |
| Start / stop | Dates, timezone, and what “stop” means (lock, unsticky, recap) |
| Where | Existing forum or category. Not a new node |
| How people find it | Prefix or tag + at most one notice + optional feature |
| Watch / notify | Which room is auto-watched; no site-wide blast |
| Staff budget | Hours you will spend hosting, not “we will be around” |
| Discord job | Live voice / hype / nothing. Forum owns the leftover |
| Leftover | Recap, gallery, canon article, or “delete the notice and walk away” |
| Success | One number you will look at after the leftover exists — not peak posts during the hour |
The number is not “replies during the AMA.” That number is always exciting. The number is: how many non-staff accounts posted in the leftover week, or how many new first-posts got a human reply. Steal the honesty from the metrics article: take your own baseline, do not invent a healthy AMA size.
XenForo: stock is threads, prefixes, notices, features
You do not need an events add-on to run the four types above. You need discipline.
Thread. Discussion for AMAs and most contests. Article for patch notes and recaps you want to read as a document. Poll only when the choice is real (next AMA day, which prize, which map). Question is the wrong type for an AMA; you are not marking a solution. Moving a special type into a forum that does not allow it is how you lose chrome — the engagement article already walked that caution.
Prefix. Three to seven per forum, named the way people filter: AMA, Contest, Patch, Season, Recap. Staff-only prefixes for states members should not set (Closed, Needs recap). Twenty coloured prefixes are decoration. The community-practice reason to prefer prefixes over nodes is not taste. It is empty rooms, crawl waste, and permission rebuilds.
Sticky. One or two per forum. The live event may be one of them. A 2019 “read this first” that you never update is already a landmine; an expired contest sticky is a second one. Review stickies the morning after the stop date.
Notice. Communication → Notices. Official types used across this site’s XenForo writing: Block (under the nav, until dismissed), Scrolling (junk ticker if you stack them), Floating (one-shot), Fixed (emergency bar). Criteria are the point: guests versus Registered, message count, this forum. One live Block per audience. An event notice that outlives the event teaches banner blindness.
Feature (2.3). Thread tools, featured/ list, featured widget. Order is featured date. 2.3 will not expire a feature for you. Put the AMA or the patch article on the door; take it off when the window closes. Do not feature a private staff planning thread.
Admin identity. Official announcements (the patch is live, the contest is closed, the rule changed) can come from the system-like Admin account. Hosting, jokes, “what should we ask,” and debate come from a personal profile without the nuclear badge. Community practice: members will not argue with the account that can ban them. If your only account is Admin, make a second one before the AMA, not during it.
Stock will not: schedule a calendar grid, RSVP, raffle, or turn a prefix into a group. If you need RSVP, a custom field or a poll is enough for most hobby boards. If you need a full calendar product, that is an add-on decision with a named owner — not a prerequisite for Thursday.
Discourse: a topic is the venue; Calendar is optional chrome
Latest already answers “what moved.” You do not need a portal to make an event visible. You need a topic people can watch.
Default path. Category that already has watchers. Tags for type and state (ama, contest, ship, s3). Pin for the window. A first post with the clock. Staff replies that host. Recap in-topic. Unpin.
Official Calendar plugin. Discourse’s plugin page: a dynamic calendar in the first post of a topic; participants can add events; a “Holiday Calendar” mode exists for staff time off. Hosted: listed on Business and Enterprise. The 2026 pricing grid also lists Events on Business. Prices and plugin packing change — re-check the live page. The Discourse documentation notebook we queried did not include a Calendar settings tour. This article will not invent one. If you are on hosted Free or Pro, you may not have it. You can still run every event type above with a topic and a date in the title.
Trust levels during an AMA. TL0 accounts are sandboxed: one embedded image, two links, two mentions, no flags, tight chat. An AMA that demands four screenshots from a brand-new account will bounce them. Tell guests in the first post. Do not turn the sandbox off for one evening. The trust-level model is the longer version.
Chat versus the topic. Official Chat is short-form, permissioned with the same trust ladder, available on hosted plans. It is a fine backstage for staff. It is a bad leftover. If the interesting answers happen in Chat, paste them into the topic before the window closes. Discord is the same rule with a different logo — see forum versus Discord.
Where Discord belongs (and where it does not)
XenForo community sources we queried do not discuss Discord at all. Treat the split as operations, not as a documented XF feature.
| Job | Forum | Discord |
|---|---|---|
| Canonical Q&A, patch notes, rules, recap | Yes | Link only |
| Live voice, raid night, “we are online now” | Announce the time | Yes |
| Searchable “what did they say about X” | Yes | Search is a different product |
| Hype on the day | Notice + feature | A channel you will mute tomorrow |
| Identity / roles | Groups, promotions | Guild roles — integration is a separate how-to |
The integration article is webhooks, connected accounts, and [8WR]. Do not start an event by installing that stack. Start by writing which medium owns the leftover. Two media that both claim “the conversation” will each look half empty after the guest leaves.
If the guest will only sit on Discord, you still owe the forum a recap the next morning. Staff who were in the voice channel write it. That is unpaid editing. Budget it. If you cannot budget it, do not call the voice session a forum event.
Leftover content is the actual product
The morning after is the job most teams skip.
Unstick, unfeature, kill the notice. Same day as the stop time. Expired chrome is how regulars stop reading staff.
Change the state, do not delete the year. Prefix Recap / Complete. Tag the same. Edit the first post so a searcher in six months hits the conclusion, not “starting in 20 minutes.” XenForo community practice on nodes: deleting a forum deletes its threads. Do not “clean up” a season by removing the node you should not have created. If you already created it, move the threads back into the broad room and leave the empty node until you have a backup and a plan — or convert it to a redirect/link if your stack can. Deleting is not archiving.
Make the leftover findable. One line in the forum description or a wiki/help page: “AMAs and recaps carry the Recap prefix.” Discourse: a tag page is enough. Do not add a new “Archive of events” category that only staff remember.
Close the loop in public. If you asked for questions, the guest answered. If you ran a poll, you shipped the result. If you promised a shortlist, you published it. Unanswered official threads train people to ignore the next event. The onboarding calendar already said that about feedback. It is louder when you put a date on the promise.
Do not keep the Discord channel “just in case.” Archive or hide it. A dead event channel is the chat version of an empty node.
Cadence: fewer events, more rituals
A board that runs an event every weekend is a marketing calendar, not a community. Staff will host until they do not. Then the room will feel cancelled.
A workable year for a hobby or mid-size board, as practice, not as a benchmark:
- One ritual a stranger can answer (weekly or fortnightly). This is not an event. It does not get a notice every time.
- Patch notes whenever you actually ship, using the newsroom split.
- Two or three AMAs a year you can staff, not twelve you will ghost.
- One seasonal prefix if your product has a season. Zero if it does not.
- Contests only when you have a leftover use for the entries.
If you cannot staff the ritual, cancel the AMA first. The ritual is how activity survives the hype. The AMA is a spike. New members still need a first-question that is not “were you at the event.” That is onboarding methods, not another campaign.
Stacking a contest on an AMA on a patch day will look busy and measure as one spike. The health metrics piece will tell you to mark those days on the sheet so you do not congratulate yourselves.
Worked month (hobby game board, XenForo or Discourse)
Week 1. Patch 1.8 ships. Article + discussion thread. Prefix Patch. Feature three days. Notice 48 hours. Staff answer the three real questions. No new node.
Week 2. Ritual only. “What are you running in 1.8?” in the main room. Personal staff account, not Admin. No notice.
Week 3. AMA with a developer who already posts here. Title includes the date and timezone. Prefix AMA. Calendar event if Discourse Calendar exists. Discord voice optional, recap mandatory. Host on a personal profile. Stop time in the first post. Next morning: recap paragraph, prefix Recap, unsticky, notice off.
Week 4. Do nothing that needs a banner. Measure: first posts, time-to-first-human-reply, whether the recap was linked from the welcome thread. If the only movement was week 3, you rented a night. Keep the ritual.
That month has one event, one edition, and one habit. It is enough.
A checklist you can paste into a staff forum
- Type, owner, start, stop, leftover — written before the thread exists.
- Venue is an existing room. No event category.
- Prefix or tag created (or reused). Not a new colour for one night.
- Host account is not the root Admin for conversation.
- One notice, one sticky, optional feature — all dated to die.
- Discord has one job, written down. Forum owns the URL.
- Staff hours reserved for hosting and the morning-after recap.
- First post includes the clock, the off-limits, and how a TL0 / new Registered person can participate (image caps, link holds).
- Stop date: unsticky, unfeature, notice off, state prefix flipped, recap edited into post one.
- Week-after look: non-staff posts, first-post replies, not peak-hour count.
FAQ
Do we need Discourse Calendar or a XenForo events add-on?
No. A date in the title and a prefix will run every type in this article. Calendar is hosted Business/Enterprise chrome (plus Holiday mode for staff). Buy it if you already run many dated sessions and local time is a real support cost. Do not delay Thursday for a plugin.
Should the AMA be a live Discord and a forum announcement?
Only if someone is paid (or reliably volunteered) to write the recap. Otherwise pick one medium. The forum wins when you care about search. Discord wins when the guest will only speak in voice. Hybrid without a recap is a disappearing event.
Can we put events in their own node so the main room stays clean?
That is how you get an empty room and a quiet main. Prefix the event in the room that already moves. Clean is a filter, not a building.
What if nobody shows up?
Leave the leftover honest: “We tried, here is what we asked, here is the next ritual.” Delete the notice. Do not delete the thread unless it is spam. A quiet AMA is information. A deleted AMA is how you repeat it.
Can staff enter the contest?
If they can win, no. If the contest is a gallery with no prize, say so. Judges do not enter. The Admin account never enters.
Takeaways
- An event is a date plus a leftover. If you cannot name the leftover, run a ritual instead.
- Four types: AMA (transcript), contest (gallery), patch notes (canon), season (prefix). Do not invent a fifth building.
- XenForo stock is enough: thread type, prefix, notice, feature, sticky, and a personal staff account. Community practice: no casual Admin, no temporary nodes.
- Discourse: a tagged topic is the venue. Official Calendar is optional Business-tier chrome. Chat is backstage.
- Discord may own the hour. The forum owns the URL. Integration how-tos are a different article.
- The morning after is the job: recap, unsticky, kill the notice, keep the year.
Run fewer events. Write them down. Leave something a stranger can read in six months.