Skins: |

NWN SCRIPTS

Title

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

Author

Demetrious,OldManWhistler,IntrepidCW

Submitted / Updated

10-17-2004 / 11-22-2006

Category

Rulesets

Expansions

Works on all versions

View Code

Henchmen Always Bleed to Death



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


VERSION 1.3
- Robust configurable player / henchman bleed / death / respawn system for SP / 
MP / DMed / Non-DMed 
by Demetrious, OldManWhistler and IntrepidCW 
 
Old 0.03 beta version: 
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 soon. 

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



Noobs read there:
This System is modified via constants, after modyfind the constants ... :
Always recompile your module after modifying habd_include because it is an include file.
#1: Select "Build" from the toolset menu and then choose "Build Module".
#2: Click the "Advanced Controls" box to bring up the advanced options.
#3: Make sure that the only boxes that are selected are "Compile" and "Scripts".
#4: Click the "Build" button.
#5: Remember to always make sure you are using the options you want to use when running "Build Module"!
 


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), PHB Movement Skills (Balance, Climb, Jump,
Swim, Escape Artist), and Player Character Auto Save. 

The main intent of this system is that players never instantly die 
(configurable). 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 (configurable 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 or solo games 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. 

Finally, the system can be configured in a short time to fit your needs. Respawned PCs can be moved to a predefined waypoint, you can also use the bindstone system implemented. HPs can be fully managed by the HABD. Finally you have some tools to use some sort of 'Hell/Heaven' areas in your module. 

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.
- Giantkin for help with betatesting. 
-OldManWhistler, for doing the main hard work.

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 
IntrepidCW Portfolio 
http://nwvault.ign.com/portfolios/data/1081928501.shtml 

FEATURES

IMPLEMENTATION NOTES
- 5scripts, 3 player items, 2 DM items, 1 placeable. Some optional premade 
objects (2NPC, 3 Conversations, 1 Placeable, 1 Waypoint, 1 Trigger).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 ofevery 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 include an optional kind of bind stone system. It can be also used to bring persistence to controled locations. 
- 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 are advanced bandages that can be sold, are not free, and could be placed at stores if you wish). 
- 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 (chance is configurable). 
- If going from living to -6 or lower you will be capped at -5 to give you a good chance to be saved (configurable). 
- If going from living to dead you will be set to -6 to -9 HP instead of dying (configurable). 
- You can declare some areas where death is hard: Mosters will be able to kill youon a single hit, and you will start bleeding at appropiate number (no -5 limit). 
- 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 1 second). 
- 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 2). The DM Force Instant Death widget can bypass this setting. 

DEATH:
- Now you can specify areas (by Resref) where death and bleeding is imposible. - 
Now you can specify areas (by Resref) where Instant Death due to a single hit is 
allowed.- 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. - Permadeath for 
PWs is supported (requires you to script what leads the player to permadeath, 
see the custom permadeath function at script "habd_onpcrespawn";
furthermore you must specify a waypoint in the options there) - 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. - Respawned PCs can be moved to a waypoint or to a BindStone. 



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.
// First import habd_1.erf

// #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 (before the Main statement) 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: Modify the spells Resurection and Raise Importing an    erf
   // If you are using patch 1.62 or up, import the habd_nw_1_64.erf file to replace
   // your nw_s0_raisdead and nw_s0_resserec scripts.
   //
   // For older versions try Importing the habd_nw_1_31.erf file to replace your
   // nw_s0_raisdead and nw_s0_resserec scripts with SoU 1.31 compliant ones.

// If you have custom code at these spells, then you need to merge manually:
// (if your code has a return; sentence somewhere, then you should think about
// where you can put the HABDCode)

// #9 manual: Open nw_s0_raisdead. Copy this at the end of the script (before
the last } ):

    // HABD CODE START
    HABDRaiseDeadSpell(oTarget);
    // HABD CODE END


// #10 manual: Open nw_s0_resserec. Copy this at the end of the script (before
the last } ):

    // HABD CODE START
    HABDResurrectionSpell(oTarget);
    // 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.
// IMPORTANT: Recompile your module scripts!

// #XX: ONLY IF YOU USE AN OLD PATCH. If you are using a patch below 1.64 ...
// Read the FAQ for detailed info, and make sure you change the constants in
// the MISC section (always set HABD_PATCH_PRE1_64 to TRUE)


// #XXX: IMPORTANT, SINGLE PLAYER MODS. If you are using HABD in a module that
// is going to use the SaveGame/LoadGame NWN feature, you must never load info
// from DataBase (and you shouldnt save).
// Set HADB_DB_PERSISTENT to FALSE, HABD_EXPORTCHAR to FALSE (other persistency
// configs could be better deactivated)
// I counsel to delete calls to HABD at OnClientEnter event script, OnClientLeave
// (will not fire anyway).
// If your module must work both as multiplayer and singleplayer, let everything
// as multiplay, but try setting HABD_SPGAMES_NO_OCE to TRUE.


// Install Notes: 
   // 1. You can get problems if you are using another script to track hitpoints when these HP are <=0.
   // 	I encourage you to disable these scripts, and enable the HABD HP Tracking, setting TRUE the
   //	configuration constant HABD_MANAGE_HITPOINTS.
   // 2. Read the FAQ for more.

See PDF file for additional information.



CONFIGURATION SETTINGS

// MISC SETTINGS
//
// HABD_PATCH_PRE1_64
// If you are using a NWN patch below 1.64, mark there as TRUE, otherwise the code could
// suffer an exploit when PCs leave the game possessing a familiar (altough to
// solve the NWN Bug the script is less robust). Default FALSE.
//
// HABD_LEVELUPBLEED_EXPLOIT_KILLS
// There is a exploit, when a PC levels up when bleeding. He is not stabilized
// properly, and he does not die. If this constant is TRUE the PC is killed and
// the DMs alerted. If FALSE it will simply alert DMs and print the note in log.
//
// HABD_FAMILIAR_EXPLOIT
// There is a exploit, PCs can possess their familiar when dying :\, it tends
// to ruin lost dying scripts and provoke strange behaivours. If set to 0, the
// familiar of a PC will always die when starting to bleed. If set to 1, the
// familiar will not die then, he will be able to figth, but if the PC possess
// the familiar it will die and the PC will keep bleeding.
//
// HABD_ITEMSONENTER
// Configure what items are given to players and DMs when entering the module.
// It is a three digit number. Each number is an item, 0 = dont' give the item,
// 1 = give the item.
// First number is the DeathToken, second the bandages, third the HABDRulesItem.
// E.g. "010" = only give the Bandages on enter
//
// HABD_PATCH_PRECURSEDITEMS
// If you are using a NWN patch that does not support Cursed Items (Undroppable)
// , turn it to TRUE, you will need also to do some small changes (read the FAQ)
//
// HABD_SPELL_TRACKING
// HABD can take care of Spell/feat tracking, making sure that the exploit that
// restores feat/spell uses will not happen. This feature will work perfectly
// if you are running NWN patch 1.65 or better. Old patches have Bioware bugs
// that need very complicated workarounds.
// 0: No spell tracking.
// 1: (Recomended) Spell tracking saving at OnClientLeave event. Uses less
//  access to database, but is not crash - proof (do you really want to make it
//  crash proof?).
// 2: Spell tracking will save everytime HABD saves any other data, which can
//  be very often depending or other settings, can be crash-proof.
//
// HABD_USERLANGUAGE
// Default available languages, it translates most messages from english.
// Log messages, some Debug mesages and The Player Rules are not translated.
// 0: English, 1: Spanish.


// BLEEDING SETTINGS
//
// HABD_ALLOW_INSTANT_DEATH
// Default False. If TRUE, PCs can die when they go to alive to -10 or less hps in
// a single hit. HABD_NO_DEATH_BEFORE_LEVEL takes preference, soy low level chars
// will be still safe if you wish.
//
// HABD_KILLING_HIT. You can specify a negative number, if the PC descends to
// this number of hps or lower he suffers Instant Death (even if Instant Death
// is deactivated), in this way you can have the normal bleeding but instant
// death happens with very violent blows. If set as 0 it is off, you should
// configure it at -11 or lower if you want to use this feature.
//
// HABD_BLEEDING_START_LIMIT
// If going from living to -6 or lower you will be capped at HABD_BLEEDING_START_LIMIT
// (default -5) to give you a good chance to be saved. Set from -1 to -10.
// Set up to -10 to fully disable the cap (but dont allow instant death).
//
// HABD_PLAY_BLEED_VOICE
// Default: TRUE. If TRUE bleeding characters play a random apropiate voice. If
// FALSE no Voice is played. You can also specify a number from 2 to 100, that
// indicates a percentage chance to play the voices.
//
// HABD_STABILIZATION_DICE
// Determines the dice to be used for stabilization checks. Default 10 = d10.
// 20 = d20, 100 = d100, etc... Dont use a negative or very low value.
//
// HABD_GLOBAL_STABILIZATION_NUMBER
// A d10 (depending of HABD_STABILIZATION_DICE) is rolled each bleeding round,
// if the result is equal or higher than the HABD_GLOBAL_STABILIZATION_NUMBER
// (default 10 for D&D rules), the player  self-stabilizes. Change as you need,
// it must be a number between 0 and 10. Smaller, easier to get stabilized.
//
// HABD_SOLO_STABILIZATION_NUMBER
// As HABD_GLOBAL_STABILIZATION_NUMBER, but it is used (instead of the GLOBAL)
// at SinglePlayer Games, or if there are not more PCs at the server. I suggest
// to make it a bit lesser than Global in PWs.
//
// HABD_NOINPARTY_FAST_BLEED
// If set to TRUE, then players without a party in a server WITH MORE PCs
// (not DMs) playing go through the bleeding stage VERY fast (1 second). They
// will still have the stabilization chances. It does not check if there are PCs
// near. You can specify the time in seconds using a number e.g 2, 3, 4 instead
// of TRUE
//
// HABD_SOLO_FAST_BLEED
// If set to TRUE, then players in a Single player game or alone in the server
// will 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. It does not check if there are PCs
// near. You can specify the time in seconds using a number e.g 2, 3, 4 instead
// of TRUE. Default: TRUE.
//
// 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 NWN regeneration is VERY Fast,
// 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. Also search HABD_POST_BLEED_CONCEAL_DUR
//
// 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.
//
// HABD_HEAL_SKILL_DC
// DC for Heal Skill when trying to stabilize a PC using the bandages.Default:15
//
// HABD_HEALMINOR_SKILL_DC
// Once failed the Heal check for stabilization, you can get a result higher
// than HABD_HEALMINOR_SKILL_DC, then the PC will be healed up to -1 HP, but
// will be still bleeding.  0 = Disabled.
//
// HABD_ONENTER_INSTANTBLEED
// Default = TRUE. If True, when a bleeding player comes from persistence or if
// has been loged out a long time, bleeding checks are made instantaneous. It
// avoids multiplayer exploits. Set to False if you dont want it.
//
// HABD_ONENTER_INSTANTBLEED_TIME
// On use only if HABD_ONENTER_INSTANTBLEED is TRUE. It enables this feature when
// login out-in a long time. Set to 0.0 and Instant bleed will only happen
// when coming from persistance. NOTE: It is the time per hp left to die, e.g.
// a PC leaving wat -5 hps, can be out -5*15 = 75 seconds. (with deafault 15.0)
//
// HABD_ALONEINAREA_COUPDEGRACE
// If toggled on, a PC bleeding without another PCs in the area, will suffer
// a simulated coup de grace (or aditional attack) from a nearby monster, he
// will die instantly and receive a message. To turn off: FALSE (default)
// To set up, use a number between 1 and 10, it is the chance (using a d10 dice)
// to receive the coup de grace (it happens once when he starts bleeding),
// 10 = 100% .To specify that good alignment creatures will never perform coup
// de grace, use 101 to 110.
// We dont allow D&D fortitude saving throws, because any damage is still applied,
// and it usually drops you to -10.
// Note, Monsters will deal the extra hit even at distance, but within a max
// distance of 50 m
//
// HABD_DELAY_TOHEAL
// If 0.0, when the PC stabilizes it heals to 1 HP in a second. You can configure
// it to take some time. This number is the number of seconds that will take
// each hitpoint to be healed. Don't use more than some seconds, when the player
// logs-in he will be instantly healed.
//
// HABD_HENCHMEN_BLEED
// (default TRUE) If TRUE, the system applies the bleeding rules to the Henchmen,
// if FALSE it will NOT use the HABD Rules (Notes: ExecuteScript can help you to
// mix ondying scripts). If 2 = It will instantly kill bleeding henchmen ;)
// If 3, It will allow instant kill of Henchmen only.
//
// HABD_HENCHMEN_DEATH
// (default TRUE) If TRUE, the system applies the death rules to the Henchmen,
// if FALSE it will NOT use the HABD Rules (Notes: ExecuteScript can help you to
// mix ondeath scripts).

// 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_RESTART_FORCE_RAISE_TIMER
// If you set it to a value higher than 0.0, when the server restarts everyone
// that logins respawned will be autoraised in this time (if an autoraise timer
// stored in the DataBase was not lesser). If your PC corpse items can be raised
// dont set it to a low value (at least 10 seconds).
//
// 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.
//
// HABD_AUTOTIMERS_UPDATE
// When you log out/in any respawn/raise timer is reset... it is not usefull if
// you set long autoraise/respawn timers. If the constant is a number >0 it means
// that we Update the timers each HABD_AUTOTIMERS_UPDATE seconds. Default: 10.
// It should be less than any timer set, and always more than 0. If you set to
// 0 NOtimer will work.
//
// HABD_RESPAWN_IS_RAISE
// If TRUE, when you respawn, you are instantly raised.

// PERSISTENCE SETTINGS
//
// Note: If you want to change the way to use the DataBase (to implement NWNX eg)
// modify the functions HABDSaveStringToDB, HABDLoadStringFromDB,
// HABDSaveBSLocationToDB, HABDLoadBSLocationFromDB.
//
// HADB_DB_PERSISTENT
// If set to FALSE, persistent data won't be stored. If you are making a single
// player module, some persistent data won't be stored anyways because the
// OnClientLeave event shuts down the module before it writes to the database.
// HOWEVER persistent data can be stored even if OnClientLeave is not fired,
// depending of other habd configurations.
//
// 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.
//
// HABD_ONENTER_HOSTILEREPUTATION
// Default TRUE, when entering the PC gets reputation 0 (war) with the hostile
// faction. If your use of the hostile faction gets problems from this. Turn to
// FALSE. Or manage de factions with your own code.
//
// HABD_MANAGE_HITPOINTS
// Provides full management (optional, you never know) of hps. If you use it,
// disable any other hp manager script/function.. If you turn it false, only
// critical HP info will be saved and restored... however you could have some
// problems when using with another HP management script.
//
// HABD_BINDSTONE_PERSISTENT
// It will save the Bindstone locations to the DB. It will be very usefull if
// you are using any kind of DM location manager (or using this Bindstone system
// to manage locations). It does NOT restore locations. Read the Respawn options
// also. Really it saves locs to DB and loads them after server restart, for
// respawn purposes mainly. Furthermore, when doing so it will also save all the
// HABD info (hps, state, etc..).
//
// HABD_BINDSTONE_MANAGE_LOCATIONS
// If TRUE, when the PC logsin after a server restart, he will jump to last
// bindstone triggered. It is a limited and optional way to make locations
// persistent. Usefull if you only want to make the players appear in safe or
// controlled places.
//
// HABD_EXPORTCHAR
// If TRUE, every time we save the HABD info to the DB, the player is also
// exported. It improves the system robustness against server crashes. In Single
// Player Games it will be better as FALSE.
//
// HABD_SMART_SAVETODB
// If set to TRUE, information will be saved to DB more often, not only at
// onclientleave event (or bindstone triggering if used). We'll save info to
// db when the PC suffers a state change: bleeding, from bleeding to alive,
// death, respawn, raising... It makes HABD more robust against server crashes.
//
// HABD_SPGAMES_NO_OCE
// If 1, when OnClientEnter function is fired, it will detect if we are
// playing a Offline game using GetPCPublicCDKey()NWN function, if we are OffLine
// HABD OnClientEnter tasks are skipped, avoiding SinglePlayer bugs when loading
// info from DB when we load a SavedGame. Default = FALSE. To activate = 1 .
// Note: LAN games are online games.

// 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.
//
// HABD_NO_0PX_FROM_PENALTY
// If set to TRUE, a PC will be lowered to 1px instead of 0px (if it happens),
// it is usefull if you use the fact of having 0 px to identify new players.

// 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.
//
// HABD_DROP_PLOT_ITEMS
// Allows you to drop or destroy Plot Items (altough it could be a bad idea).
// 0-Not drop plot, 1-drop, 2-destroy OR drop.
//
// HABD_DROP_ALLOWED_LOOTERS
// Determines who can loot the death bag. DMs can always loot. 0-Only the death
// PC, 1-The Death PC and the people in his Party, 2-Everybody
//
// 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.
//
// HABD_RESPAWNPOINT
// The player will respawn at the WAYPOINT of the specified TAG. Default = "",
// it means no movement, will respawn at the death point, if you place the
// waypoint and introduce the Tag, the PC will jump to the waypoint when respawn.
// Usefull to make Purgatoriums, hells etc...if you want to make a difference
// based on alignments, you should use an intermediate area. Note that respawned
// PCs are not alive until resurrected.
// It is ignored when the BindStone system is working.
//
// HABD_JUMPTORESPAWNPOINT_FIRST_ONENTER
// It specifies, that, if you come from a server restart or crash (not a simple
// logout/login) as respawned, you must be mjoved to the respawnPoint or not.
// Disable it if you use a fine alternative location manager. DEfault: TRUE.
//
// HABD_GHOST_EFFECTS_ON
// It turns on (TRUE) off (FALSE) some ghost visual and mechanic effects: PlotFag,
// , sanctuary, and VFX. Turn off has sense if you transport the respawned PC to
// a 'hell'. Notes: they are still ignored by hostiles; they can be still
// selected to follow a PC, but they will not jump to another area in this way
// (exploit safe). Default TRUE.
//
// HABD_GHOST_COMMANDABLE
// It makes the player ghost Uncommandable (cannot be moved by the player) (false)
// or commandable (true). Default FALSE.
//
// HABD_HENCHMEN_NO_RAISE
// If FALSE, Henchmen can be raised using the HABD Rules. Otherwise they dont.
// (usefull if you are using another Henchmen system)
//
// HABD_PERMADEATH_LOCATION
// A PERMADEATH (permanent death) player will respawn at the WAYPOINT of the
// specified TAG. Default = "", it means no movement, will respawn at the
// death point, if you place the waypoint and introduce the Tag, the PC will
// jump to the waypoint when Permadeath takes place.
// To configure the permadeath, see the permadeath custom function 
// HABDUserDefinedPermadeath in the script habd_onpcrespawn
//
// HABD_BINDSTONE_TAG
// Tag of the objects involved in the Bindstone feature (NPCs, placeables,
// triggers and Waypoints). Better dont change this if you want to use the
// premade objects that come with the script.
//
// HABD_AUTORAISE_WAYPOINT
// If you introduce a waypoint tag, a PC that raises due to the AutoRespawn
// feature, will be moved to the waypoint. Default: "" (no jumping)
//
// HABD_RESPAWN_PCDEADCLON
// (Default TRUE) If set to TRUE, a beatifull and dead clon of the PC will be
// created at the location of the PC when he pressed the respawn button. The
// clon is not selectable or destroyable. Using Tabulator players can read the
// clon name (pc name).
// The Clon will only appear if there is a death bag with drop items or a corpse
// item inside, however, and will be destroyed when the death bag is destroyed.
// If you set if to TRUE I counsel you to change the HABD Death Bag appearance
// to an invisible object, both things will result in an cool visual effect.
// If you are using an Old Patch this function will not work, because the
// the function CopyObject could not work (in this case set to FALSE and delete
// code displaying errors).
//
// HABD_DROP_CORPSE_ITEM
// If set to TRUE, a Corpse item will be dropped to the loot bag (if no loot
// bag it will try to create a new one). The corpse can be raised by a NPC.
//
// HABD_RESTART_DELETE_CORPSES
// If set to TRUE (Recomended, using HABD_RESTART_FORCE_RAISE_TIMER at the same
// time). When the server resets, all the corpse items found in PCs inventories
// that come from persistence will be deleted.
//
// HABD_RAISE_LOGOUT_PLAYERS
// If TRUE, the corpse items cab be used to raise PCs even when they are not
// logged-in in the server! If FALSE, they can only be raised when logged in.
//
// HABD_BINDSTONE_USEWHENRESPAWNED
// If TRUE, the locations saved by BindStones will be used when the PC respawns
// and he will be moved to the last location binded. Also see the Persistence
// options.
//
// HABD_BINDSTONE_RESPAWNPENALTY
// If TRUE, when a PC respawns, it will use the penalties stored into the
// bindstone waypoint he is transported to. HABD_BINDSTONE_USEWHENRESPAWNED must
// be TRUE also.
// The waypoint will store these % penalties in two integer variables:
// HABD_BINDSTONEWayPoint_XPPENALTY and HABD_BINDSTONEWayPoint_GPPENALTY
// You must edit the variables in the toolset (rigth click in the WP, Variables..)
// If 0: Use default penalties. If <0: Penalty 0%. >0 A % Penalty, e.g. 20 is 20%
// The objects that come with the .erf should have these variables defined, just
// change them. It is an HABD 0.9 feature, old users should replace their waypoints.
//
// HABD_DINAMICRESPAWN1
// It is a Special feature that allows to dinamically change the Respawn
// configuration, when the PC is carrying some special items. The Code provides
// a basic support and a sample system, no Items. To know more details about how
// customizing and using it, read the FAQ.
// If this constant is set to 0, this feature will not work; when set to 1, will
// work, but special items will not be deleted from the PC when respawning; if
// 2, a special item will be deleted when respawning.
//
// HABD_HARDCORE_RESPAWN1
// It is a Special feature that will make harder the configured respawn settings
// when a particular condition is met. When the condition is met, the player
// cannot benefit from autoraising or rainsing when respawning, and must be
// raised by another PC or DM (if enabled).
// IT IS NOT PERMADEATH (for Permadeath read HABD_PERMADEATH_LOCATION info).
// The condition must be scripted at function HABDHardCoreRespawn in
// "habd_include", altough it uses a preset one if not customized. Read the FAQ
// for more info. You must first set this constant to TRUE (default FALSE = off).


// SAFE AREAS SETTINGS:
// HABD_SAFEAREA_RESREF_*
// It allows you to specify some areas were you can't death or bleed.
// It is intended to help you make 'heavens' and 'hells' for death players.
// There you must specify the RESREFs of the areas.
// You can set up to 10 areas. If you need more, add more constants and modify
// the function HABD_GetIsSafeArea().
// IMPORTANT: Start writing in the first constant, otherwise it will not check
// the following areas.


// HARD AREAS SETTINGS:     (buwahaha)
// HABD_HARDAREA_RESREF_*
// If you enable the usual cap and disable Instant Death for all the module,
// maybe you still want to make some areas more frigthening. There you can/
/ specify the ResRefs of the areas that will be Hard (eg use with the villains
// base). In a hard area the bleeding cap is -9, and Instant Death is allowed.
// You can set up to 20 areas. If you need more, add more constants and modify
// the function HABD_GetIsHardArea(). Note: It will kill even PCs of low level
// that shouldnt die (HABD_NO_DEATH_BEFORE_LEVEL is ignored)
// IMPORTANT: Start writing in the first constant, otherwise it will not check
// the following areas.


// 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 complete and highly polished beta version, you should be able to configure your death rules as you want. 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.
Ahora con traduccion al castellano.

IMPLEMENTATION NOTES
- 5 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
HABD_1_32.zipHABD_1_32.zip Submitted: 10-17-2004 / Last Updated: 07-05-2006	zip	1.1Mb	2894
Package contents

SCORE OUT OF 10

9.84
30 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 (30):

1 2 3

Posted by puket at on06/27/06

I noticed the same problem.......RaglinMason has written with the onclientleave.

Posted by Darkvalley at on03/04/07

Great system! The possibilities are awesome.Thanks a lot sharing this with us.

Posted by Rubric at 2007-02-2405:34:50

Thanks Intrepid -- this is a very nice set of scripts. It has more features than I need, but it hasn't been too hard to configure it. Here is my only problem: If I click on the henchman while she is bleeding, she stands up, bows gracefully, and says "Can I help you?" Then she falls back down and continues bleeding. So, I'm thinking, wow that is one dedicated henchman -- she's still all helpful even though she is bleeding to death! Still, I would like to disable that if possible. I think I remember reading somewhere that it's not possible, but I thought it was worth asking. Also, I haven't yet figured out how to get the henchman to do a standard NWN-style respawn back to the temple. She just disappears when she dies. I think I can probably figure this one out eventually, so my main question is with the overly helpful bleeders. I'm using 69meh's hench system, if it matters.

Posted by RaglinMason at on10/21/06

Doh! Doesn't like those angle brackets (the rest of my post disappeared)! Anyway, in "english" the code looks like it says "if current hitpoints are less than or equal to zero, use the shadow variable instead ELSE use the shadow variable anyway"!? I think that the ELSE clause in the case of the HABDSetDBOnClientLeave method probably should be Setting the local int rather than getting it, and in the case of HABDSetDBString probably should just be using current hitpoints rather than the shadow variable when writing the DB string out. It seems to make sense to me anyway, unless there's another method in between somewhere that is guaranteeing the shadow variables are always up to date. I've seen other posts with code pasted in, how do you do that, do you actually have to do the "ampersand-lt-semicolon" type stuff?

Posted by RaglinMason at on10/21/06

Actually I think I may have found it. The following occurs in both the HABDSetDBString function and HABDSetDBOnClientLeave: int iHP = 0; if (HABD_MANAGE_HITPOINTS == TRUE) { iHP = GetCurrentHitPoints(GetExitingObject()); if (iHP

Posted by IntrepidCW at 04:22:13 Voted10.00

Raglin it looks like you have some problem with the ClientExit event. I didnt tested the item-bindstone, but may work giant.

Posted by RaglinMason at on10/21/06

I have found this system to work great for the most part, and couldn't do with out it. That being said, I've had some trouble with players who've been damaged in a playing session and who healed or rested prior to logging out having damage applied when they come back in next time. This is multiplayer on a standalone server with servervault only. I've been wondering if there are problems with the client enter/exit scripts and their firing order, but haven't been able to track it down. Has anyone else seen this?

Posted by giantkin at on10/18/06

hi Intrepid! ;) the Permadeath stuff... i had ya include while ago... under the Hardcore stuff. Bindstone... i think on mine, i made a STONE, that had the scripts on it, instead of the trigger/thingy u had. not sure if u ever used it. gk _________________________ GK

Posted by IntrepidCW at 07:41:15 Voted10.00

First, THANKS for everyone who voted and helped with this script to make it reach the Hall of Fame :) ___ cooldaddyo, I think you have done what was needed (you put the bindstone waypoint in the same area where the NPC is, rigth?), i will try to get some spare time and re-test the bind stone by myself.

Posted by Markshire at on07/29/06

Thank for a nice system. A little over complex for our needs but we've adapted quite a few of the functions to fullfil them. Thank you for all the hard work. Greatly appreciated. _________________________ Vault Game World Entry: Markshire Website: www.markshire.com Server: www.markshire.net:5121 NWNWiki: Markshire Vault Submissions: NWN1: Magic Carpet Transitions | Experience and Teamwork System | Portable Persistent Chest System | Nerfed Pulse Drown | Renaming System | Quill of PC Recording NWN2: Climbing System | Explosive Barrels | Quill of PC Recording Fiction: A Missed Adventure | Kurm and the Sewer King's Curse | A Harrowing Story | Loki's Foulest Trick | Rising Force | The Mad Red Titan: One, Two, Three

1 2 3

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

Most recent posts on the MMO General Boards

Analyst: Star Wars: The Old Republic Could...Analyst: Star Wars: The Old Republic Could Sell 3M: more numbers
- last reply by Acao on Aug 15, 2011 06:15 PM

which class will your first character be
- last reply by Blisteringballs on Aug 15, 2011 05:50 PM

New Community Content!
- posted by Vault_News on Aug 15, 2011 05:00 PM

New Community Content!
- posted by Vault_News on Aug 15, 2011 04:00 PM

NWN Idea Database Update
- posted by Vault_News on Aug 15, 2011 03:46 PM

Missing Votes for NWN2 Hall of Fame
- posted by Vault_News on Aug 15, 2011 03:40 PM

Missing Votes for NWN Hall of Fame
- posted by Vault_News on Aug 15, 2011 03:39 PM

Random Questions and game altering suggest...Random Questions and game altering suggestions!!!
- last reply by ArkadyTepes on Aug 15, 2011 03:22 PM

State of the game?
- last reply by LyricOpera on Aug 15, 2011 01:37 PM

Yesterday streaming, now demanding downloa...Yesterday streaming, now demanding download :(
- last reply by Sinane-tk on Aug 15, 2011 10:23 AM

Around The Network:

Neverwinter Nights 2 at IGN

Neverwinter Nights 2 Cheats at IGN

Neverwinter Nights 2 at GameSpy

Neverwinter Nights 2 at GameStats

Neverwinter Vault

Planet Neverwinter

About Us | Advertise | Contact Us | Press | Careers

By continuing past this page, and by your continued use of this site, you agree to be bound by and abide by the User Agreement.
Copyright 1996-2011, IGN Entertainment, Inc. | Support | Privacy Policy | User Agreement | RSS Feeds
IGN’s enterprise databases running Oracle, SQL and MySQL are professionally monitored and managed by Pythian Remote DBA.

NWN2 NWN