User:Rayanth/TableFun: Difference between revisions

Latest revision as of 05:28, 19 August 2019

Warp disruption and warp scrambling

AttributeID	AttributeName	Description	CategoryName	My notes
2506	behaviorWarpScrambleDuration		Behavior Attributes	New AI - Duration in miliseconds.
2507	behaviorWarpScrambleRange		Behavior Attributes	New AI - Range in meters.
2508	behaviorWarpScrambleDischarge		Behavior Attributes	New AI - Cap usage in GJ.
2509	behaviorWarpScrambleStrength		Behavior Attributes	New AI - Warp scramble strength (so far always a real scram).
103	warpScrambleRange	Maximum range objects can be warp scrambled from.	EW - Warp Scrambling	Old AI - Range in meters.
105	warpScrambleStrength	Amount to modify ships warp scramble status by.	EW - Warp Scrambling	Old AI - Warp disrupt/scramble strength.
504	entityWarpScrambleChance	Chance of entity warp scrambling it's target.	EW - Warp Scrambling	Old AI - Some NPCs don't warp disrupt/scram every cycle.
505	warpScrambleDuration	Duration	EW - Warp Scrambling	Old AI - Duration in miliseconds (can be null).
1350	activationBlockedStrenght		EW - Warp Scrambling	Old AI - Denotes warp scrambling effect (instead of just disruption).

@@ Line 1: / Line 1: @@
 {{#css:
-.cassiel-special tbody>tr>:nth-child(5){
+.cassiel-special tbody>tr>:nth-child(5){background-color: blue;}
-background-color: blue;
-}
 }}
 == Warp disruption and warp scrambling ==
-{| class="wikitable cassiel-special" style="text-font:left;"
+{| class="cassiel-special" style="text-font:left;"
 ! style="background-color:#222222; text-align:left;" | AttributeID
 ! style="background-color:#222222; text-align:left;" | AttributeName
@@ Line 68: / Line 66: @@
 | {{co|slateblue|Old AI}} - Denotes warp scrambling effect (instead of just disruption).
 |}
-==== Distinguishing between a warp disruptor and a warp scrambler ====
-In the good old day no NPC actually warp scrambled (shuts down microjump- and microwarpdrives), they all just warp disrupted at various strengths. With the introduction of the [[Burner Mission|Burner missions]] (2014), followed by diamond ♦-named NPCs and [[Forward Operating Base]]s (2017) as well as [[Triglavian Invasion]]s (2019) this changed. There are now two things to check to see if an NPC uses normal warp disruption or actual warp scrambling:
-* {{co|slateblue|Old AI}} - An actual warp scrambler will have the attribute 1350 (activationBlockedStrenght) set to 1.
-* {{co|violet|New AI}}  - All NPCs with the behavior-attribute of 2509 (behaviorWarpScrambleStrength) use actual warp scramblers.
-==== Consolidating 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. 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 504 but no other attributes so it cannot actually warp disrupt.
-* {{co|lightgreen|Warp scramble range}} is either attribute {{co|slateblue|103}} (old) or {{co|violet|2507}} (new).
-* {{co|lightgreen|Warp scramble strength}} is either attribute {{co|slateblue|105}} (old) or {{co|violet|2509}} (new) and values above 1 doesn't necessarily mean it's a scram.
-* {{co|lightgreen|Warp scramble duration}} is either attribute {{co|slateblue|505}} (old) or {{co|violet|2506}} (new) but can also be null.
-* {{co|lightgreen|Warp scramble chance}} is attribute {{co|slateblue|504}} (old) or {{co|violet|null}} (new) and if '''null''' should be treated as 1 (100% chance).
-* {{co|lightgreen|Warp scramble discharge}} is attribute {{co|violet|2508}} (new) but will be {{co|slateblue|null}} for old AI (doesn't simulate cap usage).
-* {{co|lightgreen|Warp scrambling effect}} is true if either {{co|slateblue|1350}} (old) or {{co|violet|2509}} (new) is not null.
-If you're writing a function or script to check for warp disruption capabilities, it's best to double-check that you have entries for both {{co|lightgreen|warp scramble strength}} and {{co|lightgreen|range}} (they should all have at least those two entries if they actually have warp disrupt capabilities), then if they do also adjust the {{co|lightgreen|warp scramble chance}} to 1 if it's null and check to see if it's the effect is that of a '''warp disruptor''' or a '''warp scrambler'''. The existence of {{co|lightgreen|warp scramble duration}} and {{co|lightgreen|discharge}} will then vary.