[CF-Devel] Paralyze

[David Hurst]

>
     
      > That makes it impossible to remove paralyze - thats the reason why there is
     
     >
     
      > no "remove paralyze"
     
     >
     
      > in the game - the server never knows why the speed is decreased . It can be
     
     >
     
      > paralyze but also a
     
     >
     
      > different effect.
     
     >
     
     
     >
     
      In my wholly honest opinion, it should be impossible for a player to be
     
     >
     
      paralized.  Using my mud as an example again, we had to remove the ability to
     
     >
     
      paralize players for a number of reasons:
     
     
I disagree I love it as a spell and getting paralyzed is kind funny, but I think it is overly powerful.

>
     
      1)  It's not *fun* to be paralized.  You are stuck, can't do squat, you just
     
     >
     
      get to witness your own death and feel helpless about it.  Death sucks, but
     
     >
     
      unavoidable death sucks alot worse, and leaves a lasting anger in the player.
     
     
Woah this is an excellent point. This comes back to making a game fun, crossfire being the game it is is fun. But some things are not as fun as they could, for example paralyze and drain. I also feel some classes/races are perhaps chosen by newbies, when they really are not designed to be fun for newbies. Q's, fireborn and wraiths, are by far the most popular races for newbies, and yet these are the three hardest!

>
     
      2)  It really becomes a problem when lots of players are around, some people
     
     >
     
      aren't nice, and would paralize newbies to just be mean.
     
     
Funny for the person doing it, very very unfunny for the victim.

>
     
      3)  Players who have never had it happen got confused, and thought the server
     
     >
     
      blew up, or the network died on them, and would disconnect.
     
     
Yeah, I remember I thought this when I first got paralyzed. I thought it was bad lag and got really peeved =).

>
     
      4)  The worst case, is usually, player gets paralized, and the doorbell rings. 
     
     >
     
      this is almost allways a complete lose for the player.  You have no way to save
     
     >
     
      your game, or get out of wherever you are.. you are just stuck, and it sucks. 
     
     >
     
      Add to that the ability in crossfire to die, and then re-die over and over to
     
     >
     
      starvation, and things get pretty bleak.  (Thats a different issue, which I do
     
     >
     
      plan on solving soon)
     
     
Yeah true again

>
     
      In my experience, it is a very cool spell, and provided a very realistic and
     
     >
     
      cool experience, but the negative aspects of it were so bad, that it was
     
     >
     
      driving players away.  Nothing is more frustrating to a player than dieing in a
     
     >
     
      situation like that.  More often than not, players that were bitten by it, fell
     
     >
     
      into the "quit for good" category.
     
     
Agree here.

>
     
      Basically on the mud this was solved by making the spell non-functional against
     
     >
     
      players, so you could still paralize monsters.  In addition, we implemented a
     
     >
     
      "hold person" spell.  The hold person spell had the same effect as being
     
     >
     
      braced, but being unable to shut it off.  A player affected by that could
     
     >
     
      recall away, and then wait it out.
     
     
This is a very interesting, what about we make paralyze brace the player, and only allow them to use_item and use_wisdom? Thus they can heal, recall and use equipment that might lesson the problem.. before they die. I really like this idea.