User:Cassiel Seraphim/ESI: Difference between revisions

Line 307:

==== Consolidation and sanity checks ====

So far there doesn't seem to be an overlap of identical types of data between the old and new AI, ~~if it's a newer NPC using the new behavior-attributes it doesn't have the equivalent old attributes. This means that~~ you can use things like coalesce in sql, or similar functions, because they will never both be set to non-null values for a single entity. In some cases, you do a triple check by picking either the old or either of the two new and exclusive attributes.

So far there doesn't seem to be an overlap of identical types of data between the old and new AI, so you can use things like coalesce in sql, or similar functions, because they will never both be set to non-null values for a single entity. In some cases, you do a triple check by picking either the old or either of the two new and exclusive attributes.

There ~~will~~ also ~~be entries~~ with ~~only some of the warp disrupt~~ attributes, like the '''Renyn Meten''' that has ~~a warp disrupt chance value in~~ attribute {{co|slateblue|504}} but no other attributes so it cannot actually warp disrupt.

There are also entities with too few attributes, like the '''Renyn Meten''' that only has the attribute {{co|slateblue|504}} but no other attributes so it cannot actually warp disrupt.

* {{co|lightgreen|Warp scramble range}} is either attribute {{co|slateblue|103}} (old) or one of {{co|violet|2507}} or {{co|violet|2504}} (new).

@@ Line 307: / Line 307: @@
 ==== Consolidation and sanity checks ====
-So far there doesn't seem to be an overlap of identical types of data between the old and new AI, if it's a newer NPC using the new behavior-attributes it doesn't have the equivalent old attributes. This means that you can use things like coalesce in sql, or similar functions, because they will never both be set to non-null values for a single entity. In some cases, you do a triple check by picking either the old or either of the two new and exclusive attributes.
+So far there doesn't seem to be an overlap of identical types of data between the old and new AI, so you can use things like coalesce in sql, or similar functions, because they will never both be set to non-null values for a single entity. In some cases, you do a triple check by picking either the old or either of the two new and exclusive attributes.
-There will also be entries with only some of the warp disrupt attributes, like the '''Renyn Meten''' that has a warp disrupt chance value in attribute {{co|slateblue|504}} but no other attributes so it cannot actually warp disrupt.
+There are also entities with too few attributes, like the '''Renyn Meten''' that only has the attribute {{co|slateblue|504}} but no other attributes so it cannot actually warp disrupt.
 * {{co|lightgreen|Warp scramble range}} is either attribute {{co|slateblue|103}} (old) or one of {{co|violet|2507}} or {{co|violet|2504}} (new).