We weren’t really planning on doing this, but an exploit has been discovered and, unfortunately, been used to crash peoples’ servers and we need to plug the hole.* So we’re releasing version 2.1.18.* Currently it is just* a patch download on the downloads page. * We’re still hard at work on 2.2, and we’re hoping to have stuff for you soon on that front.

Patch notes:

* Netgame fixes:
* Fixed an exploit where malformed packets with invalid node identifiers caused the server to crash.
* Made the server recognise verified admin players’ bans, as opposed to only treating them as unenforced kicks.
* Fixed the fact that the allowteamchange console variable was completely broken, having previously caused both desynchronisations and crashes when switched off.

* Software rendering fixes:
* The game no longer crashes whlst attempting to render certain types of FOF off the top or bottom of the screen.
* Precipitation being off the top or bottom of the screen no longer causes visual artifacting (or, in rare cases, crashes).
* Fixed various issues with the v.DrawFill function. This includes its shoddy handling of V_SNAPTO flags, amongst other quality of life improvements.

* Minor, unrelated fixes:
* Fixed an issue where falling rock hazards could linger in perpetuity after colliding with slopes.
* Fixed a crash caused by Jet Jaw badniks attempting to attack players who had had the “MF_SHOOTABLE” object flag removed through add-ons.
* Fixed a crash caused by attempting to execute the “Call Lua Function” linedef executor with blank fields.
* Fixed an issue where attempting to have more than 10,000 screenshots in your screenshots directory was erroneously allowed.

Let me apologise! Since 2.1.15 onwards, I've been handling the preparation of installers for the devteam because I'm basically always around. The last exam of my exam season had just happened when .18 started to become a thing, so I was too busy to make this version's installer for the main release. Now that I'm free of such shackles, it's been created and placed on our non-public file storage, and will be added to the website once the people with the appropriate credidentials get home from work or whatever it is they spend their days doing.

But yeah, Rob is right. There is no reason someone who already has a version of SRB2 from 2.1.15 onwards installed on their machine would download the installer for .18 instead of the patch unless they just wanted to do it for the hell of it.

Yay! SRB2 2.2 comes a little more closer to completion!
Speaking of which, what is the estimated/approximate/hoped release date for 2.2?

When it's done.™

__________________
Science tells us that nothing can be proven, only rendered more likely to be true. If we do not question what we already know, how can we know, much less admit, when we're wrong? Such things are vital to progress.

Protip: Never expect ANY new version, mod, or addon in the making to be done when you, your friends, or even the developers themselves set some form of a deadline, life is shit, and by default, tend to get in the way of people's lives and prevent them from getting some time to work on projects, especially for this open source free to play kind of mod. It's an objective, but not a required one, especially since no one is, will, or should get paid for doing it.

In the meantime, make a mod yourself, maybe we will know when your mod is done, right? :P

Parkinson's Law. Nobody could reasonably expect a team like this to stick to a predefined schedule, but as a general productivity measure, I hope the devs are at least personally setting goals and dates for themselves. You'll lose perspective of time and a sense of direction otherwise.