I don't want to spoil the air with bad news but, I've tried reinstalling/repatching and its just no good. ET starts fine, but whenever I attempt to host a session of any kind to try the bot out, I get some kind of serious error popup and the game closes during the mapload. I don't know if this will help or has any useful information but I grabbed the windows generated report and have it here.
A pretty shocking disappointment to be sure but, this things a clean install now with nothing else to interfere. I can't imagine what could cause this.
Naturally. If you think back to my first main site message - I was complaining that nearly all other bots are broken in some way due to patch 2.60, just to be sure I reran the patch just now and the results are the same. Plus its noted in the readme - which I did
This is the exact error message I got. Its a real mental lapse to have failed to mention this the first time around but I was still scrambling with little things hoping it was just a misconfiguration or something on my end.
At this rate, short of a second reinstall, I can't figure on any course of action.
EDIT: To answer your second set of questions - WindowsXp and an old Athlon 1.2ghz. It's never given me trouble with ET before.
EDIT#2: Oh and sorry I missed that but I've started the mod both of the conventional ways - first by making a shortcut with the added +set fs_game fritzbot and also by way of the in game mod menu. From the shortcut I recieve the error and stopped code, from in game it just appears to stall completely during the load, though according to windows its still running.
Success! one thing that immediately caught my eye here is that the filesize for the qagame_mp_x86.dll is 922k, while the one in the zip you just attached to the thread is about 886k. Something that sticks out obviously.
In either case overwriting that file was apparently the magic button I needed pressed. The bots were busy wailing on each other in warmup as always haha. Thank alot chief, you rock. Sorry for my scrambled reports there though.
Alright - I had my suspicions, but your report proved it.
I compiled the .dll to take advantage of some newer CPU features, but it was supposed to be backwards compatiable (according to MicroCrap). Obviously it wasn't.
I'll fix the DL and release a patch for those who got it. Thanks for your help in finding this!