You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2023. It is now read-only.
1.4 changed the way it declares buff immunity on npcs:
//Don't set immunities like this as of 1.4:
NPC.buffImmune[BuffID.Confused]=true;immunitiesare handled via dictionaries through NPCID.Sets.DebuffImmunitySets
which looks like this, in SetStaticDefaults (!):
//Specify the debuffs it is immune toNPCDebuffImmunityDatadebuffData=new NPCDebuffImmunityData {SpecificallyImmuneTo=newint[]{
BuffID.Confused
}};
NPCID.Sets.DebuffImmunitySets.Add(Type, debuffData);
So it would be necessary to port such statements (most often found in SetDefaults), problematic would be dynamic immunities in AI() (haven't seen anyone do it), or looping through all buff IDs to set it, which I believe is just done through ImmuneToAllBuffsThatAreNotWhips = true now. Detecting this would be a pain I bet.
As an aside, Player.buffImmune is unchanged
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1.4 changed the way it declares buff immunity on npcs:
which looks like this, in
SetStaticDefaults
(!):So it would be necessary to port such statements (most often found in
SetDefaults
), problematic would be dynamic immunities in AI() (haven't seen anyone do it), or looping through all buff IDs to set it, which I believe is just done throughImmuneToAllBuffsThatAreNotWhips = true
now. Detecting this would be a pain I bet.As an aside, Player.buffImmune is unchanged
The text was updated successfully, but these errors were encountered: