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
9,758
Lanternwood
FB posts
30
pulled
FB comments
896
content (identity withheld)
Mentions analyzed
388
6 topics · facebook
Avg sentiment
-0.14
Neutral / Mixed
Sentiment overview · 388 mentions analyzed
-0.14Neutral / Mixed
NegativePositive
Positive 80 (21%)
Neutral 78 (20%)
Negative 135 (35%)
Mixed 95 (24%)
Most mentionedPositive hypeLocalisation qualityCompetitor comparisonNew class balanceMonetisation and pricingEvent rewards
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: 839pos: 31%neg: 33%eng: 28%
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: 408pos: 31%neg: 32%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: 702pos: 40%neg: 24%eng: 17%
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.