GAME IMPROVEMENT IDEA: Give us a DUPLICATE STUN GRAPHIC Indication

[RiverBummer]

Mat never fails to amaze me with his infinately nested worst-case hypothetical speculative recursion on cause and effect.

Capturing the flag on this one point: We agree it would be useful to know if a 2nd stun landed or not - even if the effect does not stack past the current melee round. The more visual feedback we have the more effective tweaking of runes becomes possible for the user.

On the second point of Matt's pessimistic world-view (which I see now is his natural reflex for anything he did not suggest) I almost completely disagree with the astonishingly small substance of his objections. Matt would have us all believe that the developers at Tynon are completely incompetent and unable to work through the too complex cerebral mechanizations to give some manner of reasonable and fun multi-stun stack bonus that would not invoke Matt's chicken-little catastrophic effect on the whole Tynon universe of game play; nor increase the work load for the poor programmers and prevent them from doing other things. Having designed, implemented and managed software development for a living I know the culture and most find this sort of mother-henish conjecture at least mildly insulting.

Philosophically, a special effect capability resides withe EACH in-game character and EACH, SHOULD do SOMETHING SPECIAL in the same way EACH hero in formation had a chance to deliver extra damage when its character skill fires INDEPENDENT of the other hero's in formation. It would be conceptually "the right thing" to give at least some damage bonus or to reset the timer to carry it into the next round so that stuns don't end on round boundaries (which is pathetically unrealistic to anything in real or magical realms). If nothing else give a fraction of health back to the 2nd stunner or let him retain his Morale (not lose his morale to see his hit totally ignored and of no consequence) if the stun is already active (revert to normal melee mode of hit to try the morale again on the next sortie).

Design by committee and consensus never works especially when the parochial psychology of adolescent/immature pessimism and the regular sort of "I didn't think of that first" hubris reverse-synergizes with the double-stunning negative effects of doing nothing - just to avoid manufactured fears and ridiculous concerns. What most any rational person sees, even reading between the lines here, is that the current implementation is not rational - not even for a fantasy world. Rather than second guess things why don't we let the software development manager DO HIS JOB and see if his team are up to doing something smart with this rather than just tossing out faux obstructions like "we could use their time better fixing other things" sorts of ridiculous arguments?

There's a gazillion ways that this could be implemented in a non-intrusive way that does not lead to "the sky is falling" cascade of hysteria...