Hi!

I installed nQuake a couple of days ago so I could fool around with som bots before I hit up some real servers, everything worked great, at first...
Yesterday I tried playing some regular single player, and the next time I started up quake and typed "bot_1on1" automatically loaded aerowalk, and
tried typing "addbot" in the console, as I usually do, the cmd didn't even exist anymore?

I know this has got to have something to do with me playing singleplayer the night before this, but I have know idea of how to fix it...
Ofc I could always reinstall, but I was hoping there is some easier solution than that.

Also I've tried googling this, aswell as search for similair threads here on the forum, but to no awail...

This is bugged indeed, type this into the console before you start the bot game:

Super thanks! Back to enjoying the fun times of not getting raped untill I play some real opponents :-)

This needs fixing asap, if not by the client, then by changes to the bot_* aliases in nQuake

It's already fixed in the client (starting multiplayer game via the menu was bugged the same way), nQuake configs need fix too, bugreport has been sent to nQuake site.

Ok good

I wish I had time to fix this.

This should be fixed now.

I downloaded and installed nQuake last night and found this exact same problem. It's the reason I registered and came to this forum, to find a solution (thanks).

I installed nQuake, played bots happily, tried single player out, then when I tried to play bots again it wouldn't recognise the "addbot" command. So it appears it may not be fixed...

But thank you for nQuake, regardless. It kicks ass.

Does the suggested command "sv_progsname qwprogs" help?

Yes, it does, and I've already thanked them for the solution. I was just explaining that the exact same problem is still happening after an nQuake developer said "should be fixed".

It should however work if you close it and start it again? Unless you've used cfg_save within singleplayer?

I tried closing and re-opening, and I also tried rebooting my machine. It is possible that I might have done a cfg_save without thinking whilst in a single player game.

I now know the solution though so it's all gravy

Ah, ok. Thanks for warning. It's possible that the bug is still present in nQuake. I remember also some another user reporting the same thing after the fix was announced.