Started by miquelfire, December 23, 2016, 10:38:04 PM

Previous topic - Next topic


So, I got done playing a game recently, and noticed that my copy of CW2 has an update queued on Steam. I can't seem to find any info about it.


There was a strange bit of code (change made way back in 2013) that never got into the main line of CW2 until the new, Anniversary edition of CW2 (the 500- and 800- version builds). The change broke some maps, and we're still waiting for archaeologists to return with the scrolls that describe the original reason for the change. ...

Stay "tooned"...


Yes, there is a new 0801 update for CW2.  It's an interesting tale...
In 2012 after the release of version 0497 I apparently fixed a "bug" in the creeper logic related to fields.  That fix was never pushed out in an update.  So the seasons came and went.  At the beginning of 2016 I repackaged CW2 to have a captive runtime.  That was based on the last source tree, so it had this "fix".  This version of CW2 was downloaded by a few folks who had trouble with the old AIR version.

Later in 2016 I released the CW2 anniversary edition.  This was of course based on the latest source, and had this "fix".  Problem is, some maps (maybe 1, maybe 10... I'm not sure I only know of 1) relied on the old behavior, not the fixed behavior. Map "#2766: The Treasure Chamber" is the map that broke.  The reason it broke is because it actually has a tiny flaw in the way the fields are arranged.  They allow creeper to leak out.  But, this only happens with the "fixed" creeper/field logic.  So the author never knew since it worked just fine in the game he had (and nearly everybody else had).

So, since the game spent 99.9% of its life with the flaw, I have restored the flaw.  That ensures that the creeper logic is as it was in version 0497 and all of the existing maps will work as intended.  It isn't a really large problem, since the game's entire history has been with the flaw :)  So, the prudent course was to restore that behavior and stop calling it a flaw.


Quote from: virgilw on December 24, 2016, 10:57:43 AM
So, the prudent course was to restore that behavior and stop calling it a flaw.
You know the old saying: "It's not a bug, it's a feature". Fascinating story. I hadn't heard of this.