Forums
Heatmap Bot Update v1.3.0
Shipped v1.3.0 today with a significant pricing restructure
Old: Free (7 days) Paid $4.99/mo
New: Free (5 days) Basic $2.99/mo Pro $7.99/mo
The old $4.99 single tier wasn't working. Too cheap to feel serious. Too expensive for impulse buy. Now there's a $2.99 entry point that's easy to say yes to.
Add free https://top.gg/bot/1482225606761...
Heatmap Bot Update v1.2.0
Just shipped v1.2.0!
Biggest change: Ko-fi payments now auto-activate.
Previously I had to manually grant paid tier after every payment, not scalable. Now when someone pays on Ko-fi and includes their Discord Server ID in the message, the bot detects it automatically and activates their subscription instantly.
Also added /announce so I can broadcast updates directly to servers that opt in, much better than hoping people check the changelog.
Heatmap Bot Update
Things I learned shipping a Discord bot this week:
1. Railway's restart policy can cause rapid reconnects Discord IP ban.
Set restartPolicyMaxRetries to 3, not 5. The fewer restarts, the less likely you get rate limited.
2. SQLite is fine for a Discord bot.
WAL mode + aiosqlite = zero issues so far. You don't need Postgres until you're at hundreds of servers with heavy concurrent writes.
3. discord.py slash commands take up to 1 hour to propagate globally.
For instant updates during development, sync to a specific guild instead. But remove guild sync before production or you get duplicates.
4. matplotlib heatmaps are slower than expected (~300ms per render).
Why I built Heatmap Bot
Hello Product Hunt!
I built Heatmap Bot because I kept posting in my Discord server at the wrong time and getting zero engagement.
Turns out most servers have a very clear activity pattern, weekday evenings are usually peak time. But Discord doesn't show you this anywhere.
With one command: /heatmap, you get a full 7 24 activity heatmap directly in chat. There's much more command.
Why I built Heatmap Bot
Hello Product Hunt!
I built Heatmap Bot because I kept posting in my Discord server at the wrong time and getting zero engagement.
Turns out most servers have a very clear activity pattern, weekday evenings are usually peak time. But Discord doesn't show you this anywhere.
With one command: /heatmap, you get a full 7 24 activity heatmap directly in chat. There's much more command.

