*** CUT ***

This change was discussed on various occasions on the client-channel many, many
times. Of course, that is easy to miss.

The change to triggers is the second thing mentioned in Batclient's Changelog,
available from inside the client, as well as on the Batclient forum (in the URL
http://www.bat.org/forum/index.php?showtopic=258 ). A pointer to this
information was also posted in the game-wide inform at the point of release.
Besides this, also the internal inform newsgroup was used.

This change was *requested* by the players, and agreed among arches that the
whole thing should be done properly and recoded from scratch: trigger parsing
is to be done straight from the stream instead of separately in each window
(feature track item #166; sorry no, you don't get see this list as of now).

Sadly, this item requires changes to some of the scripts. Not all of them. This
kind of changes aren't done "every day".

Now, what we didn't know is that with v1.80 we actually introduced not one but
several "new" bugs, even though we had many iterations in internal testing--
one of the bugs being trigger-related.. Why, yes, we were overconfident in the
release. For certain undisclosed reasons, we also wanted everyone to receive
the new update as they load up BatMUD (see about v1.71 later).

The trigger bug: we spent several hours today fixing this issue, as soon as it
was identified (through feedback from the players). Naturally, we ended up
fixing more than just that. Btw, yesterday which was the day after v1.80
release, we spent correcting such as the bold/lite -issues players were
experiencing.

As you noted to me during the time I was writing this message, you've noticed
that your triggers actually work again. Yes, see--..

But while we're at it...the deprecated v1.71 was actually made available for
download already before the v1.80 was out, had you happened to look a bit
deeper on BatMUD's website. No pun intended!

Otherwise, thanks for the comments. I know there's a lot to be made "better" in
our processes, for such as preparing fully staged releases (which they actually
already are due to replication issues), however we're really thin on resources
for the Project--so we've taken this "indie" approach for now.

But without input on what's working and what's not, we'd be half the way where
we are right now, my thanks for helping us out. Though, my advice is that the
in-game client -channel is a much better way to get your dose of info on where
we're at right now, rather than the flame-newsgroup. But the choice of weapons
is yours, my friend.


Amarth Shadowstring