Posted by Infidel on 07/16
"The change to stun (where it doesn't cost mana without a victim)
will not be going in after all."
Hmm, it would have been fair if it went in... Laggy players
are at a great disadvantage when it comes to trying to land
spells on fleeing opponents. -flop-
I think either that should be changed or at least rip surge as
headbutt has too many things going for it in comparison.
Friday, July 16, 08:06AM
As a laggy mage, I have to agree. -burp-
On a fleeing opponent, I no loger use stun at all, because I simply
waste a load of mana for no result. If the mana loss were at least
reduced it would help a lot.
Yours in boggy gooeyness,
Fungus the Bogeyman [Mafia Stenchmeister]
Friday, July 16, 08:42AM
Okay, I was a little brief in the message where I said that the change
wasn't going to happen. Let me be a little more verbose here.
I decided not to put in the change for two reasons:
First, it's an anomaly for the spell to work that way. At some point,
we'll probably move the code that does the targetting and mana charging
out of the individual spells and into one or two functions. This will
allow us to more easily make spells work consistantly (right now, which
spells charge if you mistype the target? Which don't? Which default to
the caster if no target is given?) The idea would be to have each spell
consistant with similar spells (which is to say, for example, combat
spells would cost mana if they miss. Prep and combat spells wouldn't
default to the caster if no target is given, but things like fly and
The second reason is that at the Q & A there were a few people cackling
with glee as they prepared to go off and make their next pkiller. This
isn't necessarily a bad thing, but it was enough that I thought it
might be better to rethink the decision.
The code may will go in next week, there hasn't really been a decision
made, but I thought that it was worth more thought than I gave it when
I put it on the todo list.