Animations are coded into models (although a model may reference another model for the animations to be copied from).

NWN's engine supports animation which are not just movement, rotation or other object transforms; you can also 'animate' some Trimesh properties such as Alpha and self-illumination colour (used for e.g. fading in/out a night-time glow in the windows of buildings).

Animations are used in the engine to time actions (eg casting a spell) as well as even make situational bonuses apply (eg; Knockdown is "they're in the knock down animation state" - the effect just plays the animation for a set duration).

This page is currently written just to list "these are animation names and durations" not about creating custom ones - that will hopefully follow!

Tutorials

A reasonably old tutorial on creature animations that still mainly applies today is available here: http://www.neverwinternights.info/cc_creatureanimation.htm

Full (Humanoid) versus Simple (Creature)

Most humanoid sized creatures use a full animation set - ie they can sit down, or whatever else. The super model for this is "a_ba" (which can also be edited to affect all things referencing it).

Many monster creatures use a limited animation set. These are usually more model-specific, eg; wolves would be very different to ogres.

The types of animation allowed are set by the appearance.2da line:

There are modifiers for these MODELTYPE which can be added but don't affect the animations available as such:

• W - Wings allowed (P assumes this)
• T - Tail allowed (P assumes this)

Animation Types

Loop - The animation is built to be looped. The first and last frames are the same pose. Often called "duration".

FNF - "Fire and forget" animations play once and include the start and end portions in the single animation. Most commonly used for emotes and actions. Many however can be looped just fine (especially useful for the talking ones for instance).

Start - The animation includes only the starting portion of the animation, which can also be called "impact". Some game animations are the same for start and end, and just reverse the start one.

End - The animation includes only the ending portion of the animation, often called "cessation".

Animation Root

The animroot parameter in the animation header tells which bone is the highest level bone controlling the animation. Multiple animations can be mixed within a timeframe. The animation with the deeper animroot takes precedence. Full body animations have their animroot set to the rootdummy, while partial body animations, like walking with a shield, only animate from the torso down to the hands.

Animation Length

The animations have a length - this is set in MDL as the "length" parameter. This is in real seconds and orientationkey fields determine the progression of the animation over that time period. Each node affected can have different amounts of changes to the animation done, and the game interpolates between the times - although it is best to keep them frequent throughout the time period.

Some animations can be quite long - like 7 seconds for "worship" - while some are super short - 0.0333333015 for "deadfnt".

Example Animation Length is in frames based on 30 FPS below, so a length of "1" would be 30 frames of animation, and a length of "0.5" would be 15. 0.033333 seems to be the lowest - which is about 1FPS - and probably should be a guideline on how a "static" and quick animation is done (in this case, being dead you don't move much!).

Some animation are hardcoded to run for a predefined amount of time. If you make it longer or shorter the game compresses or expands the time. For instance walk animations have a set time loop and going beyond that makes the animation look sped up.

It's not clear which ones are hardcoded fully like this. This information should be listed below if known.

Custom Animations

The default a_ba etc. MDL files tend not to include custom animation definitions. These are for adding yourself as a modder. You have options of just using the looping animation or adding a start and end animation too.

Animations are named:

• customXstart - the starting animation, fired once when the animation starts
• customXlp - the looping animation, this can be the only one present if required
• customXend - the ending animation, fired once when the animation ends

With NWN:EE you can use custom1 up to custom70 with relevant constants for PlayAnimation available to use them.

Choice of Combat and Pause Animations based on Weapon

The weapon or items you have equipped in your left and right hands affect many animations. The main baseitems.2da WeaponWield column controls a lot of this although some is hardcoded slightly. Some rough notes on additional things that occur that are not combat animation related:

• **** = standard one-handed weapon (although may be two handed if small creature is wielding it)
  • Torches have their animation coded to their baseitems.2da line
• 1 = not wieldable
• 4 = two-handed weapon (polearm)
  
  • Has a special idle animation (over the shoulder at rest)
• 5 = bow
  
  • Special walk animation overlay
• 6 = crossbow
  
  • Has a special idle animation
• 7 = shield
  
  • Special walk animation overlay
• 8 = double-sided weapon
  
  • Has a special idle animation (over the shoulder at rest)
• 9 = creature weapon
• 10 = sling
• 11 = throwing weapon (dart, shuriken or throwing axe)

Animation Supermodels

The game can inherit animations - no need to have every MDL file have animations in it. A model may have a (super)model from which it inherits animations. The model may overwrite any animation from its supermodel. The structure of the two models must to match, i.e. the order of the objects in both files must be the same.

The most complex chain of supermodels is the ones used for player models. This section will be filled out with the hierarchy (and why you see slightly different animations for say, Half-Orcs compared to Humans) later.

Animation Lists

These lists have been reordered from what is in the MDL files to be in a more sensible order where things related to each other are next to each other (eg sitdown and sit animations).

• Animation Name - the name used in the MDL file. Recommended to make it lowercase as the default files do.
• Title - What we're calling it here for clarity
• Length - The "length" field timing in seconds that the engine assumes. If the example FPS isn't matching up it'll just speed up or slow down the animation.
• Example Animation Length (30FPS) - since Blender and 3dsMax work in frames, not seconds, this is an example time frame for 30FPS
• Base/Overlay - Some animations are base animations, and some will overlay on top of an existing animation, for instance talking animations, over the pause or sit animation, or having a shield equipped when running.
• Type - See above for types.
• Animroot - The root node this animation is tied to, eg; torso_g - see notes about about animroot
• nwscript PlayAnimation constant - the constant to use in PlayAnimation to get this to play.
• Example picture - example picture if required

Full Animation List

Full models are "P" for parts-based player models and "F" for full animation set single-models.

Simple Animation List

Used when MODELTYPE is "S" and "L", although "L" has a few additions. These are generally used by the non-humanoid or simple models, generally with no weapons or one type of weapon. The "c" references "creature" - think dogs, trolls, beetles or the like who wield no weapons and are not humanoid enough to rely on the default animations.

Technically you can code up the animations to assume some form of weapons - for instance the Balor or Fire Giant who are L have a single large sword in their primary attacking hand. Driders have bows or one or two weapons, etc.

L additionally can have full animations for Bow and Crossbows - which appears useful for the "Drider" creatures who use a lot of bows. Most creatures which are not Driders will still be able to "weild" them but revert to default to the basic animations it seems. They could have them added though (eg a Fire Giant wielding a Crossbow would work with animations added). Note that slings are not available although they generally "look fine" and act as if the creature is just throwing a stone instead of using a sling if it generally swipes it's hands as it's attacking (ie Mephits are good, while Wolves may not be so good!).

You can have weapons (rhand/lhand) and shields (lforearm) with the appropraite nodes. However the base animations won't change.

One other note for "L" types: the WEAPONSCALE property in appearance.2da does scale the weapon visually but does not add any additional range to melee attacks - the game assumes you've sized the creatures combat distance accurately to the weapon they (usually) weild, eg a Balor with his Greatsword.

Actions that do not work:

• ActionSit will fail for S and L model types

Animations that do not play:

• Talking overlay animations won't ever play for S and L creatures
• Potion and Read Scroll animations when using items will just play creadyr - the "cast" part does work though (ie pointing outwards usually) utilising ccastout. Grenades do mostly work as intended though and use an attack animation ca1slashr and properly throw the projectile.
• Many emotes will default back to "cpause1" instead of playing
• There is only one knockdown/death animation
• You can only have 1 casting animation plus the creature special one
• And many many more limitations but with these limitations comes a lot faster animation set to make.

Things that need testing:

• Animation names that are in the "Full" set and may work on the S or L sets if present.
  • To test: more emotes, things like "whirlwind" and "drwright" (drawing weapons),
• Animations that automatically play, say, "cpause1" explicitly, even if the F animation is present
• Custom animations

Some notes from here: http://www.neverwinternights.info/cc_creatureanimation.htm

The "Equivalent Full Animation" may be a useful reference point if copying from a_ba and other supermodels. Every simple animation has a full equivalent.

Ambient and non-combat Animations

Used when PlayAnimation is played and for certain actions in the game.

Many are also used in Conversations - a hardcoded list according to the GFF documentation, although since the list there doesn't correspond to the nwscript there are other options - see below. Putting your own in via. a GFF editor may actually work fine it is likely not validated.

The default conversation editor only shows these options however as per above menus. There is nothing special that PlayAnimation cannot do, so you can also use the animations from that in a script.

The fact some say "overlay" probably means the head continues to bob as if talking when the animation is played but this needs testing. Not sure if PlayAnimation also does this or if you put in other values into this field in the GFF.

• 0 = default, talk normal
• 28 = taunt
• 29 = greeting
• 30 = listen
• 33 = worship
• 34 = overlay salute
• 35 = bow
• 37 = steal
• 38 = talk normal
• 39 = talk pleading
• 40 = talk forceful
• 41 = talk laugh
• 44 = victory fighter (note: interestingly not named 1/2/3...)
• 45 = victory mage
• 46 = victory thief
• 48 = look far
• 70 = overlay drink
• 71 = overlay read
• 88 = play no animation - A special one presumably stops talking (the 0 option or option 38)

For the Engine ID a list of these is available on the NWNX pages. Why Bioware didn't just link the constants to the engine ID values who knows. Maybe to protect the poor animation programmers from the toolset script editors...

There are also animations that might be usable in the conversations which are not available with PlayAnimation as per this NWNX page.

Note: If an Animation Name field is blank then it simply won't play an animation.

Item Conjuration and Casting Animations

Note that spells cast from items come with their own pre-set animations. These appear to be hardcoded to different baseitems.2da lines.

Tile Animations

Note for at least the Day/Night/Nigh2Day/Day2Night animations, these animations will only run on objects that have an animation dummy; a dummy nested within the main dummy of the MDL, and with the exact same name as that main dummy but with 'a' appended to the end, e.g. if you have a tile called tno01_s01_02, the animation dummy must be called tno01_s01_02a. This is because by default all tile Trimesh geometry is static, but the engine checks for geometry that's linked to the animation dummy and checks for animations on that geometry only.

Example frames (taken from a night/day glowing window that works):

VFX Animations

Placeable Animations

Animations just for placeables. Animation times are examples there is no set limits.

Note if there are inventories some of the animations are disabled; on, off,  on2off, off2on, default  (used when set to static). 

Note: Setting a placeable containing a skinmesh or animmesh to static will lead to a crash. There is a flag in the placeables.2da which prevents the user from setting it to static. Example: Ballista model from patch 1.69 (its bowstring uses a skinmesh).

Animations for Doors

Animations just for door objects.