We're dangerously close to it now. The only remaining item on my list is the broken fog, and I think I'm going to leave that be for now as it seems more hardware dependent than anything else.
A few points regarding some of the other items:
- Web download has now been transitioned to Windows API code and should run a lot cleaner, with no "Internet Explorer components" (that aren't really) in use.
- PQ messaging is there but right now the client only responds to ping times. It's not beyond the bounds of possibility that I might delay to extend this a bit more, but it depends on how messy the original code is.
- DP_TE_PARTICLERAIN and DP_TE_PARTICLESNOW have been implemented as a test bed/proof of concept of DP extensions.
- FRIK_FILE has not been implemented; there are huge dependencies on other parts of the code that I've changed beyond recognition (Zone memory, PR temp strings and file handles) so it needs quite intensive rewriting and testing before I can say "yeah, this works". I'll probably need to cook up a mod of my own just as a test bed.
- Previous dependencies preventing it from running on Windows 2000 have been straightened out.
- An old bug preventing you from being able to kill Shub has been fixed.
- Several bugs relating to invalid model and skin indexes in mods like Prydon have been fixed.
- A "levelstats" command to dump info on the current level to the console has been implemented. I had intended to include a dump to file option but didn't in the end. Set condebug 1 to do this yourself.
- Speaking of which, condebug 1 mode has been greatly enhanced as a means of providing multiplayer game info; it no longer temporarily locks your game while writing large amounts of text to the console. condebug 2 will revert to the old behaviour.
One final point regarding the public domain thing I wrote about a while back. Having thought about it a bit more, I'm now inclining towards not doing it. It's not that I think the GPL is any kind of ultimate paragon of licensing excellence (I don't) but more a case that there are logistical implications I need to think through further.
The next post should either be an announcement of release or a notification that I'm delaying for whatever reason, so sit tight!