zadao.aiNova Quasar: Flares
In short
Flares post automatically in your channel when something real happens: a member or XP milestone, a new leaderboard leader, an anniversary, or on PRO a holder milestone or SIP result. Never about price.
Flares are posts that fire on their own when something real happens in your community: you turn a rule on once ("post when we pass each 500 members") and from then on Nova writes the post and publishes it in your own Discord channel or Telegram group. Flares are the first feature of Nova Quasar, Nova's community marketing and reach features.
What a flare looks like
2,000 members
🎉 ZADAO just passed 2,000 members. Thank you to everyone who showed up and stuck around.
That is two thousand people who decided this was worth their time.
The title and first paragraph come from a template, so a flare never needs AI to post. The last line is the optional AI-written line: one short sentence about the event, added while your weekly allowance lasts. On Discord a flare is a card in your accent color; on Telegram it is a formatted message. If your community runs its own bot (Nova Soul), flares post as that bot.
A flare has no calendar and no per-post approval. Every one is tied to an event, and each event posts once.
What you can announce
| Trigger | Fires when | You set |
|---|---|---|
| Member milestone | The server or group passes every N members | N (for example 500) |
| Community XP milestone | The XP earned by the whole community passes every N | N |
| Member level milestone | A member reaches level 10, 20, 30... | Every how many levels |
| New leaderboard leader | Someone new takes first place on the all-time XP leaderboard | Nothing |
| Community anniversary | Once a year on the community's birthday | The date (optional on Discord, where the server's creation date is used) |
| Token holder milestone (PRO) | Your token passes every N holders (Stacks, Solana, EVM) | Chain, token address, N |
| Stacks governance result (PRO) | A SIP changes status, or an advisory-board vote on one closes | Optionally one SIP |
The XP, level and leaderboard triggers need Ascend turned on. A new rule starts from the current numbers: one created at 1,530 members with "every 500" first posts at 2,000, not for the 1,500 it missed.
Free vs Community PRO
| Free | Community PRO | |
|---|---|---|
| Active rules | 3 | 20 |
| Template flares | Unlimited | Unlimited |
| AI-written lines | 10 / week | 150 / week |
| Voice of the AI line | Nova's | Your Nova Soul persona |
| Community triggers (members, XP, levels, leaderboard, anniversary) | ✓ | ✓ |
| Token holder and governance triggers | — | ✓ |
| Your own template per rule | ✓ | ✓ |
When the weekly AI allowance or your plan's AI budget is spent, flares keep posting with the template alone.
Keeping it quiet. A community posts at most 4 flares a day by default (you can set 1 to 12), on both tiers. A flare over the limit is skipped, not queued, so yesterday's news never shows up late. Each rule can also have a cooldown between two posts.
Set it up
- As an admin, in the channel (Discord) or topic (Telegram forum) where flares should appear, tell Nova what to announce:
"@Nova post here when we pass each 500 members"
- Add more rules the same way, or point one at another channel (Discord only):
"@Nova announce in #wins when someone reaches level 20"
- Check it: "@Nova test the flare" posts a labelled sample with example numbers.
- See what you have with
/flares, or ask "@Nova what flares do we have?" To change one: "@Nova pause flare #3", "@Nova make the member flare every 1,000". - Optional: write your own text for a rule ("@Nova use this text for the member flare: We are {milestone} strong, {community}!"), turn the AI line off, set a card color, or add a footer note such as a risk warning.
The same settings are on the Nova Quasar card of the Community Settings dashboard.