We're getting caught up in definitions and interpretations of skill descriptions here. Are skill descriptions really all that trust-worthy?
But, to ease the confusion, consider it this way. A spell is the act of magically causing something to happen. You pay your energy, you wiggle around a bit, and presto change-o, reality bends to your will. That specific act can be countered or interrupted by things that affect "spells".
Now, one of the magical effects you can create with a spell is to bring into being an enchantment or a hex on your target. That magical, ongoing effect, is something that will last for a set amount of time (Maintained enchantments are another story altogether and, in fact, used to be classified as something altogether different. They were "Blessings" not spells at all. Which led to things like "Rend Blessings" and "Blessed Aura".) and provide a constant or triggerable magical effect of its own. You cannot counter that enchantment or hex by countering a spell. It requires disrupting the magical energies within that enchantment or hex itself and is an entirely different beast than stopping someone from doing the happy dance that lets them create it. You can, of course, prevent the hex or enchantment from coming into being by interrupting or countering the spell that creates it. But that's not countering the hex or enchantment.
If we're really going to get nit-picky about things then there are no "enchantment spells" or "hex spells" there are just "spells". Those things that are enchantment spells now should read "Spell. When used this spell creates an enchantment on target ally that does...whatever". And hex spells should be similar. However, since the enchantment and the spell that created it are so closely linked and share the same name and you'll want to know the effect of the enchantment by looking at the spell and using such a spell sets it out in its own little area full of traps and counters, it's denoted that the spell creates an enchantment by saying it's an "enchantment spell".
Skill classifications are still a bit of a cobbled together mess. At least we're not in the days when there were Blessings and Mantras and Pet Skills and more floating around but some skills just make you scratch your head. Why's Life Siphon a hex and not an enchantment? Why's Shield Bash a skill and not a stance? And so on, there's plenty of fudging and exceptions that make setting out exact rules from skill classifications tilting at windmills at best.
Quote:
|
Originally Posted by Bgnome
Smite said it was a staff attack in the old description. this was most likely before the development of wands, so now it does not mention a specific weapon requirement. do you still need a staff or a wand to use it?
|
Yeah, Smite's the Monk attack skill. As far as I know, it's never needed a staff to use. In fact, long ago there weren't even any staves in the game. It's always required a melee weapon, a fact which caused me no end of consternation when my Smiting mon/war decided to give it a try. It's not a bad little skill, I mean, it can just carve through undead and Necros where it'll often do more damage than most Final Thrusts without the added precondition of their being under 50%, it just costs too much energy for most Warriors and is burried in an unpopular skill line.