Counters and weapon shooters (DMute hex)

[beowuuf]

Two cases of duh for when I was checking the hex ages ago....this should fill in some gaps

a) counters:

These work as follows - the 3rd/4th byte determines number of activation needed
(eg 6 1 needs two activations, 86 1 needs three activations, 6 2 needs four, etc)
and you need a close effect to activate them.

However, they work like this - each close effect decreases the hex by one level, so 6 2 goes to 86 1, 86 1 goes to 6 1, etc
So, by stunning simplicity, any open effect targetted at it increases the hex levelby one! 86 1 goes to 6 2, etc
Only when the hex level is decreased to a ground state of 6 0 does the object activate.

The only small niggle is that you can't get back from this ground state (well, I haven't found a way yet!) so once an object is activated it's activated.

CSB had (as I've posted before) a nice trick, where a constant weight effect was associated with the counter, so each time the hex was changed, it would generate a null effect (eg on an open constant weight, it will re-inforce the close effect each time until activation) so giving a limit on the 'shop' bedise the DDD, and limiting monster swarm generators

b) I have been looking into the 3rd byte '7' of wall object for a while trying to work out what it could be for, and also at the same time always thinking it was strange that weapon shooters double fire, while spells and objects can have single and double versions.
Duh
7/87 creates a single shot version of the weapon shooter, with the same hex (eg 7 3 gives a torch shooter)





<i>Edited by: <A HREF=http://pub17.ezboard.com/ubeowuuf.showP ... beowuuf</A> at: 8/3/02 9:24:08 am
</i>

[Zyx]

Hey, it's cool to see somebody is still investigating the mechanisms of DM! Keep your inner fire this way, Beowuuf!

[beowuuf]

lol, thanks, but there's RTC 0.20 out there too! : )