Infestation Quests - Revision history

Zelknolf at 03:23, 16 January 2015

2015-01-16T03:23:34Z

Zelknolf at 03:23, 16 January 2015

2015-01-16T03:23:13Z

Zelknolf at 00:46, 30 December 2014

2014-12-30T00:46:20Z

Zelknolf at 22:44, 21 September 2014

2014-09-21T22:44:07Z

Zelknolf at 22:34, 21 September 2014

2014-09-21T22:34:47Z

Zelknolf: starting article on infestations

2014-09-21T22:32:41Z

starting article on infestations

New page

Warning: This article is about a feature which is currently under development. While this information may be used to prepare build for future releases, the ACR must be updated for anything listed to become functional.

Infestation quests are quests which are provided as a generic framework from the ACR. The DM team of a server may specify an area or series of areas as "infested" with some sort of creature, and these creatures will expand and displace the typical group spawns of all of those areas for as long as their numbers sustain.

Infestations are limited in their spread by builder specification, and follow existing area transitions. The DM team may stop an infestation arbitrarily.

==Build Specifications==
If any area or waypoint should not be affected by infestation code, it should have a local int set on it, called ACR_QST_MAX_INFESTATION and set to -1.

If any area of waypoint should have a maximum infestation tier allowed, it should have a local int set on it, called ACR_QST_MAX_INFESTATION and set to the maximum tier. It is important to note that setting every waypoint in an area to a max tier will not alter the state of the area. For example, an area which is set to tier 4 but only contains tier 1 waypoints will only spawn tier 1 infestations, but can be bordered by tier 5 areas, leading to PCs who find the gradient of challenge ratings extremely difficult.

As a recommendation for playability, major roads should have a max infestation tier of 1, and minor roads a max infestation tier of 2.

==Infestation Spread==
Fecundity of infestations is defined at creation and is adjustable. However, it is generally expected that infestations will attempt to spread such that there is at most a one-tier difference in the infestation strength across any given area transition.

If, for example, we had an infestation which grew at a rate of 1/day with a maximum tier of 3...
{| class="wikitable"
|
{| class="wikitable"
|-
! colspan="5" | Day 1:
|-
|~
|~
|0
|~
|~
|-
|~
|0
|1
|0
|0
|-
|~
|0
|0
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 2:
|-
|~
|~
|1
|~
|~
|-
|~
|0
|1
|0
|0
|-
|~
|0
|0
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 3:
|-
|~
|~
|2
|~
|~
|-
|~
|0
|1
|0
|0
|-
|~
|0
|0
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 4:
|-
|~
|~
|2
|~
|~
|-
|~
|1
|1
|0
|0
|-
|~
|0
|0
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 5:
|-
|~
|~
|2
|~
|~
|-
|~
|1
|1
|1
|0
|-
|~
|0
|0
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|}
{| class="wikitable"
|
{| class="wikitable"
|-
! colspan="5" | Day 6:
|-
|~
|~
|2
|~
|~
|-
|~
|1
|1
|1
|0
|-
|~
|0
|1
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 7:
|-
|~
|~
|2
|~
|~
|-
|~
|1
|2
|1
|0
|-
|~
|0
|1
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 8:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|1
|0
|-
|~
|0
|1
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 9:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|1
|1
|-
|~
|0
|1
|0
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 10:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|1
|1
|-
|~
|0
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|}
{| class="wikitable"
|
{| class="wikitable"
|-
! colspan="5" | Day 11:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|2
|1
|-
|~
|0
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 12:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|2
|2
|-
|~
|0
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 13:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|2
|3
|-
|~
|0
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 14:
|-
|~
|~
|3
|~
|~
|-
|~
|1
|2
|2
|3
|-
|~
|1
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|
{| class="wikitable"
|-
! colspan="5" | Day 15:
|-
|~
|~
|3
|~
|~
|-
|~
|2
|2
|2
|3
|-
|~
|1
|1
|1
|~
|-
|0
|0
|0
|~
|~
|-
|0
|0
|~
|~
|~
|}
|}
... that is, you expect infestations to "crawl" over whatever land mass they're placed on, with things getting densest and toughest in the places farthest from the front line, which isn't necessarily where the infestation starts.

==Maintenance and Cleanup==
If an infestation ever becomes unmanageable or otherwise unresponsive, you can find the infestation's data on the host's disk, inside of the NWN2 user's Documents/Neverwinter Nights 2/QuestResources/ directory, and then restarting nwn2server.exe.

Infestations are saved as XML, and thus may be edited with any plain text editor. Edits made to infestations in this manner will not be read by the server until nwn2server.exe is restarted.

← Older revision		Revision as of 03:23, 16 January 2015
Line 1:		Line 1:
−	Warning: This article is about a feature which is currently under development. While this information may be used to prepare build for future releases, the ACR must be updated for anything listed to become functional.
−
−
	Infestation quests are quests which are provided as a generic framework from the ACR. The DM team of a server may specify an area or series of areas as "infested" with some sort of creature, and these creatures will expand and displace the typical spawns of all of those areas.		Infestation quests are quests which are provided as a generic framework from the ACR. The DM team of a server may specify an area or series of areas as "infested" with some sort of creature, and these creatures will expand and displace the typical spawns of all of those areas.

← Older revision		Revision as of 03:23, 16 January 2015
Line 2:		Line 2:


−	Infestation quests are quests which are provided as a generic framework from the ACR. The DM team of a server may specify an area or series of areas as "infested" with some sort of creature, and these creatures will expand and displace the typical ~~group~~ spawns of all of those areas ~~for~~ as ~~long as their numbers sustain~~.	+	Infestation quests are quests which are provided as a generic framework from the ACR. The DM team of a server may specify an area or series of areas as "infested" with some sort of creature, and these creatures will expand and displace the typical spawns of all of those areas.
		+
		+	An area is considered cleared when all of the group spawns in the area are slain. This means that areas which contain no group spawns should be guarded from infestation, as the absence of any group spawns to slay means that the area cannot be cleared.

	Infestations are limited in their spread by builder specification, and follow existing area transitions. The DM team may stop an infestation arbitrarily.		Infestations are limited in their spread by builder specification, and follow existing area transitions. The DM team may stop an infestation arbitrarily.

@@ Line 14: / Line 14: @@
 ==Infestation Spread==
-Fecundity of infestations is defined at creation and is adjustable. However, it is generally expected that infestations will attempt to spread such that there is at most a one-tier difference in the infestation strength across any given area transition.
+Fecundity of infestations is the number of bosses in the infestation, and the spread of the infestation will be reduced every time a boss is killed. An infestation without a boss does not spread, and only occupies specific areas set up by the DM. It is expected that infestations will attempt to spread such that there is at most a one-tier difference in the infestation strength across any given area transition. This algorithm isn't perfect, and complex series of area transitions can result in some bigger leaps, but simpler areas shouldn't have this problem.
 If, for example, we had an infestation which grew at a rate of 1/day with a maximum tier of 3...

@@ Line 551: / Line 551: @@
 ==Maintenance and Cleanup==
-If an infestation ever becomes unmanageable or otherwise unresponsive, you can find the infestation's data on the host's disk, inside of the NWN2 user's Documents/Neverwinter Nights 2/QuestResources/ directory, and then restarting nwn2server.exe.
+If an infestation ever becomes unmanageable or otherwise unresponsive, you can find the infestation's data on the host's disk, inside of the NWN2 user's Documents/Neverwinter Nights 2/QuestResources/ directory. Therein are XML files, each one representing one active infestation on the server and having the name picked by the DM who created it. The infestation can be removed by deleting the file and then restarting nwn2server.exe.
 Infestations are saved as XML, and thus may be edited with any plain text editor. Edits made to infestations in this manner will not be read by the server until nwn2server.exe is restarted.

@@ Line 7: / Line 7: @@
 ==Build Specifications==
-If any area or waypoint should not be affected by infestation code, it should have a local int set on it, called ACR_QST_MAX_INFESTATION and set to -1.
+If any area or waypoint should not be affected by infestation code, it should have a local int set on it, called ACR_QST_MAX_INFESTATION and set to -1. Infestations will also not pass through these areas. So, for example, if a town's surface is set as unable to be infested, an infestation outside the town won't raid the town's sewers (unless they have an area transition to the town's exterior).
 If any area of waypoint should have a maximum infestation tier allowed, it should have a local int set on it, called ACR_QST_MAX_INFESTATION and set to the maximum tier. It is important to note that setting every waypoint in an area to a max tier will not alter the state of the area. For example, an area which is set to tier 4 but only contains tier 1 waypoints will only spawn tier 1 infestations, but can be bordered by tier 5 areas, leading to PCs who find the gradient of challenge ratings extremely difficult.