Scene/SceneDesc were relatively old and unused and also quite complex to implement so they never got ported to XML from the 010 templates.

Note:  Half the files that actually use Scene/SceneDesc are in Empire Earth III, which its version 20.2.0.8 behaves differently for these blocks than other 20.2.0.8 versions.  The only way to tell the difference is by the file extension, which is .nifcache.   This is beyond the scope of nif.xml, and so only the game files that match the version conditions of Gamebryo proper are supported.

Several objects used separate center/radius when it's actually an NiBound object.  This was apparent with the addition of additional data to NiBound for custom 20.3.0.9 versions for Divinity 2.

Only MdlManBinary.nif cannot be read for Divinity 2, and it appears to be some kind of rig filled with custom classes serialized to NIF.  There is no desire to decode this single NIF with 10 custom classes.

Also the Divinity 2 XML files that have a Gamebryo header are ignored as they appear to just contain XML strings in more custom classes.

In C++ and other langs, this compound member gets generated to "union" which clashes with the reserved keyword.

Enhanced support for WorldShift.

In order to not complicate the objects, I fudged the official version conditions slightly to accommodate 10.4.0.1 given that no official versions exist between 10.2 and 20.0.

Aside from the new custom block, only modified the conditions that were already there.

Made `<version>` mean distinct combination of header values which produce identical block layouts.  This meant splitting up several main Versions into many based on User Version or Bethesda  Version.

id = Used to uniquely identify this collection of NIF versions. Can also be used for enum generation, map/dictionary keys.

user = List of User Versions which are functionally equivalent

bsver = List of Bethesda Versions which are functionally equivalent

custom = If user/bsver are default but the Version is actually specific to a developer and not an official Gamebryo version

supported = Whether or not the XML fully supports reading/writing of this version.

ext = List of custom file extensions associated with this version.

The attempt here was to exclude Bethesda from several rows on NiBoneLODController, since in the XML it inherits from NiBoneLODController for its own custom block that does not have those rows.  The reasoning is actually that it does *not* inherit from NiBoneLODController in the engine,  but the inheritance will stay fudged here for now.

Formalization of what makes type and member name strings valid requires the removal of non-alphanumerics with the exception of the colon.

They were kept separate for clarity in actual code using the enumerations; clarity that doesn't transfer over to XML which is using the raw integers.

```
(A & X) != 0 && (A & Y) != 0 && (A & Z) == 0
```
Is the same as
```
(A & (X|Y|Z)) == (X|Y)
```
Basically != 0 you want that particular bit on the RHS of the expression, and == 0 you do not.
Anything tested you put on the LHS.

Also switched the order of HalfVector3/Vector3 as the larger type should come first.

A concise way of listing which versions are most important to each game.

Each game should have only one set of `{{}}`.

Note:  In the case of Oblivion, there are two "primary" versions..  20.0.0.4 (10) is used for KF and 20.0.0.5 is used for NIF.  Thus I changed the "game name" to `{{Oblivion KF}}` for 20.0.0.4 (10).

First batch of fixed issues detected by the new linter.

Also some slight cleanup, plus an interitance fix a Bethesda particle class.

First-pass implementation of `since`/`until` and `versions`.  Avoided nearly all Bethesda blocks for now, as they require the token system or would become absurdly repetitious.

Moved all the DEM specific stuff out of NiMesh and into compounds.  Did some decoding while I was at it.   There are many small customizations to other blocks for DEM, but I am not including them in this commit.  Regardless, the existing XML only worked for DEM1 and now at least some DEM2 will load fully.

Added V10_2_0_0__1 and scoped NiFurSpringController to it since it is a custom block only for that game.

Fixed inherited duplicate names, as well as the layout of BSTriShape for Particle emitter geometry data in SSE.

Left the name for Dynamic Data as "Vertices" though it is technically just called "Dynamic Data" in engine.  It contains the vertices and bitangent X for any BSDynamicTriShape, so the naming is apt.

Added additional decoding from DEM decoding in 74c1aac since I erroneously added some of the decoding to NiPSParticleSystem in 1d62f16 anyway.

Did not decode any completely custom blocks.

Removed redundant descriptions for unknown values, removed incorrect descriptions for previously unknown values.  Any custom extension unknowns were prefixed with their relevant game.  Anything that was "Unk" was changed to "Unknown" for consistency.

A few inherited duplicates were also fixed in the process.

Hey look at that, linting helped immediately.  Too bad I forgot to lint before committing the last commit.

The `ver` attribute was never actually formalized and just meant as a shorcut for using both ver1/ver2 on the same version.  `userver` was almost never used and `userver2` was becoming increasingly uncommon as most comparisons were switched to inequalities.

To make things easier, these should just be part of the expression.

Tokens are grouped by name and associated with a list of attributes.  Only listed attributes should be processed for tokens of that name.

Order of token groups matters.  Token strings can themselves include tokens, so any token group used in other tokens needs to come after.

Using tokens from niftools#70 it is now feasible to version the Bethesda blocks.

For niftools#70

For niftools#70

…ols#76

The `cond` attribute was being overloaded with multiple functions.  Conditions should be actual expressions, using local or inherited data.  Type checking inside of `cond` would also mean that you could do both in one expression, such as `cond="NiParticleSystem && Num Vertices > 0"` which doesn't make any sense.

So, `onlyT` and `excludeT` were made to serve that function.  Two attributes also means not having to use the unary not (!) in order negate the meaning.

Existing logic can simply alias the attributes to cond if need be.

For niftools#76

`bool` type is something that has to be dealt with as it changes size.  Also it's marked as countable which should probably be analyzed... It shouldn't be used in array counts.

For niftools#76

Follow-up to fd66c97 for niftools#70

Was completely unsupported and undocumented and unused by any software.  Replaced with arithmetic even though the decoding is likely wrong anyway.

For niftools#76

For niftools#70

Have not decided on the non-escaped entities such as `==`, `|`, `||`, etc. yet, as at least `==` is much more readable than `#EQ#`.

Replaced all Version, User Version, etc. with their global tokens.

Also cleaned up NiTexturingProperty in the process.

Now that any usage of `User Version 2` was actually just a `#BSVER#` token, reorganized the header information for Bethesda NIFs into the correct layout, and renamed the member to a more appropriate BS Version.

The global for #BSVER# uses the member of operator `\`, but as it is a token now it is free to be used however one wishes.

I split #BSSTREAMHEADER# into its own token in case the expression is ever reused (it used to be on multiple members before this reorganization).

Also put `Max Filepath` into BSStreamHeader where it belonged.

For niftools#70 and niftools#76

Adopting the token syntax of the other tokens, TEMPLATE and ARG can now be treated the same as other tokens and differentiated from regular identifiers in a generic manner.

For niftools#76

Also reorganized the basic types to be in a logical order.

For niftools#76

The signed integeral types were marked as countable even though they should not be used for array sizes.  A negative value cannot be passed into an array size.   They are still integral though, so countable was split into `countable` and `integral`.

In addition,  added `boolean` to designate types that can toggle the presence of another member.

Also reordered items for `convertible` so that the referenced types come before the type referencing it, i.e. larger types first.

For niftools#74

Implemented thanks to changes done in niftools#76 for differentiating integral and "countable" i.e. can be used for sizes.

Marking types as boolean was also in niftools#76, yet there were no errors for this lint; all the `cond` references that were not complex expressions were already boolean types.

For niftools#70

Their use was discussed as being useful for shifting and masking values before sending as an ARG.

For niftools#3, niftools#76

Replaces all Flags types with real enums (where there were only two options) or a new bitfield type.

Bitfield mimics the bitfield syntax of C structs (Compounds), but also acts like Enum/Bitflags with the `storage` attribute in that the entire structure can simply be aliased to a basic type like `ushort`.

The `type` on each Bitfield member does **NOT denote size**.  Each member only takes up the bits that are defined by `width` and `pos`.  The `type` information is for casting for getters and setters.  That means for C structs, code generation would not use the type on each member, but the storage type instead.

Finally added bhkPlaneShape, used once in SSE.  Added bhkCylinderShape which is possible to export from the official FO4 exporter.

Cleaned up much of the class descriptions and also added `binary="true"` to the padding bytes.

Try to use element text whenever possible, and remove any unnecessary XML comments.  Soon the XML will be regenerated and so the XML comments need to be well formed and in predictable locations.

Named the compounds correctly after the actual structs,  separated the "Has Data" bool from the compound as it's not actually part of the struct, but before it in a for loop during (de)serialize.

Combined NiAdditionalGeometryData and the BS version into one compound when possible.  But the block can actually no longer be found in any official files, so the BS version is not very important.

For niftools#76

For reduced ambiguity.  Adapting for this in Python is as easy as

```py
# XML Booleans
XML_TRUE = ["true", "1"]
XML_FALSE = ["false", "0"]

# Example
self.is_abstract = get('abstract') in XML_TRUE
```

Note "True" and "False" are not valid booleans in XML.  Only lowercase.

Havok serialization is separate from inheritance and so certain shapes that are actually convex were not considered such by nif.xml, which in turn excludes them from uses of `template="bhkConvexShape"`.

Created a fake base class to fix these issues.  Also, bhkConvexTransformShape no longer inheriting bhkTransformShape was more correct anyway, as the Ref type could be made more specific (bhkConvexShape).

Did some comment/description cleanup and some minor decoding.

FO4 DLC uses BSLightingShaderPropertyUShortController in 2 NIFs, but according to the CK it is not actually a functional block and spits out constant warnings. It is still needed in nif.xml for serialization though.

FO4 also adds two booleans for Env Map shader type for SSR.  These were previously marked as an Unknown Short.  These booleans are *not* synced with their values in the BGSM files except for generated meshes such as SCOL and precombined.

For niftools#76.  `calc` does not need to be supported and is only used for pre-serialization preparation of the data.  This can also be done by hand.

Some revisions also need to be made for niftools#70 and niftools#73 to account for another attribute with its own expression grammar and tokens.

However, the tokens introduced for `calc` will not be added to the tokens in the XML and will need to be explicitly supported if supporting `calc`.  They are:

1D array size (uses regex): `#LEN[(.*?)]#`
2D array size (uses regex): `#LEN2[(.*?)]#`

Ternary `?`: `#THEN#`
Ternary `:`: `#ELSE#`

Also removes any unnecessary `calculated` without replacement.

Additionally, `calc` is used to limit array size for the time being, though it's possible this should be done with its own attribute, such as `maxlen`.

Unknown Short for FO3+ was two values, a byte and a bool.

Renamed "Num Skin Partition Blocks" and "Skin Partition Blocks" and combined the Partitions array into one row, as having a row separate for SSE was unnecessary.

Specifying ver1/ver2 even for `vercond="#BS...` for FO3 and later allows early rejection of that member for any non-BS 20.2 NIFs.

Use a correct bitfield for NiGeometryData flags now that we know what the unknown values are for Bethesda bhk data. (NiGeometryData that gets used in a bhk shape)

Split up the Rigid Body CInfo into multiple compounds for each Havok version (though left 550/660 combined).  Followed suit with bhkWorldObject and bhkEntity.

Having each in their own CInfo simplifies both naming and versioning at the cost of repetition.

The bhkRigidBodyCInfo variants will need some kind of shared parent, but compound inheritance is currently not part of the XML spec.  It would have to be done with custom types in niflib.  The shared parent will be needed for getting/setting the same info on different CInfo versions.

For Name-based APIs, naming all NiBound fields consistently helps with generic treatment of NiBound getting and setting for any NiObject.

FO4 changed the Color3 to a Color4 for Skin Tint.  Leaving as separate Alpha for now however.

Also found out the point of the BSSkin::Instance array which is non-uniform scaling.

Added `default` to a large number of members, as well as `calc` to a few members to enforce array sizes based on other data.

Also fixed a few `type` issues.

This is a first pass in a much larger effort,  using data analysis to gather the most commonly used values.

The previous decoding was all guesswork, though did align somewhat.  Enough to know that the decoding from FO4 applies to Skyrim as well.

Cleaned up class naming e.g. Descriptor->CInfo to match the engine and other classes already named that way.  Added hk/bhk to front of type names where appropriate.

Changed Info/Property names to be consistent e.g.  "Rigid Body Info", "Entity Info" instead of CInfo.

Changed all "Unused" fields to a consistent naming scheme, using byte array types and binary="true".

Class hierarchy fixes.  Class documentation complete overhaul.

Some existing naming collides with new naming of different fields, e.g. bhkMoppBvTreeShape "Scale" used to be "Shape Scale" and now "Scale" is  "MOPP Code" -> "Scale".

Made a correct bitfield using `uint64` as the underlying type, split into nibbles for the sizes and offsets of the vertex attributes.

Changed VertexFlags to VertexAttributes and it no longer has the empty nibble in front.

ARG passing of the BSVertexDesc is treated as the underlying numeric value of the bitfield, so that the attributes can be passed into BSVertexData using `#RSH# 44` instead of the member accessor syntax.

This makes the first use of the basic `uint64` type, so (de)serialization now requires support of 64-bit values.

Also use `true` instead of `1` to match other XML booleans.

The correct name for StringIndex is NiFixedString.  Also added NiTFixedStringMap which is used once in the NiPhysX module.

Second default values pass, plus some general changes to accommodate them.

For niftools#72

Renamed modules from Gamebryo:  NiParticle, NiPSParticle.

As of Gamebryo 2.5, old NiParticle was renamed NiParticleOld and the new NiMesh-based particle system was named NiParticle.  I didn't like this naming scheme given NiParticleOld is more important to us.

Ni Modules not in Gamebryo:  NiCustom, NiLegacy

These are to handle third party blocks and blocks from NetImmerse (pre-Gamebryo).

Ignored from Gamebryo:  NiCollision, NiPortal, NiPhysXParticle

These were instead absorbed into other modules.

Bethesda modules:  BSMain, BSAnimation, BSParticle, BSHavok, BSLegacy

Animation, Particle, Havok, and Legacy are not modules used by Bethesda.  Legacy is for Morrowind-specific blocks (NetImmerse).  In addition,  BSShader is a module for all the shader related blocks and that has all been folded into BSMain.

For niftools#72

So that first party modules can be singled out if needed.

Improved class descriptions and fixed Flags values and defaults.

For niftools#76

Implement initial subclass defaults.  Had to add additional attribute to deal with versioning of defaults, like block versioning.

Added more defaults to normal fields.

Added default to Vertex Color array, also enforcing that members with `arr1` can have a `default`.

Specify SizedString vs NiFixedString where appropriate.  The compound type `string` is an extra level of indirection in many cases, where the block can never be used on versions less than 20.1.0.3 where the CString to NiFixedString transition happened.

NiFixedString is a basic type, so using it where possible is recommended over the `string` compound type.

`string` could NOT be changed when dealing with multiple rows with the same name but version exclusive, such as "Accum Root Name".

Changed ShortString to ExportString as it was already documented as being exclusive to the Bethesda stream header.

Added SizedString with ushort length type, for the SSF File path.

BSGeometrySegmentData - Combined rows which did not be separated by version.  Adopted better naming from FO4.

AspectFlags type for NiParticlesData for BS.

Changed the unused W component of what should be a Vector4 for Vertex to 'Unused W' for all rows.  Should seriously consider making these all Vector4s for endian correctness.

Misc comment cleanup.

For niftools#70 and niftools#76

Added tokens for range attribute strings.

Did initial pass of ranges, many from Bethesda's official export scripts for FO4, which limit the values in the UI. Also have begun using data analysis to find implied min/max ranges (as well as sane defaults).

For niftools#70 and niftools#76

The way that BSPackedCombinedSharedGeomDataExtra refers to the shared geometry was decoded.  It stores the hash of the filename and the offset to the data.

NetImmerse NiParticle (called NiOldParticle after Gamebryo 1.1) was severely undecoded.  This affects several NetImmerse games like Morrowind and Freedom Force.

The per-particle info in NiOldParticle actually remained identical to the class in NiParticle, which is named "NiParticleInfo".  It did however have a different name in NetImmerse which was "NiPerParticleData".  Since they were the same data, the two compounds were merged and NiPSysData was updated.

Decoded some unknown fields and blocks for WorldShift and Guild 2.

NiSourceTexture is now correctly decoded.  The unknown byte actually controls whether the image data Ref gets serialized or not, but it was always 1.  The addition of another conditional value increases the complexity for Pixel Data to 3 rows, all exclusive by version or condition.

Even though in these cases it doesn't matter because of version exclusivity, keep them ordered by type instead of grouped by version.

Renamed BSLightingShaderPropertyShaderType and its associated name field ("Skyrim Shader Type" -> "Shader Type").

BSDistantObjectInstancedNode is mostly undecoded but fully readable.

Treatment of shader flags is preliminary and will change over time.

So that "value" can be used for bit patterns (collections of individual bits).