Community & Sentiment
Owned-channel social listening — Facebook Pages + Discord. Sentiment, topics & recommendations from a read of the full message/comment corpus. · data 2026-06-24
FB fans
7,262
53 posts · 186 comments
Discord members
1,564
#general
Discord messages
2,393
468 unique authors
Mentions analyzed
446
8 topics · 2 channels
Avg sentiment
-0.10
Neutral / Mixed
Sentiment overview · 446 mentions analyzed
-0.10Neutral / Mixed
NegativePositive
Positive 140 (31%)
Neutral 45 (10%)
Negative 183 (41%)
Mixed 78 (17%)
Most mentionedMonetisation and pricingPositive hypeGuild recruitmentLocalisation qualityNew class balanceCompetitor comparison
Weekly sentiment split (% of mentions)
Community volume — daily Discord msgs & authors
Net sentiment trend (positive − negative, by week)
Content volume split — by channel
Top discussion topics — mentions, colored by sentiment
Weekly read
positives · negatives · recommendationJun 1–8
msgs: 501pos: 33%neg: 32%eng: 27%
Volume steady; the pricing thread is still the loudest single topic.
▲ Guild recruitment and the new class both read positive.
▼ Pack pricing keeps getting compared to a rival title.
→ Recommend: Answer the pricing thread directly before the next event.
Jun 8–15
msgs: 572pos: 40%neg: 25%eng: 29%
Volume steady; the pricing thread is still the loudest single topic.
▲ Guild recruitment and the new class both read positive.
▼ Pack pricing keeps getting compared to a rival title.
→ Recommend: Answer the pricing thread directly before the next event.
Jun 15–22
msgs: 683pos: 40%neg: 27%eng: 22%
Volume steady; the pricing thread is still the loudest single topic.
▲ Guild recruitment and the new class both read positive.
▼ Pack pricing keeps getting compared to a rival title.
→ Recommend: Answer the pricing thread directly before the next event.
Social listening — topics
Trending → recommended action
Monetisation and pricing
Rival title ran a cheaper starter pack
→ Publish the value comparison the team already has
Server stability
Queue times at peak
→ Post the capacity fix date rather than staying quiet
New class balance
Split opinion after the patch
→ Share the win-rate data; the numbers are better than the mood
Issue tracker
Monitoring
Login queue at peak hours
Discord · Ops · Raised with backend; watching the 20:00-22:00 window.
Escalated
Pack pricing called out against a rival title
Facebook · Product · Pricing review scheduled; comparison table drafted for the team.
What worked / didn't (Jun 15–22)
Worked: Answering the balance thread with actual win-rate data moved it from negative to mixed within two days.
Didn't: Staying silent on pricing. The thread did not die, it grew and picked up the competitor comparison on the way.