Yeah, I skipped over build 37. Don't think much of it.
For build 38, I put on a white lab coat and rubber gloves. I tried to be as paranoid as I could be along the way. Each step of the build, I double-checked so as not to introduce errors. The result is a setup executable which probably is exactly what will be distributed to the world. If testing on this build goes okay, I will simply rename the .EXE and start spreading it around. The idea is to avoid rebuilding because there is a small chance I'll screw something up along the way.
Purposefully, I didn't make an upgrade installer because it won't be distributed (it's just a tool provided for convenience to beta participants), and the testing emphasis should go on the full installer which will be distributed.
I would like it if people could run through this smoke test:
1. Install DROD and run it.
2. Import 1.5 data if you got it.
3. Play through the first level.
4. Switch between fullscreen and windowed modes.
5. Create a new hold and edit some rooms.
6. Export the hold.
7. Import the hold.
It'll probably take you 10 minutes. I'm trying to hit the basic functionality of DROD across the different configurations we have out there. I'm looking for some strange and stupid error that was introduced by the build itself, since the changes to the code have been minimal.
If you run this test successfully, please reply back to this post and say something like "
I ran the smoke test successfully on Windows 98"
. I'm interested to know that we have all the O/Ss covered. We will try to run the release candidate on Windows 95/98/XP/ME/NT/2000. This might sound dumb, because we have been testing the same stuff for months, but we have to check once more for the release candidate to avoid some really embarrassing last-minute mistakes. After getting DROD uploaded to twenty or thirty game sites, it would be horrible to learn that say... we shipped with the wrong version of a DLL.
Here's what was fixed/changed in build 38. Some testing around these changed areas would also be appreciated:
83928 Changes addressing editing rights.
80687 Update credits just before release.
83785 BUG: CWidget:: DrawFilledRect() occasionally buggy
83784 Add tool tips to title screen
83762 Hold/level settings.
83672 Fix tar and roach egg spawning
83687 Add home/end commands to multi-line text box.
83679 Fix broken demos
83625 File select dialog goes blank after choosing A: fails.
Finally, I don't want to be close-minded about fixing any new bugs you may find. The bar for fixing them is very high right now. If you see something annoying, but basically workable, we will probably not fix it in DROD:AE. If you see a bug which prevents you from doing something or loses your data, we probably will fix it. If in doubt, please report the bug, and don't take it hard if we choose to skip over it for this release.
-Erik
____________________________
The Godkiller - Chapter 1 available now on Steam. It's a DROD-like puzzle adventure game.
Decent Apps - open source tools for writing and deploying privacy-focused LLM-based web apps.
Is this because of the rule changes? I had "record victory demos" on and had played through level 20 of DROD with this player throughout the various beta builds.
