I'm A Banana
Potassium-Rich
JamesonCourage said:If the Staff of the Magi needs an arcane magic user to wield it, what is gained by saying "needs to be a mage" over "needs to be wielded by an arcane magic user"?
The Q&A seems to describe a system that's all about gatekeeping. If it is used with such a light, infrequent touch -- only with "highly specialized" mechanics -- it's more about defining who isn't allowed to do a thing (or get extra out of a thing) than giving a list of items that a given character can use. Rodney pretty much comes out and says it:
My main reaction here is why the heck we need to do the restriction at all. Is it going to break the game if my cleric of the god of magic gets her hands on a full-potency staff of the magi? Probably not. It's a magic item -- a purely additive bonus.Rodney Thompson said:These groups are just a tag or label that can be applied to the classes, grouping them by their common elements, so that in the rare case where we need to restrict another game object, we can do so
If they're being conservative and applying it only in highly specialized ways, it's not even going to be very useful for organization purposes. Just, you know, if your DM rolls a random magic item and it's a staff of the magi or something similar, your party fighter can't use it fully, even if he has an INT of over 9,000 and your party mage, as a sorcerer, is mostly a CHA monkey who used INT as his dump stat?
Bleh. At least if they apply it conservatively, it will be a label I can pretty much ignore, but I'm still with a lot of the people who question how much the game is really gaining from this particular "tech."