Skins: |

NWN SCRIPTS

Title

Hemophiliacs Always Bleed to Death (0.03BETA) - Robust configurable player/henchman bleed/death/respawn system for SP/MP/DMed/Non-DMed play

Author

Demetrious&OldManWhistler

Submitted / Updated

08-21-2003 / 04-01-2008

Category

Rulesets

Expansions

Works on all versions

View Code

Hemophiliacs Always Bleed to Death


BETA VERSION 0.03
- Robust configurable player / henchman bleed / death / respawn system for SP / MP / DMed / Non-DMed
by Demetrious and OldManWhistler

http://nwvault.ign.com/Files/scripts/data/1061531334485.shtml

CAVEAT
This is a (highly polished) beta release. The intention is to release the full version in late September 2003.

We want this to be hands down the best bleeding / death / respawn system out there and we need your input to make that possible.

INTRODUCTION

From the same fools who brought you PHB Familiars and UMD by the book, Supply Based Resting, Party Loot Notification, Permanent Area Effect Spells, Speed Override, Take Cover (PHB environment AC) and PHB Movement Skills (Balance, Climb, Jump, Swim, Escape Artist).

The main intent of this system is that players never instantly die. Player death will always be caused by player action -- because help didn't reach them in time and never because of a bad roll of the dice. They will always go through bleeding before reaching death. There are stabilization checks (10% chance) and bandages can bring you back to life on a DC 15 heal skill check as per PHB, except that when stabilized you instantly go to 1 HP.

One of the unfortunate side effect of playing a real-time game rather than a turn-based game is that it can be very difficult to react to a player bleeding in a timely matter. In turn-based play, your party members would know that you are bleeding and be able to react within one or two round. This system seeks to restore the ability for your party members to be aware and react.

With the default settings of this system it should be very rare for low level players to die if they have party members with them for support. Once they reach higher levels and have the means to afford Resurrection and Raise Dead then the time to bleed to death decreases. The intention is to make death a rare occurrence. After all, with all those local clerics tossing out rez like candy, its any wonder there's still undead around left to fight.

The bleed / death system is intended for multiplayer use but CAN be used in solo play. The respawn system is intended for multiplayer use only but can be used for single party if the auto-raise feature is enabled. The auto-raise feature can be configured to use up scrolls. The respawn system can be disabled or easily replaced with a different system.

This system was originally built with single-party DMed play in mind, but it should be able to scale to ANY kind of play. This is the Swiss Army knife of death systems. The same bleeding / death / respawn system can be used for henchmen AS WELL as players, removing additional complexity from your module.

If you want to want to support solo play with this script, then enable the fast bleed option and set the solo auto-raise option to a very low value. That way when a player bleeds / dies in solo play they do not have to wait long for help that will never come.
THANKS
- HCR team, at one time or another we must have stolen some of your ideas.
- Lazybones for coming up with a name for the system.
- Typhonius, DickNervous, Feds, Ochobee and Blewz for help with the initial play-testing.

Apologies to anyone who is suffering, or knows someone who suffers with a hereditary blood-coagulation disorder and takes offense at the name. We thought it was a rather witty name for a system where players must always go through bleeding before dying. No offense was intended.

OTHER WORKS BY SAME AUTHORS

Demetrious' Portfolio
http://nwvault.ign.com/portfolios/data/1055729301.shtml
OldManWhistler's Portfolio
http://nwvault.ign.com/portfolios/data/1054937958.shtml

FEATURES

IMPLEMENTATION NOTES

- 4 scripts, 3 player items, 2 DM items, 1 placeable. The only NWN content modified is Raise Dead and Resurrection spells, and the henchmen death scripts should be modified if you want to enable henchman bleeding / respawn as ghost.
- It uses DelayCommand events scheduled on the players instead of heartbeats. It only uses CPU cycles when players are bleeding, dying, dead, respawned or entering / leaving the module. This removes the overhead of searching through the player list on the heartbeat.
- Delayed commands are rescheduled at the start of a chain to prevent stalled states when the CPU is overloaded and events start getting dropped.
- DelayCommand is *NOT* a recursive function, so there is no worry about CPU performance hits.
- All settings are CONST variables that are evaluated at compile time to speed up execution.
- Henchmen only bleed / respawn if they have a master. Potions can be used on bleeding henchmen as well as any of the normal means of healing another creature. Henchmen bleeding is implemented by "faking" to 0 to -9 HP bleed with 10 to 0 HP.

FEATURES NOT IMPLEMENTED
- We considered having an option for limiting raising and resurrecting to same party only (to prevent death penalty griefers) but you cannot invite dead players to your party so we decided against that.
- We considered storing player location persistently, but all persistent location systems I have seen require some kind of workaround to store the player location over a module reset (most common being an additional script in the exit event of every area). We figured it was better to leave such complexity out of this system and let the end user choose the persistent location system that is right for their needs.
- We do not include any kind of bind stone system. But our respawn system can easily be removed (changing one line in the configuration) so that you can replace it with the respawn system of your choice.
- Dropped items are not automatically picked up. Dropping large inventories is laggy enough without adding additional processing.
- There is no ability to change the settings while the module is running. This is because all the settings are constants to speed up execution.
- It is not possible to make familiars or animal companions bleed because there is no scripting command for making them rejoin the party as a familiar / companion.

ITEMS:
- All items are stored under Custom5 in the palette or Chooser.
- Automatically given out to players who do not possess them on log in.
- All items have no weight, are worth no money and cannot be sold.
- Items cannot be transferred to other players or dropped.
- There is a Skull item that displays the player's bleed / death / lost XP / lost GP statistics.
- There is a Bandages item that can stabilize a bleeding player on a DC 15 heal check or make a respawned ghost follow the player using the bandages.
- There is a Rulebook item that displays how this system is configured for the module. It displays the penalties as they would currently apply to the PC reading the book.
- There is a DM statistic item that can display the bleed / death / lost XP / lost GP statistics for an entire party.
- There is a DM force death item that can instant kill players / henchmen without putting them through the bleeding state. You can tie this in with the prevent death feature to make death only happen when the DM decides it should.

 BLEEDING:
- Works for players as well as henchmen.
- 10% chance of self-stabilization to 1 HP.
- If going from living to -6 or lower you will be capped at -5 to give you a good chance to be saved.
- If going from living to dead you will be set to -6 to -9 HP instead of dying.
- Free DC15 heal check bandages can be used to stabilize other players to 1 HP.
- Any healing will stabilize another player.
- Casting raise / rez on a bleeding player stabilizes them to 1 HP or more. (It is a waste of a spell, but it works).
- Immune to damage while bleeding. You have to bleed to death.
- Regeneration items always stabilize players and keep them from ever dying. (Defaults to leaving regeneration items on the player)
- Bleeding players are temporarily made invisible to make monsters change targets.
- Players can be made invisible for a configurable amount of time after bleeding to give them a chance to heal or run away (default is 12 seconds).
- Possessed familiars die instead of bleeding.
- First bleed message tells the total time until death.
- Nearby party members are notified of the bleeding player every round, even number of rounds between bleeding is greater than one.
- All DMs are notified of when players are bleeding / dying. (default on)
- Number of rounds between bleeding is based off of player level. (defaults to giving low levels a long time between bleeding to reduce the chance of dying since they can't afford Raise / Rez)
- Fast 1sec bleed when playing solo without a party. (default off)
- There is an option for preventing player death until they reach a certain level. (default is 4). The DM Force Instant Death widget can bypass this setting.

DEATH:
- Force auto-respawn after being dead for a specified time. (default 3 min)
- Force auto-raise after being dead or respawned for a specific time. (default off)
- Auto-raise can be configured to only work if the player possesses raise dead / resurrection scrolls that are consumed in the process. If this is enabled then the dying can never cause raise dead / resurrection scrolls to be dropped or destroyed. (default off)
- Additional force auto-raise timer for solo players only. (default off)
- Henchmen have their own separate auto-respawn and auto-raise timers.
- DMs can bring dead players back to life with no penalty by using a DM heal.

HENCHMEN BLEEDING AND DEATH:
- The same bleeding / death / respawn system can be used for henchmen by modifying your henchmen OnDeath scripts. Requires two additional lines to your henchmen scripts and should be compatible with all henchmen AI provided that they use the NW_ASC_BUSY condition properly.
- Henchmen support does not require any other modifications.

PENALTIES:
- Separate % GP / XP penalties for respawn, raise dead and resurrection.
- XP penalty can be configured to prevent level loss (default no level loss).
- GP penalty can be configured to have a maximum amount to take (default 10,000gp max).
- If dropping / destruction of all gold is enable, then no gold will be lost to the penalty (since the player drops the items before the penalty is applied).
- There is no penalty for henchmen bleed / death.
- User defined functions called at bleed, respawn, raise and rez that can be used to apply other penalties without having to go deep into the internals of our code.

ITEM DROPPING ON DEATH:
- Item dropping on player death can be configured as any combination of the following options. Any options can be configured to do nothing (0), drop item (1) or destroy item (2). The conditions are evaluated in an order of precedence.
  - Drop nothing. (default)
  - Drop all gold. (this will avoid any GP penalties since gold is dropped before penalty applied)
  - Drop equipped left-hand / right-hand items.
  - Drop a random equipped item.
  - Drop the most expensive equipped item.
  - Drop all equipped items.
  - Drop Raise Dead / Resurrection scrolls.
  - Drop a random backpack item.
  - Drop the most expensive backpack item.
  - Drop all backpack items.
- Dropped items are NOT automatically re-equipped or picked up.
- If players forget to pick up items they dropped, they are automatically reminded every 30 seconds.
- The placeable created to store dropped items is automatically destroyed when it empties.
- If all of the drop settings are disabled then the placeable is not created.
- There is an option to destroy dropped items rather than store them in a placeable.

PERSISTENCE:
- Persistence can be disabled with a flag. (default enabled)
- Persistence only works with a multiplayer server. It has no effect in single player (no OnClientLeave event in single player)
- Statistics to keep track of how many times the player has bled / died in total, how many times since the server was restarted, and how much gold / XP the player has lost in total from penalties.
- Persistent DB functions for storing bleed / death / respawn state.
- Auto-respawn and auto-raise timers are stored persistently at various increments.
- Players remain in the same state over module restarts, even with local vault characters.
- Persistent data is stored with one DB write at OnClientLeave and one DB read at OnClientEnter. It is very fast with minimal DB size (less than 1kb per player record).
- When bleed / death / respawn is restored at player log in, it does not reapply the penalties or falsely increment the statistics.

RESPAWN:
- Can be used with other respawn systems (default uses our system)
- Option to disable death GUI to remove respawn. (Default GUI enabled)
- Option to disable respawn button but leave death GUI (Default respawn button enabled)
- Additional system to respawn as a ghost with no player control. (default enabled)
- Using bandages on respawned ghost makes them follow you if you are in the same party (simulates carrying a corpse).
- Living players can barter with respawned ghosts (simulates search the players corpse for scrolls, except corpse has a say in what is taken).
- Respawned ghosts cannot be DM moved by shift-click.
- Respawned ghosts cannot be recovered in single player by using the dm_heal console command. So the respawn state could be used as permanent death in a single player game by setting the auto-respawn timer to 0.1.
- Casting raise or rez brings respawn ghost back to life, but applies raise / rez penalty on top of respawn penalty.
- DMs can bring the "ghosted" PC back to life by toggling invulnerability (no penalty). Casting raise or rez also works, but DM heal does not.



INSTALLATION NOTES

// If you are unsure of which scripts are currently associated with your module event, go to your
// Module Properties and click on the Events tab.

// #1: Change your Module OnPlayerDying script to "habd_onpcdying".

// #2: Change your Module OnPlayerDeath script to "habd_onpcdeath".

// #3: (Optional) Change your Module OnPlayerRespawn script to "habd_onpcrespawn". If you wish
// to use a different respawn system then make sure the HABD_RESPAWN_SCRIPT variable in
// "habd_include"  is set to the script you want to use.

// #4: Add the following line to your module OnActivateItem, OnClientEnter,
// OnClientLeave, OnUnAcquiredItem, nw_s0_raisdead, nw_s0_resserec scripts:
#include "habd_include"

// #5: Add the following line to your module OnActivateItem script:
if (HABDOnActivateItem(GetItemActivator(), GetItemActivatedTarget(), GetItemActivated())) return;

// #6: Add the following lines to your module OnClientEnter script:
HABDGetDBOnClientEnter(GetEnteringObject());
DelayCommand(6.0, HABDItemsOnClientEnter(GetEnteringObject()));

// #7: Add the following line to your module OnClientLeave script:
HABDSetDBOnClientLeave(GetName(GetExitingObject()));

// #8: Add the following line to your module OnUnAcquiredItem script:
if (HABDOnUnAcquiredItem(GetModuleItemLostBy(), GetModuleItemLost())) return;

// #9&10 automatic: Imported the habd_nw_1_31.erf file to replace your nw_s0_raisdead
// and nw_s0_resserec scripts with SoU 1.31 compliant ones.

// #9 manual: Open nw_s0_raisdead. It should look like:
   if(GetIsDead(oTarget))
   {
       //Apply raise dead effect and VFX impact
       ApplyEffectAtLocation(DURATION_TYPE_INSTANT, eVis, GetLocation(oTarget));
       ApplyEffectToObject(DURATION_TYPE_INSTANT, eRaise, oTarget);
       // HABD CODE START
       // Apply the user defined effects.
       HABDApplyPenaltyIfDead(oTarget, SPELL_RAISE_DEAD);
       // HABD CODE END
   }
   // HABD CODE START
   HABDCureRespawnGhost(oTarget, SPELL_RAISE_DEAD);
   // HABD CODE END

// #10 manual: Open nw_s0_resserec. It should look like:
   if (GetIsDead(oTarget))
   {
       //Declare major variables
       int nHealed = GetMaxHitPoints(oTarget);
       effect eRaise = EffectResurrection();
       effect eHeal = EffectHeal(nHealed + 10);
       effect eVis = EffectVisualEffect(VFX_IMP_RAISE_DEAD);
       //Apply the heal, raise dead and VFX impact effect
       ApplyEffectToObject(DURATION_TYPE_INSTANT, eRaise, oTarget);
       ApplyEffectToObject(DURATION_TYPE_INSTANT, eHeal, oTarget);
       ApplyEffectAtLocation(DURATION_TYPE_INSTANT, eVis, GetLocation(oTarget));
       // HABD CODE START
       HABDApplyPenaltyIfDead(oTarget, SPELL_RESURRECTION);
       // HABD CODE END
   }
   // HABD CODE START
   HABDCureRespawnGhost(oTarget, SPELL_RESURRECTION);
   // HABD CODE END

// #11.1: Optional, for bleeding / respawning henchmen open up your henchmen OnDeath event scripts (ie: nw_ch_ac7) and add the following line to the top:
#include "habd_include"
// #11.2: Add the following line as the first line inside of the main function.
void main()
{
    // HABD CODE START
    if (HABDMakeHenchmanBleed()) return;
    // HABD CODE END

// #12: Open up "habd_include" and go to the configuration modification section.
// Change the configuration as it suits your needs. Make sure to save the include
// file and recompile your module to ensure that the settings take effect.



CONFIGURATION SETTINGS

// BLEEDING SETTINGS
//
// HABD_SOLO_FAST_BLEED
// If set to TRUE, then players without a party go through the bleeding stage
// VERY fast. This is useful for single player modules or when people are
// playing solo in a multiplayer module. They will still have the stabilization
// chances from bleeding to death without having to wait such a long time to die.
//
// HABD_NERF_REGENERATION_ITEMS
// Regeneration items will cause the player to never bleed to death. This is
// how AD&D intended them to work. Unfortunately that also means that characters
// with regeneration items will never die with this bleeding system. This is why
// regeneration items should be very rare, yet few people set up their campaigns
// that way.
// If you set this variable to TRUE, it will enable a workaround that unequips
// regeneration items when the player starts bleeding.
//
// HABD_NO_DEATH_BEFORE_LEVEL
// This will turn death off until the players have reached a certain level.
// Players are NEVER notified that this setting is turned on (to prevent abuses).
// From the player's perspective it will always look like they are stabilizing.
//
// HABD_POST_BLEED_INVIS_DUR
// Setting this value greater than 0.0 will give players invisibility for the
// specified period of time after they recover from bleeding. This is to give
// them a chance to heal or run away.
//
// HABD_ROUNDS_PER_BLEED_*
// These variables are used to set how many rounds it takes to bleed -1 HP
// based on the player level. If you set the value to 0, the player will
// instantly bleed to death. Do not set to a negative value.

// DM NOTIFICATION SETTINGS
//
// HABD_DM_NOTIFICATION_ON_BLEED
// If TRUE, it will SendMessageToAllDMs when a player bleeds.
// This can generate a lot of spam on the DM channel. It is only intended for
// use with single party games.
//
// HABD_DM_NOTIFICATION_ON_DEATH
// If TRUE, it will SendMessageToAllDMs when a player dies.
//
// HABD_DM_NOTIFICATION_ON_PENALTY
// If TRUE, it will SendMessageToAllDMs when a gets an XP / GP penalty from respawn / raise / rez.
//
// HABD_DM_DISPLAY_STATS_TO_ALL
// If TRUE, using the DM statistics item will display the statistics to all DMs.
// If FALSE, it will display only to the DM using the item.
// Setting it to TRUE is useful when you want to capture such info into your
// DM Client log file.

// TIMER SETTINGS
//
// All timers start counting from the moment the player dies.
//
// HABD_FORCE_RESPAWN_TIMER (AUTO-RESPAWN)
// HABD_NPC_FORCE_RESPAWN_TIMER (AUTO-RESPAWN)
// Set this to a value greater than 0.0 to force respawn after a certain amount
// of time has lapsed. If players remain lying dead for long enough, they will
// be forced to respawn. Auto-respawn timer must be less than the auto-raise timer
// if the auto-raise timer is enabled.
//
// HABD_FORCE_RAISE_TIMER (AUTO-RAISE)
// HABD_NPC_FORCE_RAISE_TIMER (AUTO-RAISE)
// Set this to a value greater than 0.0 to force raise after a certain amount
// of time has lapsed after death. If players remain lying dead or respawned
// for long enough, they will be forced raised. Autorepawn timer must be
// less than the autoraise timer if the autoraise timer is enabled.
//
// HABD_SOLO_FORCE_RAISE_TIMER (AUTO-RAISE FOR SOLO ONLY
// Set this to a value greater than 0.0 to force raise solo players after a
// certain amount of time has lapsed after death. If the player remain lying
// dead or respawned for long enough, they will be forced to respawn.
//
// HABD_FORCE_RAISE_USES_SCROLLS
// Set this value to TRUE to have force raise consume scrolls. If the player or
// henchmen does not possess any standard raise / rez scrolls then they will not
// be force raised. Note: this will keep raise / rez scrolls from being
// dropped on player death.

// PERSISTENCE SETTINGS
//
// HADB_DB_PERSISTENT
// If set to FALSE, persistent data won't be stored. If you are making a single
// player module, the persistent data won't be stored anyways because the
// OnClientLeave event shuts down the module before it writes to the database.
//
// HABD_DB_NAME
// The name of the database to store the persistent information. If you leave it
// with the default value then the same DB will be used for all modules you run.
// If you want to use different databases for different modules then change the
// name.

// PENALTY SETTINGS
//
// Set values for the respawn / raise / rez penalties.
// The value is a percentage of the total XP to get to the next level or
// the total GP coinage the player possesses. Set a value of 0 if you do not
// want a penalty. Set a value of 100 if you want the player to lose a level or
// to lose all of their GPs.
// If HABD_DROP_GOLD is set to TRUE, then the gold penalties won't do anything
// because gold is dropped before the penalties are applied.
//
// HABD_RESPAWN_*_LOSS
// Penalty for respawning.
//
// HABD_RAISE_*_LOSS
// Penalty for being raised from the dead.
//
// HABD_REZ_*_LOSS
// Penalty for being resurrected.
//
// HABD_NO_LEVEL_LOSS_FROM_XP_PENALTY
// Set this to FALSE to allow XP penalty to cause level loss. If set to TRUE
// then the penalties can cause a player to lose a level.
//
// HABD_MAX_GP_LOSS_FROM_GP_PENALTY
// Set this to a value greater than 0 to set a maximum GP loss. Regardless of
// the percentage penalty they will will only lose a maximum of that amount.

// ITEM DROP ON DEATH SETTINGS
//
// Set these constants to 1 if you would like to drop specific things at
// time of death. Set the constant to 2 if you would like to have the dropped item destroyed.
// Plot items are NEVER dropped or destroyed. The is an order of prescendence to the
// operations.
//
// Dropped items are NOT automatically repossessed when the player returns
// to life. This is to reduce lag. The placeable that stores the dropped items
// with automatically notify the player if it still contains items and
// self-destructs when it is empty of items.
//
// HABD_DROP_GOLD
// Drop or destroy all gold the player possesses. This happens before any penalties are
// applied, so the GP penalties will not do anything if this is enabled.
//
// HABD_DROP_WEAPON_SHIELD
// Drop or destroy the items equipped in the left and right hand slots.
//
// HABD_DROP_RANDOM_EQUIPPED
// Drop or destroy a random item from the players inventory on death.
//
// HABD_DROP_MOST_EXPENSIVE_EQUIPPED
// Drop or destroy the most expensive item the player has.
//
// HABD_DROP_EQUIPPED
// Drop or destroy all equipped items (including left and right hand slots).
// This setting overrides HABD_DROP_WEAPON_SHIELD.
//
// HABD_DROP_RAISE_REZ
// Drop or destroy any Raise Dead or Resurrection scrolls in the backpack.
//
// HABD_DROP_RANDOM_BACKPACK
// Drop or destroy a random item from the players inventory on death.
//
// HABD_DROP_MOST_EXPENSIVE_BACKPACK
// Drop or destroy the most expensive item the player has.
//
// HABD_DROP_BACKPACK
// Drop or destroy any items in the backpack (including Raise Dead / Resurrection)
// This setting overrides HABD_DROP_RAISE_REZ.
//
// 0 - off
// 1 - drop
// 2 - destroy

// RESPAWN SETTINGS:
//
// HABD_RESPAWN_SCRIPT
// This is the script called when respawn is forced. It should be the same
// script as in your module OnPlayerRespawn script. Change this value if you
// want to use the auto-respawn feature with a different respawn system.
//
// HABD_RESPAWN_ALLOWED
// Set this to FALSE to turn off the death GUI. Players will lie there dead
// until someone raises them.
//
// HABD_INSTANT_RESPAWN_ALLOWED
// Set this to FALSE to turn off the respawn option in death GUI (if the death
// GUI is enabled).
//
// HABD_HENCHMEN_GHOST_RESPAWN
// Set this to TRUE to allow henchmen to respawn as ghosts the same way players
// do. If set to FALSE, it will perform the default henchmen death code of
// whatever henchmen AI you are using.

// USER DEFINED FUNCTIONS:
// Modify these following functions to add additional status penalties, hooks
// into other systems, or whatever you want. They will be called on the Bleed,
// Respawn, Raise and Resurrection events. IMPORTANT: Do not give CON penalties
// on any events which would have the player at 1 HP (bleeding or raise) because
// you will just make them start bleeding again if their CON goes to a negative
// value.
//
// HABD_USERDEFINED_*_DESC
// If these strings have a value, then the information will be sent to the
// player when the event happens. This description will also be displayed in the
// death rulebook.
//
// HABDUserDefinedBleed() - Called after a player starts bleeding.
// HABDUserDefinedRespawn() - Called after a player respawns with the HABD
//                            respawn system. Not called with other respawn systems.
// HABDUserDefinedRaise() - Called when the Raise Dead spell is cast on a dead
//                          or respawned player.
// HABDUserDefinedResurrection() - Called when the Resurrection spell is cast on
//                                 a dead or respawned player.

Select All Text | View Code in separate window

Format

Module and Code

Type

Type - Other

Includes

None

Description

CAVEAT

This is a (highly polished) beta release. The intention is to release the full version in late September 2003. Please send all bug reports, potential exploits, requests for additional features, and suggestions to [email protected]

We want this to be hands down the best bleeding/death/respawn system out there and we need your input to make that possible.

IMPLEMENTATION NOTES
- 4 scripts, 5 items, 1 placeable. Only NWN content modified is Raise Dead and Resurrection spells.
- It uses DelayCommand events scheduled on the players instead of heartbeats. It only uses CPU cycles when players are bleeding, dying, dead, respawned or entering/leaving the module. This removes the overhead of searching through the player list on the heartbeat.

Read the script box for more information about this script.

Files

Name	Type	Size	Downloads
habd003.ziphabd003.zip Submitted: 08-21-2003 / Last Updated: 09-01-2003	zip	719.18Kb	3075
--

SCORE OUT OF 10

9.83
31 votes
View Stats
Cast Your Vote!

AWARDS

PORTFOLIO

Add this entry to your portfolio so you can track it

Manage your existing portfolios or create a new one.

SCREENS

You Must Be Logged In to Participate.

Comments (117):

1 2 3 4 Next>

Posted by Styxx42 at 2009-12-21 19:08:51 Voted 10.00 on 11/29/09

Primeval Atom, Yes Sorry didn't realize your question might be to me.
Yes 1.69 compliant as far as My limited knowledge is. We used it pretty much straight out of the box. It didn't work for me because I was working out how to add Wildshape in to it as well.
Love it, and can't play with out it.

Posted by Primeval Atom at 2009-12-03 02:11:42 Voted 10.00 on 12/03/09

So what you are saying is that Vr. Beta 0.03 works with patch 1.69 right out of the box?

That is good news =D

I think HABD is a good option pack death rule system to use in a PW.
_________________________
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into
(")_(") your signature to help him gain world domination.

Rip RPG

Posted by Styxx42 at 2009-11-29 20:07:31 Voted 10.00 on 11/29/09

Got this running and absolutely love it.
Forgot to come back and vote.
Thanks.

Posted by Styxx42 at 2009-07-22 08:40:21 Voted 10.00 on 11/29/09

This sounds great, but I am having issues getting it running. Is anyone else running this out of the Box so to say on 1.69 NWN? I am getting errors about missing right brackets duing step 5 of the install procedure.

Posted by Yanos at 2009-01-02 03:50:41 Voted 10.00 on 01/02/09

A very good job.

Posted by Shai182 at 2008-06-03 09:58:10 Voted 9.75 on 06/03/08

nice work!

Posted by dsabrae at 2008-05-12 11:00:18

Anyone doing support on this package still? The contact info seems to no longer be valid and im trying to get

/*
nw_s0_res.nss

Raise Dead, Resurrection

By: Flaming_Sword
Created: Jun 16, 2006
Modified: Jun 16, 2006

Consolidation of 2 scripts, cleaned up
*/

#include "prc_sp_func"

//Implements the spell impact, put code here
// if called in many places, return TRUE if
// stored charges should be decreased
// eg. touch attack hits
//
// Variables passed may be changed if necessary
int DoSpell(object oCaster, object oTarget, int nCasterLevel, int nEvent)
{
int nSpellID = PRCGetSpellId();
int bRes = (nSpellID == SPELL_RESURRECTION);

if (GetIsObjectValid(oTarget))
{
SignalEvent(oTarget, EventSpellCastAt(OBJECT_SELF, nSpellID, FALSE));
if (GetIsDead(oTarget))
{
SPApplyEffectToObject(DURATION_TYPE_INSTANT, EffectResurrection(), oTarget);
if(bRes) SPApplyEffectToObject(DURATION_TYPE_INSTANT, EffectHeal(GetMaxHitPoints(oTarget) + 10), oTarget);
ApplyEffectAtLocation(DURATION_TYPE_INSTANT, EffectVisualEffect(VFX_IMP_RAISE_DEAD), GetLocation(oTarget));
ExecuteScript(bRes ? "prc_pw_res" : "prc_pw_raisedead", oCaster);
if(GetPRCSwitch(PRC_PW_DEATH_TRACKING) && GetIsPC(oTarget))
SetPersistantLocalInt(oTarget, "persist_dead", FALSE);
}
else
{
if (GetObjectType(oTarget) == OBJECT_TYPE_PLACEABLE)
{
int nStrRef = GetLocalInt(oTarget,"X2_L_RESURRECT_SPELL_MSG_RESREF");
if(nStrRef == 0)
nStrRef = 83861;
if(nStrRef != -1)
FloatingTextStrRefOnCreature(nStrRef,oCaster);
}
}
}
return TRUE; //return TRUE if spell charges should be decremented
}

void main()
{
object oCaster = OBJECT_SELF;
int nCasterLevel = PRCGetCasterLevel(oCaster);
SPSetSchool(GetSpellSchool(PRCGetSpellId()));
if (!X2PreSpellCastCode()) return;
object oTarget = PRCGetSpellTargetObject();
int nEvent = GetLocalInt(oCaster, PRC_SPELL_EVENT); //use bitwise & to extract flags
if(!nEvent) //normal cast
{
if(GetLocalInt(oCaster, PRC_SPELL_HOLD) && oCaster == oTarget)
{ //holding the charge, casting spell on self
SetLocalSpellVariables(oCaster, 1); //change 1 to number of charges
return;
}
DoSpell(oCaster, oTarget, nCasterLevel, nEvent);
}
else
{
if(nEvent & PRC_SPELL_EVENT_ATTACK)
{
if(DoSpell(oCaster, oTarget, nCasterLevel, nEvent))
DecrementSpellCharges(oCaster);
}
}
SPSetSchool();
}

to work with steps 9 and 10 of installation using the execute script call in the above code.

Posted by Samji83 at 2008-05-10 12:46:17 Voted 9.50 on 05/10/08

Seems like a bug:

Once in a while (it seems randomly O_o) some characters lose all their items on login .......this is very frustrating, I've checked all the scripts 1000 times and could not understand where the prob is.

Maybe some of you have gone trhough this?

Thx, and great job guys

Sam

Posted by Gonzo_og at 2008-03-22 09:06:50 Voted 10.00 on 03/22/08

Good stuff.
_________________________
stuff

Posted by Racerblue at 2008-03-22 07:43:00 Voted 10.00 on 03/22/08

Used it. Loved it.

Posted by kirbyef at 2008-03-09 05:43:39 Voted 10.00 on 03/09/08

I classic handy set of scripts indeed.

Posted by grimjim at 2008-03-01 14:44:17

Actually, I am a hemophiliac, and we don't always bleed to death. Lovely title.
_________________________
Jim Grimsley

Posted by Ondaderthad at 2008-02-16 20:36:56 Voted 10.00 on 02/16/08

I am using this system as part of the Vuldrick Base Module
_________________________
The Best PW system is getting even better.
PLATEMAIL Tech Preview

Posted by Shargast at 2007-12-30 02:55:23 Voted 10.00 on 12/30/07

Good system! It's being used in alot of PW's including the three that I've built!

Great Work
Shargast
_________________________
Realms of Shargast V1-V5ab, LOTR V15, The Undeath Clave & Faithful of Aerth

Posted by AJGoo at 2007-09-29 16:01:36 Voted 9.50 on 09/29/07

Am using it.
_________________________
The dead only know one thing, it is better to alive

Posted by Eat2surf at 2007-09-29 11:53:45 Voted 10.00 on 09/29/07

thanks! sorry for the long-time lack of voting!
_________________________
Enjoy!

Here's a Link to The City of Torencia prefab.
Check out this Link to my Jack and the Beanstalk module... Do you have what it takes to be Jack?!
oh.. and my entry in the NWN2 area contest.. Treasure Island! : Link

Posted by eliandi at 2007-04-01 23:18:47 Voted 9.50 on 04/01/07

very useful package

Posted by MrT at 2007-02-19 23:49:25 Voted 10.00 on 02/19/07

Utterly superb!
This highly customizable script is exactly what I required.
A huge thank you to the creator/s.
"When you're dead.....you're dead!"

Posted by Carlo at 2006-10-21 16:22:41 Voted 9.50 on 10/21/06

Also thought I'd voted for this a long time ago. Easily customizable, powerful system that works well in both DM'd and non-DM'd games. I've had a version installed in my campaign module now for over two years.

Posted by Arkangyl at 2006-10-15 11:49:56 Voted 10.00 on 10/15/06

Eeek! I thought I had voted for this a loooong time ago. My apologies. I used this system quite happily in my DMed campaign (it is still there heh). I think it is certainly one of the better systems for this though there are other excellent ones too, but it did the trick for me! ^_- Thanks guys.

Posted by Shioni at 2006-09-23 21:07:32 Voted 10.00 on 09/23/06

I like this system, but I wish I knew how to tweak it so that when you hit 0 life it stops the damage. Other wise the script never fires because of over kill damage hot taking 20 damage with 2 hp left

Posted by Rosietreats at 2006-07-09 07:36:06 Voted 10.00 on 07/09/06

I have helped others incorporate this system into exsisting modules, and have found it to be a very good system indeed!
Very nice work!

Posted by jon ( 62.156.xxx.xxx ) at 2006-03-30 07:43:25

Great. Thanks!

Posted by Venture at 2005-12-11 17:07:41 Voted 10.00 on 12/11/05

I've used this for about 2 and a half years in my campaign, and it works perfectly. Incredibily customizable, and easy even for a scripting idiot like me.
_________________________
NWN Campaigns - the NWN/NWN2 Campaign Database
Naeldor Weekly Campaign

Posted by terremer ( 194.2.xxx.xxx ) at 2005-11-14 07:00:37

Great and robust system, it done all I need.

Posted by Ythaniel ( 69.221.xxx.xxx ) at 2005-11-12 09:04:30

Can we please remove this version of the script from the Vault.

Posted by Lorimim at 2005-10-09 00:29:08 Voted 10.00 on 10/09/05

Every other pw is using this. Why isn't it in the Hall already?

Posted by hogdraif ( 201.8.xxx.xxx ) at 2005-05-07 05:00:01

qual eh a senha so nwn??????
eu perdi a minha e nao cincigo jogar!!

Posted by lv8pv ( 80.213.xxx.xxx ) at 2004-10-19 07:26:00

I implemented this system on an exsisting persistent world. I followed the read me and had no problem what so ever. Everything worked at first try.

Good system.

Posted by IntrepidCW at 2004-10-17 06:27:59 Voted 10.00 on 10/17/04

1 2 3 4 Next>

You must be Logged In to post comments in this section.