Deprecated: Assigning the return value of new by reference is deprecated in /home/virilneu/public_html/blog/wp-includes/cache.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /home/virilneu/public_html/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/virilneu/public_html/blog/wp-includes/theme.php on line 540
Virilneus’ GS4 Idea Book » Curse Improvements & Disease

Virilneus’ GS4 Idea Book

December 3, 2007

Curse Improvements & Disease

Filed under: Sorcery — Virilneus @ 2:40 pm

Curse is a peculiar spell, unlike most other spells in game the affects of curse are controlled by stance, this is an artifact of coding practices that are over 10 years old, it is time to update curse to modern standards.

 You see, way back when, stance was the only way available to coders to differentiate spell types, and so curses became stance dependent, and the stance choices were mostly arbitrary. I know they were arbitrary because they were random. All sorcerers shared just 1 curse, the vulnerable TD lowering one, all others were randomly assigned to different stances.

GS4 changed that, it made the curses standardized based on stance, but what it should have done is gotten rid of the stance method altogether.

The better way to do this type of affect is through a verb. CURSE, like BESEECH for paladins or CURE for empaths, should be a spell verb allowing a sorcerer full access to their varying curses from any stance.

>curse seer vulnerable

>curse seer clumsy

>curse seer itchy

And so forth. The side benefit of doing this, is that no longer will the number of curses be limited by the number of stances, sorcerers could potentially have dozens of different curses if a GM wanted to code them. Not that I’m asking for that kind of coding resources, but the possibilities would be limitless.

What I would like to see is for Disease turned into a curse. Currently it is on the list of spells to be overhauled to make it more worthy of its spell slot. Considering what was done with 118, I’m optimistic about the possibility of gaining a nifty attack spell, however I think sorcery could gain a better attack spell if GMs were not limited by the concept of disease. So, I would like disease tucked nicely away into curse. Freeing up 716 for a new cool attack spell.

 Then we have options, such as we could move 713 to 716, thus freeing up 713, or move 713 to 716 and move 707 to 713, thus freeing up 707. So if you wanted a 7, 13, or 16 mana attack spell, the options are there. Finally 713 could also be folded into curse, thus freeing up 2 spell slots.

As they stand now 713 and 716 are more or less just novelties, like the different types of curses, I think they’d fit well merely as components of curse rather than their own standalone spells.

 As for what spells sorcerers could use. We’re the only pure profession without a native AS based attack spell. We’re also the only pure profession without an instant attack spell whose damage can be increased through native lore study. This makes our current attack spells weaker than those from other professions at high levels. Finally, a mass target CS based spell is often desired.  In the realm of non-attack spells, we also lag behind all other pure professions in the realm of AS boosters.


  1. […] already posted about making curse verb based but what about doing more with it, what if when a curse was self-cast on the sorcerer it gave them […]

    Pingback by Virilneus’ GS4 Idea Book » Blog Archive » Curse Buffs — December 8, 2007 @ 10:01 am

  2. […] mentioned in this post I would like to see Curse changed to be verb based and then have 716 and 713 rolled into it as […]

    Pingback by Virilneus’ GS4 Idea Book » Blog Archive » 713 or 716: Major Disruption or Essence Ball — December 8, 2007 @ 10:16 am

  3. […] - Get rid of Nightmare, roll into curse and then Major Disruption or Essence […]

    Pingback by Virilneus’ GS4 Idea Book » My Sorcerer Spell List Review — December 7, 2008 @ 8:28 am

RSS feed for comments on this post. TrackBack URL

Leave a comment

Powered by WordPress