do you have the .net framework installed? is the actual spawner not working or is it not starting winbolo ds? i can't seem to reproduce the problem.
The actual app won't even start. I don't know if I have the .net framework or not, ugh. I do know that all windows updates download and install properly, but is that related to .net?
'The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.'
most likely a .net framework error http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=en should help out a tad
Ok, got it working. I'll watch for bugs and other issues as it runs. I noticed that the path for DS is quite long [2 lines] on my computer, so only half of it fits in the DS area of this new version. Also, I don't remember if I mentioned this before or not, but it appears that people aren't able to kill games from IRC that are being run from the spawner. I suspect the reason for this is that some of the scripting sheeps did for wbb is set up for Wonkaspawn, not for the Game Spawner. How this might relate to the kill issue I have no idea. The bot displays the kill message as usual, but the game isn't killed.
Anyway, glad to have it going.
AND NO CRAZY COLORS OR ART?!?!?!?!?!?!?!?!?!?! :D :) :D
Update: On first load, it failed to generate a second game after the first one was won. [Note that the first game seemed to run fine.] On the second load, it also would not load a second game after the first. The original game still shows up in the app, but no game is in wbn or the tracker.
Also, I'm encountering a problem with the 'winbolo.exe dormant process' error. In two games I've been playing in tonight, winbolo is hanging midgame and won't rejoin/re-run [I get the 1.14 white screen, which is the crazy dormant process thing, but there are no winbolo.exe processes to kill.] It's like something is acting as a 'ghost' process or something. I can reasonably assume the new software is to blame because the hanging of winbolo and the subsequent inability to restart winbolo started soon following running the new spawner. Unless - I wonder if this has something to do with the .net software which I recently installed, but it does kinda seem less likely.
Hope that's readable and helpful.
the bots won't work, because it doesn't work with wonka's spawner etc which is what i assume wbb uses to deal with games. I will make the slot for the winbolods path long since some of you :| have winbolods nested deep inside the evil ntfs filesystem.
and the not starting another one.......maybe i shoulda tested the quitonwin thing to see if it restarted lol I will see whats up tonight
Mmmm...FAT32...
This whole beta test thing could be alot of work for ya, ugh.
Oh, and I ran the older version and joined/played several games and didn't experience the lockup of 1.14 like before.
well my guess is the process exited weird and made my spawner hang, which made everything act weird
