Previous Thread
Expand All
Collapse All
Ignore Author
ReplySanctify Weapon
Inspiration Spellbook
Cyclic
Utility/Augmentation
Mana: 20-60
-The paladin’s holy weapon must be in hand for the cyclic pulse to fire.
- Performing actions that break research will break this spell.
-Every cyclic pulse forces the paladin into the kneeling position.
- Every cyclic pulse hits the paladin as if he/she cast Aspirant’s Aegis on someone else.
- Every cyclic pulse the paladin’s holy weapon gains 1 charge per 20 mana of the spell.
I like the idea, but I don't think it's necessary to be a spell. I'd rather see it as some kind of ritual the Paladin naturally gets.
Uzmam! The Chairman will NOT be pleased to know you're trying to build outside of approved zones. I'd hate for you to be charged the taxes needed to have this place re-zoned. Head for the manor if you're feeling creative.
Uzmam! The Chairman will NOT be pleased to know you're trying to build outside of approved zones. I'd hate for you to be charged the taxes needed to have this place re-zoned. Head for the manor if you're feeling creative.
The problem I see here is that you wrote a combat spell then out in books to ruin combat. Forced kneeling every pulse and breaking on most verbs makes no sense. A cyclic non ablative barrier is ok, even if it's the lesser version, and the pulsing holy charge would be nice, just not sure why it needed to force kneel and be fragile?
I'd strongly suggest removing the drawbacks from spells. No one really uses them, because they never make the game more fun and supposedly spells don't get to be bigger just because they suck.
I'm a badger, I be badgerin'
I'd strongly suggest removing the drawbacks from spells. No one really uses them, because they never make the game more fun and supposedly spells don't get to be bigger just because they suck.
I'm a badger, I be badgerin'
>The problem I see here is that you wrote a combat spell then out in books to ruin combat. Forced kneeling every pulse and breaking on most verbs makes no sense. A cyclic non ablative barrier is ok, even if it's the lesser version, and the pulsing holy charge would be nice, just not sure why it needed to force kneel and be fragile?
As I understand it, the suggested spell is intended to be used exclusively to charge holy weapons, so it wouldn't necessarily be a combat spell. The intention was not to have it cast a barrier (AA), just to give the same drawback as casting AA on others (hit to vit, conc and fatigue). In other words, I understand it to be a spell that charges our holy weapon at the expense of the caster's vit, concentration and fatigue and forcing the caster to kneel.
>I'd strongly suggest removing the drawbacks from spells. No one really uses them, because they never make the game more fun and supposedly spells don't get to be bigger just because they suck.
Charging holy weapons has some drawbacks now, the biggest of which is limited charging sites and holy icons. I think that's why Sylv gave the spell those drawbacks. However, those drawbacks are pretty severe. It might take a really long time to get an adequate number of charges with one charge per pulse, and one charge per pulse is not worth the cost of vit, conc and fatigue IMO. If we get a spell that charges holy weapons, I'd rather see it work more like AG, where it would take a favor and give you a bunch of charges. Hell, it can be a metaspell for AG that allows the caster to cast it on his/her holy weapon for charges.
As I understand it, the suggested spell is intended to be used exclusively to charge holy weapons, so it wouldn't necessarily be a combat spell. The intention was not to have it cast a barrier (AA), just to give the same drawback as casting AA on others (hit to vit, conc and fatigue). In other words, I understand it to be a spell that charges our holy weapon at the expense of the caster's vit, concentration and fatigue and forcing the caster to kneel.
>I'd strongly suggest removing the drawbacks from spells. No one really uses them, because they never make the game more fun and supposedly spells don't get to be bigger just because they suck.
Charging holy weapons has some drawbacks now, the biggest of which is limited charging sites and holy icons. I think that's why Sylv gave the spell those drawbacks. However, those drawbacks are pretty severe. It might take a really long time to get an adequate number of charges with one charge per pulse, and one charge per pulse is not worth the cost of vit, conc and fatigue IMO. If we get a spell that charges holy weapons, I'd rather see it work more like AG, where it would take a favor and give you a bunch of charges. Hell, it can be a metaspell for AG that allows the caster to cast it on his/her holy weapon for charges.
Disadvantages are kinda a delicate topic, and in almost all situations these days we try to avoid a situation where we're balancing a spell with disadvantages. Instead, we seem them as helpful and sometimes necessary flavor elements. A terrible necromantic rite is illegal not because it's super powerful, but because that's the flavor of necromancy. Teleportation spells can kill a Moon Mage because we love killing Moon Mages, not because there's something fundamentally powerful about teleportation.
-Armifer
"In our days truth is taken to result from the effacing of the living man behind the mathematical structures that think themselves out in him, rather than he be thinking them." - Emmanuel Levinas
-Armifer
"In our days truth is taken to result from the effacing of the living man behind the mathematical structures that think themselves out in him, rather than he be thinking them." - Emmanuel Levinas
I think it's important to recognize the difference between disadvantages and limitations.
Disadvantages (such as the ones Armifer described above) are not priced into spells. They're flavor, or guild mechanics, or lore requirements or what-have-you. They make spells feel more unique and, while they are mechanically a disadvantage, they enhance the spell overall.
Limitations are a different matter - those we do price into spells. Examples of this include significant restrictions to when or where a spell can be used. Generally these aren't because of game balance but to maintain logical consistency, yet they have a very significant impact on the use of the spell. Starlight Sphere only working at night is a good example of this.
Another type of limitation we'll price into a spell is if it has a reduced function compared to 'baseline' (For example, a debuff that is only half strength for whatever reason) but those are really outside the scope of the discussion here.
-Raesh
"Ever notice that B.A.'s flavor text swells in direct proportion to how much one of our characters is getting screwed?" - Brian Van Hoose
Disadvantages (such as the ones Armifer described above) are not priced into spells. They're flavor, or guild mechanics, or lore requirements or what-have-you. They make spells feel more unique and, while they are mechanically a disadvantage, they enhance the spell overall.
Limitations are a different matter - those we do price into spells. Examples of this include significant restrictions to when or where a spell can be used. Generally these aren't because of game balance but to maintain logical consistency, yet they have a very significant impact on the use of the spell. Starlight Sphere only working at night is a good example of this.
Another type of limitation we'll price into a spell is if it has a reduced function compared to 'baseline' (For example, a debuff that is only half strength for whatever reason) but those are really outside the scope of the discussion here.
-Raesh
"Ever notice that B.A.'s flavor text swells in direct proportion to how much one of our characters is getting screwed?" - Brian Van Hoose
This thread is quite educational for me. I put in those negatives for a few reasons. The biggest one is that I wanted to mimic the process a character goes through when charging a holy weapon at a holy site. There is a degree of silent reverence and concentration involved that, I felt, would not be possible in combat. The AA part was only the hit- I wanted to use something that already exists in code and would be already identifiable by players so they know what to expect. ICly I imagined the paladin finding a nice, quiet spot (Like the Green on Ratha), kneeling, and then giving of him/herself to channel divine power into his or her weapon- in a sense turning his/her self into an altar in their own right. OOCly, I keep picturing in my mind all those stained glass windows and heroic tales of knights kneeling with their swords pointed down in front of them, praying for their cause and for the blessings of their weapon. I also know that holy weapons are (rightfully) regarded as pretty darn powerful and more than one player has expressed a concern that allowing a paladin to charge without a required location would stimulate a nerfing of holy weapons (I personally feel they need more customizable umph like I posted with Aspect Prayers) so I treated the spell as a sort of negotiation- what am I willing to go through or 'offer up' in exchange for the ability to actually train with my favorite weapon, avoid so many Mammoth rides, and still not reduce the power of said favorite weapon. The cricisms I read on this I consider very constructive- thank you for those. As far as the issue I at hand I'm don't intend on giving up on it and instead would like to hopefully inspire other players to post thoughts addressing what I consider to be a big problem in the guild. If in the process I risk a little reticule putting out the occasional really dumb idea in order to chance that a fraction of my slew of ideas actually help then that's what I'm going to risk- as far as I'm concerned my guild is worth it.
