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
5,402
Tidebreak Arena
FB posts
39
pulled
FB comments
536
content (identity withheld)
Mentions analyzed
362
6 topics · facebook
Avg sentiment
-0.10
Neutral / Mixed
Sentiment overview · 362 mentions analyzed
-0.10Neutral / Mixed
NegativePositive
Positive 71 (20%)
Neutral 75 (21%)
Negative 109 (30%)
Mixed 107 (30%)
Most mentionedEvent rewardsLocalisation qualityCompetitor comparisonPositive hypeMonetisation and pricingNew class balance
Weekly sentiment split (% of mentions)
Community volume — daily FB engagement & posts
Net sentiment trend (positive − negative, by week)
Top discussion topics — mentions, colored by sentiment
Weekly read
positives · negatives · recommendationJun 1–8
msgs: 699pos: 29%neg: 24%eng: 23%
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: 386pos: 45%neg: 31%eng: 20%
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: 807pos: 29%neg: 19%eng: 23%
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.
Fixed
Mistranslated skill description
Facebook · Localisation · Corrected in the next client patch.
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.