Skip to content

Frequently Asked Questions

Mino edited this page Apr 30, 2015 · 3 revisions

Why does Minjection fail to inject?

Every single case someone has had an issue with injection, it's been because they are missing one or more DLLs. This could be the MinHook DLL, the Boost DLL, the Python DLL or the Visual C++ DLLs.

  1. Download the x86 version of Dependency Walker.
  2. Put minqlbot.dll in the same folder as quakelive.exe.
  3. Run Dependency Walker and load minqlbot.dll with it. It will tell you what's missing.
  4. If you're not sure how to interpret it, expand the module list in the middle, screenshot it, upload it somewhere (like imgur), and link it to me so I can have a look at it. You can do so either by opening an issue here on Github, send me an e-mail, or drop by #minqlbot on Quakenet.

Why is chat/callvote/X delayed when I run the bot?

Quake has two channels that everything that happens goes through. One is text-based that handles team changes, scores, chat etc., the other handles game info like players' movement, shooting etc. The text-based channel restricts how much you can input. The server does not allow a command through this channel for approximately half a second after receiving one. Due to the high output the bot can produce, the bot will control the text-based channel by means of a queue system, otherwise a lot of the bot's function would be lost. This means your commands for things like /say, /callvote etc. might be slightly delayed when running the bot.

How can I kick players below/above X amount of Elo?

You can set rating thresholds in the config. MinimumRating sets a minimum requirement, MaximumRating sets a maximum. Note that AllowSpectators is set to True by default, which will allow players to spectate, but not play. Set this to False if you want them to be kicked automatically.

Not to be confused with FloorRating and CeilingRating, which will only set the rating of a player below or above those settings to whatever you've set them to.

Why does my bot have permission level 0?

This happens when the Nickname field in the config is set incorrectly. You're supposed to set that to exactly the same name as the name of the account your bot is running. If my bot's name is MinoBot, the line would look like this:

Nickname: MinoBot