Skip to content

Instantly share code, notes, and snippets.

View DrewKestell's full-sized avatar
🌦️

Drew Kestell DrewKestell

🌦️
  • Microsoft
  • Redmond, WA
View GitHub Profile

FAQ

1. Is there a compiled version of BloogBot available for download?

No. You'll have to clone the repo and compile it yourself. Follow the instructions in the git repo README.

2. Does BloogBot work on retail/classic WoW?

No. Currently BloogBot is only tested on Vanilla/TBC/WotLK legacy clients. See the git repo README for more details.

3. Why does BloogBot depend on a database?

The bot uses the concept of "hotspots", which are a collection of positions in the game world, that the bot bounces between to grind mobs. You have to create a hotspot using the bot's UI, then select a hotspot, before starting the bot. Hotspots are stored in a database. The reason I decided to do this was so my friends and I could all share the same grinding hotspots by connecting to a cloud database. In theory, the bot could also work with a local database, or even a local .json or .xml file, but this would require some changes to Repository.cs and likely some other spots.

# FAQ
## 1. Is there a compiled version of BloogBot available for download?
No. You'll have to clone the repo and compile it yourself. Follow the instructions in the git repo README.
## 2. Does BloogBot work on retail/classic WoW?
No. Currently BloogBot is only tested on Vanilla/TBC/WotLK legacy clients. See the git repo README for more details.
## 3. Why does BloogBot depend on a database?
The bot uses the concept of "hotspots", which are a collection of positions in the game world, that the bot bounces between to grind mobs. You have to create a hotspot using the bot's UI, then select a hotspot, before starting the bot. Hotspots are stored in a database. The reason I decided to do this was so my friends and I could all share the same grinding hotspots by connecting to a cloud database. In theory, the bot could also work with a local database, or even a local .json or .xml file, but this would require some changes to Repository.cs and likely some other spots.