Abstate.shn
caution
While this file can be extended, any newly added Abstate will NOT work! You will need a Hook to add the functionality of adding new Abstates here.
The reason behind this is the hardcoded AbStataIndex Limit in the Zone service
Column Explanation
ID
The ID of the given AbState entry. There must not be any duplicate.
| Possible Values | Data Type |
|---|---|
| 0 - 65535 | UInt16 |
InxName
The Index of the given AbState entry
| Possible Values | Data Type | Additional Info |
|---|---|---|
| Anything | String | No special characters or spaces |
AbStataIndex
A special index for an Abstate. This number can not be increased without a hook that features Abstate addition.
| Possible Values | Data Type | Additional Info |
|---|---|---|
| 0 - 792 | UInt32 | 792 is the limit of the default files |
KeepTimeRatio
This column is unused
KeepTimePower
This column is unused
StateGrade
This column is unused
PartyState
Used for Party buffs, to trigger the given AbState depending on the amount of party members.
So PartyState1 holds the Abstate given to a 1 player party, PartyState2 the Abstate given to a 2 player party and so on.
| Possible Values | Data Type |
|---|---|
| Any AbState InxName | String |
PartyRange
Range for the party members to gain the party AbState
| Possible Values | Data Type | Additional Info |
|---|---|---|
| 0 ~ 4.29 billion | UInt32 | Using values greater than 5000 is impractical |
PartyEnchantNumber
How many party members can be affected by the party buff.
Theoretically this value can be greater than 5 for expeditions.
| Possible Values | Data Type |
|---|---|
| 0 - 50 | UInt32 |
SubAbState
InxName of the SubAbstate to the AbState.
SubAbstates are defined in the SubAbState.shn file!
| Possible Values | Data Type |
|---|---|
| Every SubAbstate InxName | String |
DispelIndex
An index which defines, when an Abstate can be dispeled.
These values are hardcoded in the services and are therefore referenced by the given table below
Dispel Attribute Definition
| ID | Meaning | Technical Name |
|---|---|---|
| 0 | None | DA_NONE |
| 1 | Buff | DA_GOOD |
| 2 | Debuff | DA_DEBUFF |
| 3 | Disease | DA_DISEASE |
| 4 | Poison | DA_POISON |
| 5 | Curse | DA_CURSE |
| 6 | Stun | DA_STUN |
| 7 | Fear | DA_FEAR |
| 8 | Deeper | DA_DEEPER |
| 9 | Hide | DA_HIDE |
| 10 | Bomb | DA_BOMB |
| 11 | Charged | DA_CHARGED |
SubDispelIndex
A more refined index which defines, when an Abstate can be dispeled.
These values are hardcoded in the services and are therefore referenced by the given table below
Sub Dispel Attribute Definition
| Identifier | Meaning | Technical Name |
|---|---|---|
| 0 | None | SDA_NONE |
| 1 | Stun | SDA_STUN |
| 2 | Movespeed | SDA_MOVESPEED |
| 3 | Fear | SDA_FEAR |
| 4 | Blooding | SDA_BLOODING |
| 5 | Deeper | SDA_DEEPER |
| 6 | Blind | SDA_BLIND |
| 7 | Reverse | SDA_REVERSE |
| 8 | Bind | SDA_BIND |
| 9 | Mesmerize | SDA_MESMERIZE |
| 10 | Sever Bone | SDA_SEVERBONE |
| 11 | Knockback | SDA_KNOCKBACK |
| 12 | Evasion Minus | SDA_TBMINUS |
| 13 | GTI Resist | SDA_GTIRESIST |
AbStateSaveType
Controls, how and when an Abstate gets removed from the player (except of expiration by time)
These values are hardcoded in the services and are therefore referenced by the given table below
Abstate Save Type Definition
| Identifier | Meaning | Technical Name |
|---|---|---|
| 0 | None | AST_NONE |
| 1 | Logoff | AST_LINK_LOGOFF |
| 2 | Logoff & Death | AST_LINK_LOGOFF_DIE |
| 3 | Death | AST_LINK_Die |
MainStateInx
This column is for party buffs only. Party Abstates need a main Abstate to work, which is referenced in this field.
A furthert explanation can be found in the Adding & Editing Abstates section
| Possible Values | Data Type |
|---|---|
| Any Abstate InxName | String |
Duplicate
Defines how often a buff can stuck, if it's a stackable Abstate.
A furthert explanation can be found in the Adding & Editing Abstates section
| Possible Values | Data Type | Additional Info |
|---|---|---|
| 0 - 255 | Byte | Everything above 100 is impractical |