Map4 Bug
Apparently Seriema's bug was indeed valid, I mispelled a variable name in one of the script functions on map4.
This is of course the only reason (IMO) why implcit variables suck, since if explicit declarations were neccisary it would have told me that $lphalpien was not declared, wherein $lphaliphen was =)
This bug was caused by my lazyness =D,
Before release I noticed a few issues I wanted to clean up and set about to do it. However I did not test all of these changes, and this one bit me in the butt =D
Naturally, this is an iron clad rule of development, and I am normaly good at following it, however I guess I was a little tired that day =D
Needless to say, this bug has been fixed, and the fix distributed to the testers =)
The Quit Bug
After some more testing, Seriema and I determined that the quit bug is being caused by somthing in the configuration dialog.
This dialog is made by CreateDialogIndirectParam, using an in-memory made template (evil). I am very unexperienced with dialogs and such, so I do not doubt this to be a valid reason.
It sounds like perhaps somthing is being left resident from the dialog and causing the process not to terminate. But I am unsure exactly what that could be at the moment =D
The Longest Test
Last night MW witnessed the longest test from ShoeStringGames,
They played for about three hours, and with some guidance from me (would have taken longer otherwise, due to proper exploration and all), they managed to find several (four i think) artifacts, and level about 6 times, as well as aquiring new runes (from purification) to make better spells, and getting better items to increase stats =D
All in all it was great, the gameplay seems to be going as we planned, and so far nothing has been too problematic. Durring this 3 hour test, not one showstopper bug killed the party =D
And most other comments were for added features, such as Mana Trickle Charge while near the well, which we are going to do =D
