Frequently Asked Questions

❓ Why is the bot sometimes late to post the new stock?

Grow a Garden 2 is a brand new game, so the data sources we use to fetch the shop stock are still a work in progress! Sometimes the data lags a minute or two behind the actual game. Don't worry—as the game gets older, the bot will become faster and more reliable.

❓ Why did the bot completely skip a rotation?

Sometimes the tracker completely breaks and sends us blank or frozen data. To protect you from getting spammed with broken pings, the bot will silently skip that rotation until the tracker starts working again. We'd rather miss one update than send incorrect information!

❓ How do I get pinged for specific items?

Head over to your server's reaction roles channel (the name may vary depending on the server) to choose which item notifications you want. If you'd rather receive a private DM instead of a server ping, simply run /setup, and the bot will DM you as soon as your selected items appear in stock.

❓ Is the bot trustworthy?

Yes! The developer behind this bot also created a stock bot for the original Grow a Garden, which grew to over 1,000 servers. We don't collect unnecessary data, and the bot only requests the permissions it needs to function properly.

❓ Why does the bot need Administrator permissions?

The bot uses Administrator so it can reliably perform its features without permission issues. This includes:

Creating and managing notification roles.
Sending automatic stock updates to your configured channels.
Managing activity and notification systems.

The bot does not read your private messages, access sensitive server data, or perform any actions outside of its intended features. Administrator is simply the easiest way to ensure every feature works correctly across different server setups.

❓ I have another question or found a bug.

Feel free to DM us on Discord if you have any questions about the bot or if you've found a bug.

Please do not DM us about:

⏱️ Stock updates being 1–2 minutes late. This is expected sometimes while our tracker catches up.
🔒 Permission issues. If the bot can't perform an action because it doesn't have the required permissions or role hierarchy, that's a server configuration issue, not a bot bug.