You think it was the exitgame tag that was causing crashes, or were you just mentioning that as an aside to DB .220 being buggy?True. Until today I had been using the previous version that used the exitgame tag, so I just assumed it worked in a similar fashion until it didn't and then looked at the source code. Sometimes neat features like that are more of a headache though. I added exitgame back in. It doesn't look like there will be any DB updates till next week, so I'm expecting the usual crashes every hour or so.
Btw, I really like the support for the A and B profiles. Another option you might want to consider is having the master profile contain all the profile names and then have the profile manager run them in a random order.
If it's the former and not the latter, would it be better to just hardcode in an exitgame for whichever profile you're wanting the game to reset on? Or maybe implement a rudimentary counter and then force a restart (i.e. whenever it completes 6 profiles, restart at START_HERE no matter what).