Feature Specification: Spawn System

ç i p h é r · Post by **ç i p h é r** » Tue Mar 07, 2006 2:18 am

Spawn System
The requirements for the ALFA Spawn System are detailed below.

For a short explanation of the feature specification format, visit:
http://www.alandfaraway.org/phpbbforum/ ... hp?t=27229

Functional Requirements
Spawning of NWN objects will be accomplished using waypoints, which can be configured to spawn objects individually, in numbers greater than one (same blueprint), or in groups (multiple blueprints). NWN objects will include creatures, encounters, items, and placeables. Objects can be configured to spawn and despawn according to a builder defined schedule that is based on a given day and time. A number of reserve objects and the delays between spawning can be specified at the spawn point as well as a spawning radius and the direction they're facing. Spawning can also be restricted to when PCs are in the vicinity (area) of the spawn point.

Player restricted spawn points in a destination area will activate (if inactive) during player transitions to that destination area. The spawn point will be responsible for scheduling its next spawn cycle and for deactivating itself in the absence of players in its vicinity (area). Restricted spawn points that skip their spawn cycle will automatically activate on the next player transition into the area.

Unrestricted spawn points will enter into the scheduler from the onset and spawn according to their time cycles. Spawn groups that reach a certain strength will form raiding parties (AI?) and initiate attacks on nearby population centers (of any race or type).

Visual and sound effects can also be defined for a given spawn point.

NWN Object Dependencies
Waypoints

Local Variables and External Configs
sACRSpawnResref, sACRSpawnGroup, iACRSpawnTimeIn, iACRSpawnTimeOut, iACRSpawnMinNumber, iACRSpawnMaxNumber, iACRSpawnReserveNumber, bACRSpawnNearPC, iACRSpawnMinDelay, iACRSpawnMaxDelay, iACRSpawnChance, iACRSpawnDayIn, iACRSpawnDayOut, iACRSpawnFactionStrength, fACRSpawnRadius, fACRSpawnFacing, iACRSpawnVFX, iACRSpawnSFX

Logging and Debugging (global LOG & DEBUG (on/off) constants)
TBD

Persistence Requirements
TBD

Event Dependencies
OnAreaExit, OnHeartbeat? (Area)

Overfilled Cup · Post by **Overfilled Cup** » Tue Mar 07, 2006 2:27 am

cool beans. Wish I could make something like that integrated system you talk about.. I mean come on..The basic builder could do the basic stuff..With a bit of practice..Fully marchable patrols with stops to help old ladies across the street and put out fires and WOW...even bend down to pick up the dog doody on the corner. Cool stuff Cipher.

ç i p h é r · Post by **ç i p h é r** » Tue Mar 07, 2006 9:08 am

You and I certainly have experienced the pain there, haven't we? Having activity support in the spawning/patrolling system ensures less headaches with non-compatible systems, a more robust package builders can weave their immersive magic with, and the eradication of dozens of one off user defined scripts. Those should really be reserved for the strange and unusual, not relatively common activities you'd expect NPCs to be engaged in.

When I have some more time, I'll elaborate on what I wrote. I know Thangorn's posted a few things on the content threads which I'll also need to pull over here as soon as I can decipher his writing!

Overfilled Cup · Post by **Overfilled Cup** » Thu Apr 06, 2006 6:36 pm

Has this stalled?

It will be an important feature and needs more feedback. Currently with what we know anout NwN2 it seems these systems will be fully transferable to the new game. The best thing about that is we can spend our time making them better rather than redoing them completely.

Thats a boon for us as well as the community.

ç i p h é r · Post by **ç i p h é r** » Fri Apr 07, 2006 12:41 am

Yes it does. I could go into more detail and add the things I'd like to see specifically but it would be nice to have feedback from others with experience in this area as well.

ç i p h é r · Post by **ç i p h é r** » Thu May 18, 2006 9:55 pm

Here is the spawn system Riotnrrd was working on:

http://www.alandfaraway.org/phpbbforum/ ... php?t=6108

Fionn · Post by **Fionn** » Thu May 18, 2006 10:47 pm

DAMN! I've been after him for a month of more to get me that. Holy crap that's more complex than I'd assumed.

ç i p h é r · Post by **ç i p h é r** » Fri May 19, 2006 10:29 pm

If the beta version is in the Whitehorn mod, you could possibly extract it.

Updated the spec based on the discussion in the other thread. If we can, let's build on that discussion here so we keep it organized. Moved patrols, activities, and professions to the AI thread.

EDIT: BTW, I've tried to pry all the requirements intermingled in conversation across several different threads and place them in the spec here, so I've undoubtedly misinterpretted some things and missed others. If you notice anything missing, incorrect or wish to have something stated differently, please let me know.

ç i p h é r · Post by **ç i p h é r** » Sat May 20, 2006 2:21 am

In going over some of the discussions thus far, if we intend to develop an encounter system that essentially "manages" spawns dynamically (populations, demographics, growth, spawn point randomization, encounter randomization, etc), then there really only seems like two things which the spawn system would regulate:

1. spawn statics - spawn X many resrefs in location Y
2. spawn point properties - define the environment and the kinds of spawns an area will support naturally

The problem I see with #2 is that it would break modularity if we wanted spawn and encounter systems to operate discretely. In that case, spawn properties would also have to be defined within the boundaries of the encounter system, or at least the definitions would have to be shared. Again, much depends on what we intend to do with the encounter system. The rest will, I think, be defined around it.

ç i p h é r · Post by **ç i p h é r** » Sat May 20, 2006 4:33 pm

I went through the NESS docs and added a few other things we might want to use, like spawn radius, facing direction, visual and sound effects.

ç i p h é r · Post by **ç i p h é r** » Sat May 20, 2006 8:03 pm

I think there are many ways builders might want to configure spawn points that can be used independently or in combination with one another. Here are some of them:

By EL (the most basic method):

This spawns a variety of CRs to satisfy a given EL. The EL can either be defined by the builder specifically (fixed for that spawn point) or can be calculated by the encounter system based on party level, if left undefined; A true PnP encounter.

By Creature (resref):

A specific blueprint to spawn. This would restrict the spawn point to only this blueprint. This is probably best used for spawning in distinct objects like unique NPCs, placeables, and items.

By Groups (various resrefs):

A set of blueprints to spawn. This would restrict the spawn point to the blueprints provided. This can be used for spawning in mixed sets of creatures or combinations of creatures and other objects. This is also the best way to spawn in a camp.

By Type/Race:

A specific creature type or race. This would restrict the spawn point to creatures of the specified type (monsters) or race (humanoids).

By Tribe/Faction:

A specific tribe or faction. This would restrict the spawn point to creatures belonging to the specified tribe (monsters) or faction (humanoids).

By Alignment:

A specific alignment. This would restrict the spawn point to creatures that have the specified alignment.

Essentially, we'd be cross referencing the Monster Manual in many different ways and allowing builders to define exactly what they want at any given spawn point. Mixed sets (of types) may complicate matters for the encounter system though.

Thoughts? Anything else we might want to add to this?

Ronan · Post by **Ronan** » Sat May 20, 2006 9:42 pm

I think you're blurring the line between the spawn system and encounter system, though I'm not sure there ever was a clear line. I don't think the spawn system should do anything except spawn things at certain locations.

I haven't contributed much to this discussion because I'm still trying to think through it and find an elegant solution to where the encounter system stops and the spawn system begins. Maybe I was wrong, and they should be one and the same?

Fionn · Post by **Fionn** » Sat May 20, 2006 9:46 pm

I'd restrict EL by terrain. Sharks attacking in the moutains would be silly.

Ronan · Post by **Ronan** » Sat May 20, 2006 9:51 pm

The builder would have to first define which areas contained what sort of creatures (friendlies or unfriendlies).

ç i p h é r · Post by **ç i p h é r** » Sun May 21, 2006 12:31 am

I've been having the same struggle delineating the two systems. I'm taking the approach that the spawning system would simply concern itself with applying the spawn rules at a given spawn point and nothing more. This could just as easily be built into an encounter system, except that item and placeable spawns would have no relevance to encounters, so...I can see it both ways.

Fionn wrote:Sharks attacking in the moutains would be silly.

lol. Land sharks? It'd be priceless to see the expression on the players faces though.