4th Age

[J1M]

I've finished implementing the abilities for the Hobgoblin Grunt and Hobgoblin Soldier. As mentioned above this meant implementing reactions. It also involved implementing the Marked condition (Rules Compendium, page 232).

Here's a video demonstrating Formation Strike, a conditional movement effect after an attack hits that takes into account most of the things that have been discussed in the thread recently (new monster, tooltips, checking monster race). The Hobgoblin Soldier advances, takes an opportunity attack, misses an attack, spends an action point, attacks again, the hit triggers a shift to guard an ally, which does not trigger an opportunity attack.

[J1M]

Got tired of WoW, so here are some updates:

Defeated creatures no longer block movement or line of sight.
Powers can now have both Prereqs (to select during character building) and Reqs (conditions that must be true to use them, such as Bloodied).
Finished the Orc Raider abilities.

[Unhelpful Contrarian]

I've finished implementing the abilities for the Hobgoblin Grunt and Hobgoblin Soldier. As mentioned above this meant implementing reactions. It also involved implementing the Marked condition (Rules Compendium, page 232).

Here's a video demonstrating Formation Strike, a conditional movement effect after an attack hits that takes into account most of the things that have been discussed in the thread recently (new monster, tooltips, checking monster race). The Hobgoblin Soldier advances, takes an opportunity attack, misses an attack, spends an action point, attacks again, the hit triggers a shift to guard an ally, which does not trigger an opportunity attack.

Strange. I’m unable to see the clip.

[WhiteShark]

Strange. I’m unable to see the clip.

Works for me. Have you tried watching it in a new tab? Are you having trouble viewing any other f.rpghq.org links?

[J1M]

@rusty_shackleford it appears we have 2 members unable to view vault videos.

Implementing the Imp's Tail Sting ability motivated a few improvements:
Concrete example of a monster refreshing a limited use power.
OngoingEffect can now impose a stat penalty in addition to ongoing damage and a condition.
Implemented secondary/tertiary/quaternary/quinary/etc multi-hit effects.

Also implemented the "next hit" conditional +2 buff for the Hobgoblin Archer, which I assume is similar to what will be needed for a lot of player abilities that grant temporary bonuses.

Looking to confirm a rule interpretation: which parts of the Imp's Tail Sting does a Skeleton ignore? My assumptions:

• The power has the Poison keyword, but that doesn't make the Skeleton immune to non-poison portions of the Power.
• Assuming the first attack roll is successful, the Skeleton takes the 1d8+3 physical damage.
• Assuming the second attack roll is successful, the Skeleton ignores the ongoing effect (damage and stat penalty) entirely because it is the Poison effect type.

Currently, the Skeleton is subject to the poison effect, but immune to the ongoing damage and still subject to the stat penalty. I intend to change this, but wanted to confirm first.

Monster Manual, page 63

Tail Sting (standard; recharges when the imp uses vanish) ✦ Poison
+8 vs. AC; 1d8 + 3 damage, and the imp makes a secondary attack against the same target.
Secondary Attack: +5 vs. Fortitude; the target takes ongoing 5 poison damage and a –2 penalty to Will defense (save ends both).

Monster Manual, page 234

Skeleton Level 3 Soldier
...
Immune disease, poison; Resist 10 necrotic; Vulnerable 5 radiant
...

[WhiteShark]

IMMUNITY

Some creatures are immune to certain effects. If a creature is immune to a damage type (such as cold or fire), it doesn’t take that type of damage. If a creature is immune to charm, fear, illusion, or poison, it is unaffected by the non- damaging effects of a power that has that keyword. A creature that is immune to a condition or another effect (such as the dazed condition or forced movement) is unaffected by the stated effect.

Immunity to one part of a power does not make a creature immune to other parts of the power. For example, when a creature that is immune to thunder is hit by a power that both deals thunder damage and pushes the target, the creature takes no damage, but the power can still push it.

So, for most immunities, the text in green applies: the damage type or condition is ignored, but the rest is not. However, for charm, fear, illusion, and poison immunities, the immunity extends to all effects of a power with that keyword. Furthermore, since Poison is both a damage type and a keyword, immunity to Poison means both immunity to Poison damage and immunity to all effects of Poison-keyword powers. Hence:

• The Skeleton is immune to all parts of a Poison-keyword power except damage of other types.
• Assuming the first attack hits, the Skeleton takes 1d8+3 damage because it is Physical, not Poison.
• Assuming the second attack hits, the Skeleton ignores the effect because it comes from a power with the Poison keyword.

[rusty_shackleford]

@rusty_shackleford it appears we have 2 members unable to view vault videos.

I suspect it might be because it's an mkv. Didn't bother checking the encoding, but it could be that too. I think webm/vp8 has the highest adoption between browsers for video.

[J1M]

@rusty_shackleford it appears we have 2 members unable to view vault videos.

I suspect it might be because it's an mkv. Didn't bother checking the encoding, but it could be that too. I think webm/vp8 has the highest adoption between browsers for video.

I just used the default settings in OBS. I don't see webm listed. @Oyster Sauce and @Unhelpful Contrarian which OS/browser are you using?

[Oyster Sauce]

@rusty_shackleford it appears we have 2 members unable to view vault videos.

I suspect it might be because it's an mkv. Didn't bother checking the encoding, but it could be that too. I think webm/vp8 has the highest adoption between browsers for video.

I just used the default settings in OBS. I don't see webm listed. @Oyster Sauce and @Unhelpful Contrarian which OS/browser are you using?

Firefox

[J1M]

@WhiteShark thoughts on treating Invisible as a Condition? Specifically referring to the kind granted by the Imp's Vanish power, not the Stealth skill. Does the Imp need to follow all of the Remaining Hidden rules that apply to someone who obtained Stealth via a skill check? It almost seems like there are different types of invisibility, or do they all break when someone attacks, etc.

[Unhelpful Contrarian]

@rusty_shackleford it appears we have 2 members unable to view vault videos.

I suspect it might be because it's an mkv. Didn't bother checking the encoding, but it could be that too. I think webm/vp8 has the highest adoption between browsers for video.

I just used the default settings in OBS. I don't see webm listed. @Oyster Sauce and @Unhelpful Contrarian which OS/browser are you using?

Chrome on a mobile device.

[WhiteShark]

@WhiteShark thoughts on treating Invisible as a Condition?

I think that makes sense. I don't foresee it causing any rules conflicts to classify it as such.

It almost seems like there are different types of invisibility,

Invisible and Hidden are indeed separate conditions.

hidden: When a creature is hidden from an enemy, the creature is silent and invisible to that enemy. A creature normally uses the Stealth skill to become hidden. See also invisible.
[...]
invisible: If a creature is invisible, it has several advantages against creatures that can’t see it: It has total concealment against them, it doesn’t provoke opportunity attacks from them, and they grant combat advantage to it.

Thus, Hidden includes the effects of Invisible against targets from whom one is Hidden, but being Hidden doesn't make one generally Invisible, and one can be Invisible without being Hidden.

I recall finding Stealth tricky to adjudicate at the table becuase, technically, it's checked per enemy. I'm not sure how hard implementing it will be, but at least the computer will be able to track it 100% faithfully to the rules. Here's a guide I remember being useful for understanding the Stealth mechanics in 4E: The Rules of Hidden Club

[J1M]

That was an interesting read. Agree that per creature skill checks each turn is a huge pain, even for a computer.

I also think the author is overcomplicating things a bit. If the players can communicate to effectively strip Hidden status from an enemy, why can't enemies do the same, essentially simplifying the benefit to applying only when you are hidden from all enemies?

Also a little counterintuitive that invisible is less beneficial than hidden, but at least it is semantically sound.

[WhiteShark]

I also think the author is overcomplicating things a bit. If the players can communicate to effectively strip Hidden status from an enemy, why can't enemies do the same, essentially simplifying the benefit to applying only when you are hidden from all enemies?

I thought the same thing at first, but after reviewing both the guide and the Rules Compendium, I see the issue.

If a creature finds a hidden creature, it might point the hidden creature out to others, resulting in them knowing its location.

Yes, you CAN point out the exact square of any creature you are aware of, to anyone else.

This does NOT mean that the creature is no longer Hidden, or that anyone else can perceive it - but as long as they believe you when you tell them what square it's in, they can "guess" the right square automatically.

So, as long as PCs are sharing information and can take Free Actions, anyone who breaks Hidden can tell everyone else what square to target.

As you can see, pointing out a creature to one's allies does not strip it of its Hidden status. It only lets them know the square(s) the creature occupies. Thus, the Hidden creature retains all the other benefits of Hidden against creatures who have yet to directly perceive it.

It may be worth considering what creatures can communicate when deciding whether location information can be shared. Mindless creatures, for example, may not be able to communicate at all. Since the rules only say a creature 'might' point it out to others, whether a creature can and will do so comes down to the GM's ruling.

[J1M]

IMMUNITY

Some creatures are immune to certain effects. If a creature is immune to a damage type (such as cold or fire), it doesn’t take that type of damage. If a creature is immune to charm, fear, illusion, or poison, it is unaffected by the non- damaging effects of a power that has that keyword. A creature that is immune to a condition or another effect (such as the dazed condition or forced movement) is unaffected by the stated effect.

Immunity to one part of a power does not make a creature immune to other parts of the power. For example, when a creature that is immune to thunder is hit by a power that both deals thunder damage and pushes the target, the creature takes no damage, but the power can still push it.

So, for most immunities, the text in green applies: the damage type or condition is ignored, but the rest is not. However, for charm, fear, illusion, and poison immunities, the immunity extends to all effects of a power with that keyword. Furthermore, since Poison is both a damage type and a keyword, immunity to Poison means both immunity to Poison damage and immunity to all effects of Poison-keyword powers. Hence:

• The Skeleton is immune to all parts of a Poison-keyword power except damage of other types.
• Assuming the first attack hits, the Skeleton takes 1d8+3 damage because it is Physical, not Poison.
• Assuming the second attack hits, the Skeleton ignores the effect because it comes from a power with the Poison keyword.

I had to modify the base Effect class to require an EffectTypes property, which involved touching every Effect file made so far, but the keyword that controls this immunity check is now at the individual effect level instead of the Power.

A pain to do, but now I have the flexibility to do everything you quoted, such as having creatures immune to only some of the effects a Power hits them with. (Confirmed it works for the Tail Sting + Skeleton interaction mentioned above.)

With that out of the way, it's time to return to Concealment/Obscured Squares/Invisibility.

[J1M]

The invisible condition is now functioning correctly. (Total concealment, combat advantage, movement doesn't provoke an opportunity attack.)

Emergent counter for invisibility: make the invisible creature perform an opportunity attack.

I decided that "attack" referred to "attack power" not "attack roll" for the sake of clearing the invisible condition. The practical difference is that an invisible attacker retains combat advantage for all attack rolls in a power with secondary/tertiary hit effects.

With those changes, all of the monsters I set out to implement are done.

► Show Spoiler

Hobgoblin Archer
Hobgoblin Grunt
Hobgoblin Soldier
Decrepit Skeleton (level 1)
Skeleton
Blazing Skeleton (level 5)
Orc Raider
Imp
Gravehound
Zombie Rotter

Time to bite the bullet and implement some kind of visible damage effect to make it easier to see the outcomes of attacks. I also need to revisit the targeting code and clean that up since it was initially written before there was the concept of allied teams of creatures.

[WhiteShark]

I decided that "attack" referred to "attack power" not "attack roll" for the sake of clearing the invisible condition. The practical difference is that an invisible attacker retains combat advantage for all attack rolls in a power with secondary/tertiary hit effects.

Are you referring to Hidden? Invisible isn't automatically cleared by making an Attack. The end trigger for Invisible is specific to the power that granted it. For example, in the case of Invisibility granted by the Imp's Vanish power:

The imp becomes invisible until the end of its next turn or until it hits or misses with an attack.

The imp doesn't have any powers that cause it to make multiple attacks, but if it did, its Invisibility―and the benefits granted thereby―would end after the first attack roll.

If you do mean Hidden, then the rules already have you covered:

Not Remaining Hidden:

If the creature takes an action that causes it not to remain hidden, the creature retains the benefits of being hidden, such as combat advantage, until the action is resolved. The creature can’t become hidden again as part of that same action.

Still important to remember that Hidden and Invisible are distinct. For example, an imp that uses Vanish becomes Invisible, but it doesn't become Hidden unless it subsequently uses Stealth to do so.

[J1M]

I'll have to check if the Imp was touched by errata. What you've quoted doesn't match the Monster Manual, page 63.

Tail Sting has a secondary attack and Vanish does not refer to hit or miss.

Haven't made an attempt to implement Hidden.

[WhiteShark]

I'll have to check if the Imp was touched by errata. What you've quoted doesn't match the Monster Manual, page 63.

You're right, it was apparently updated in Monster Vault. Since the later books updated the monster math for better balance against player stats, I recommend generally defaulting to the updated versions of monsters; both the portable compendium and the online one always show the most recent version of a monster.

[J1M]

I'll have to check if the Imp was touched by errata. What you've quoted doesn't match the Monster Manual, page 63.

You're right, it was apparently updated in Monster Vault. Since the later books updated the monster math for better balance against player stats, I recommend generally defaulting to the updated versions of monsters; both the portable compendium and the online one always show the most recent version of a monster.

Wasn't aware that they had updated stats with the Monster Vault instead of creating "Imp 2". I had stayed away from the Essentials line because it came across as desperate, especially the new character options.

I'm guessing the updates were pretty scattershot, rather than a reprint. Though to your point if the math changed so much that monster damage nearly doubled it might be a real pain to go through and update everything. (Am aware of MM3 on a business card, if I was using that approach it wouldn't be that difficult to update since I'm using Excel as a data source, but I am a bit concerned that would make all of the monsters feel the same.)

[J1M]

Have been improving the tooltips today so the effects that have been created already don't look so much like debug output.

How interested are people in seeing how the project is made? The code/data/etc? Here's an example of the data that defines the Imp's Tail Sting power. It's more complicated than other Powers because of the secondary attack (SequentialHit column).

By defining the data in Excel, I can easily do find/replace across all of the data or fill new rows/columns and use formulas to populate fields like Alias, PowerUsedStat, GameElement, etc. Each of the 50+ Excel sheets defines an enumeration, such Condition type, PowerSource, or Feat type. These sheets are translated into about 12,000 lines of C# to serve as an in-memory database. This approach provides compile-time type checking, intellisense, and the ability to implement things like extension methods.

Code: Select all

EnumId{ushort}	Id{omit}	Alias{string}		CreatureName{omit}	Title{string}		PowerUsedStat{Stat}			GameElement{GameElement}			FlavorText{string}		Prereq{Req}	Req{Req}	Job{Job}	PowerType{PowerType}	Level{int}	IsCommonAction{bool}	IsBasicAttack{bool}	Usage{Usage}	PowerSource{PowerSource}	Focus{Focus}	ActionType{ActionType}	Range{Range}		Target{Target}		Attack{Attack}			HitDamage{Damage}			DynamicVars{Stat[]}	DamageTypes{DamageType[]}	EffectTypes{EffectType[]}	HitEffects{Func<Creature,Creature,SrcId,List<Effect>>}							HostHitEffects{Func<Creature,Creature,SrcId,List<Effect>>}	SequentialHit{Power}		HostEffects{Func<SrcId, ReadOnlyCollection<Effect>>}
0x5D00		23808		Imp_TailSting		Imp			Tail Sting		Stat.PowerUsed_Imp_TailSting		GameElement.Power_Imp_TailSting			Multi-attack power test.	#AlwaysReq	#AlwaysReq	Job.None	PowerType.Attack	0		FALSE			FALSE			Usage.Encounter	PowerSource.None		Focus.None	ActionType.Standard	#RangeType.Melee 1	#TargetType.Enemy 1	#Ability.None +8 Defense.Phys	#1d8+3 Ability.None DamageType.Physical	[]			[DamageType.Toxin]		[EffectType.Poison]		(_,_,_) => new([])											(_,_,_) => new([])						Power.Imp_TailStingSecondary	(_) => new([])
0x5D01		23809		Imp_TailStingSecondary	Imp			Tail Sting Secondary	Stat.PowerUsed_Imp_TailStingSecondary	GameElement.Power_Imp_TailStingSecondary	[Flavor text NYI]		#AlwaysReq	#AlwaysReq	Job.None	PowerType.None		0		FALSE			FALSE			Usage.None	PowerSource.None		Focus.None	ActionType.None		#RangeType.Melee 1	#TargetType.Enemy 1	#Ability.None +5 Defense.Fort	#0 Ability.None DamageType.None		[]			[DamageType.Toxin]		[EffectType.Poison]		#(_,_,_) => [OngoingEffect [EffectType.Poison] 5 DamageType.Toxin Condition.None -2 Stat.Defense_Will]	(_,_,_) => new([])						Power.HobgoblinSoldier_Flail	(_) => new([])

[WhiteShark]

How interested are people in seeing how the project is made? The code/data/etc? Here's an example of the data that defines the Imp's Tail Sting power. It's more complicated than other Powers because of the secondary attack (SequentialHit column).

I'm a total amateur at coding, but I do find it interesting. I've never made a game, so at some point I'm curious to see how the core loop works.

[loregamer]

As a fellow code monkey I would be interested

[J1M]

One-time disclaimer: I am a hobbyist. Never worked in the game industry professionally, never completed a project to the point of putting it on a storefront. I'll place any technical details after the screenshot/video so those only interested in the progress can easily bypass those details.

Today I added icons for status conditions. I'm not sure how I will go about visually representing other effects like ongoing damage or temporary buffs yet. I suspect using icons for those in the same way would be overwhelming. Maybe I will go with something like a "buff' or "debuff" indicator that shows how many are present and you can mouseover to get more information. There's also the issue of distinguishing which effects should be displayed or not, since the approach I use has the same system for stat changes provided by things like level or race and those provided by powers.



The implementation essentially attaches a big list of Effects to each creature. A monster entering an encounter has 20-30 effects on it from its base stats and abilities. A creature does not have a strength score or a stat for "number of healing words cast this encounter". Any time a stat is needed for a calculation, it is derived from the list of Effects.

Effects implement an IsStat() function and a GetBonus() function that produces a list of stat bonuses. These bonuses include 4 pieces of information: which stat the bonus is for, how much, what type of bonus it is, and the game element it came from. All of that information is required in order to accurately calculate the stacking rules for how different effects are combined/ignored. If you think this sounds more complicated than how most RPGs implement things, you would be correct.

There's no simple "everything stacks" or "everything is an additive or multiplicative bonus". There are all sorts of conditional effects that mean that an effect needs to be aware of the entire encounter state in order to know if it applies. Examples:

• Apply a bonus if this is an opportunity attack
• Apply a bonus if the target is a certain size
• Apply a bonus that is removed once used

Current list of Stats:

► Show Spoiler

Code: Select all

	//UnsortedStat UnsortedStat
	UnsortedStat_CreatureSize = StatGroup.UnsortedStat | UnsortedStat.CreatureSize,
	UnsortedStat_SubjobCountMax = StatGroup.UnsortedStat | UnsortedStat.SubjobCountMax,
	UnsortedStat_SubjobCount = StatGroup.UnsortedStat | UnsortedStat.SubjobCount,

	//Ability Ability
	Ability_Str = StatGroup.Ability | Ability.Str,
	Ability_Con = StatGroup.Ability | Ability.Con,
	Ability_Dex = StatGroup.Ability | Ability.Dex,
	Ability_Int = StatGroup.Ability | Ability.Int,
	Ability_Wis = StatGroup.Ability | Ability.Wis,
	Ability_Cha = StatGroup.Ability | Ability.Cha,

	//Defense Defense
	Defense_Phys = StatGroup.Defense | Defense.Phys,
	Defense_Fort = StatGroup.Defense | Defense.Fort,
	Defense_Refl = StatGroup.Defense | Defense.Refl,
	Defense_Will = StatGroup.Defense | Defense.Will,
	Defense_Save = StatGroup.Defense | Defense.Save,

	//Health Health
	Health_HitPointsMax = StatGroup.Health | Health.HitPointsMax,
	Health_HitPointsBloodied = StatGroup.Health | Health.HitPointsBloodied,
	Health_HealingSurgeMax = StatGroup.Health | Health.HealingSurgeMax,
	Health_HealingSurgeValue = StatGroup.Health | Health.HealingSurgeValue,
	Health_SecondWindMax = StatGroup.Health | Health.SecondWindMax,
	Health_DeathSavesMax = StatGroup.Health | Health.DeathSavesMax,

	//Skill Skill
	Skill_Acrobatics = StatGroup.Skill | Skill.Acrobatics,
	Skill_Arcana = StatGroup.Skill | Skill.Arcana,
	Skill_Athletics = StatGroup.Skill | Skill.Athletics,
	Skill_Bluff = StatGroup.Skill | Skill.Bluff,
	Skill_Diplomacy = StatGroup.Skill | Skill.Diplomacy,
	Skill_Dungeoneering = StatGroup.Skill | Skill.Dungeoneering,
	Skill_Endurance = StatGroup.Skill | Skill.Endurance,
	Skill_Heal = StatGroup.Skill | Skill.Heal,
	Skill_History = StatGroup.Skill | Skill.History,
	Skill_Insight = StatGroup.Skill | Skill.Insight,
	Skill_Intimidate = StatGroup.Skill | Skill.Intimidate,
	Skill_Nature = StatGroup.Skill | Skill.Nature,
	Skill_Perception = StatGroup.Skill | Skill.Perception,
	Skill_Religion = StatGroup.Skill | Skill.Religion,
	Skill_Stealth = StatGroup.Skill | Skill.Stealth,
	Skill_Streetwise = StatGroup.Skill | Skill.Streetwise,
	Skill_Thievery = StatGroup.Skill | Skill.Thievery,

	//Speed Speed
	Speed_Walk = StatGroup.Speed | Speed.Walk,
	Speed_Climb = StatGroup.Speed | Speed.Climb,
	Speed_Swim = StatGroup.Speed | Speed.Swim,
	Speed_Fly = StatGroup.Speed | Speed.Fly,
	Speed_Shift = StatGroup.Speed | Speed.Shift,
	Speed_Crawl = StatGroup.Speed | Speed.Crawl,

	//Immune EffectType
	Immune_Augmentable = StatGroup.Immune | EffectType.Augmentable,
	Immune_Aura = StatGroup.Immune | EffectType.Aura,
	Immune_Beast = StatGroup.Immune | EffectType.Beast,
	Immune_BeastForm = StatGroup.Immune | EffectType.BeastForm,
	Immune_ChannelDivinity = StatGroup.Immune | EffectType.ChannelDivinity,
	Immune_Charm = StatGroup.Immune | EffectType.Charm,
	Immune_Conjuration = StatGroup.Immune | EffectType.Conjuration,
	Immune_Disease = StatGroup.Immune | EffectType.Disease,
	Immune_Fear = StatGroup.Immune | EffectType.Fear,
	Immune_FullDiscipline = StatGroup.Immune | EffectType.FullDiscipline,
	Immune_Healing = StatGroup.Immune | EffectType.Healing,
	Immune_Illusion = StatGroup.Immune | EffectType.Illusion,
	Immune_Invigorating = StatGroup.Immune | EffectType.Invigorating,
	Immune_Poison = StatGroup.Immune | EffectType.Poison,
	Immune_Polymorph = StatGroup.Immune | EffectType.Polymorph,
	Immune_Rage = StatGroup.Immune | EffectType.Rage,
	Immune_Rattling = StatGroup.Immune | EffectType.Rattling,
	Immune_Reliable = StatGroup.Immune | EffectType.Reliable,
	Immune_Runic = StatGroup.Immune | EffectType.Runic,
	Immune_Sleep = StatGroup.Immune | EffectType.Sleep,
	Immune_Spirit = StatGroup.Immune | EffectType.Spirit,
	Immune_Stance = StatGroup.Immune | EffectType.Stance,
	Immune_Summoning = StatGroup.Immune | EffectType.Summoning,
	Immune_Teleportation = StatGroup.Immune | EffectType.Teleportation,
	Immune_Zone = StatGroup.Immune | EffectType.Zone,

	//Immune DamageType
	Immune_Physical = StatGroup.Immune | DamageType.Physical,
	Immune_Acid = StatGroup.Immune | DamageType.Acid,
	Immune_Cold = StatGroup.Immune | DamageType.Cold,
	Immune_Fire = StatGroup.Immune | DamageType.Fire,
	Immune_Force = StatGroup.Immune | DamageType.Force,
	Immune_Lightning = StatGroup.Immune | DamageType.Lightning,
	Immune_Necrotic = StatGroup.Immune | DamageType.Necrotic,
	Immune_Psychic = StatGroup.Immune | DamageType.Psychic,
	Immune_Radiant = StatGroup.Immune | DamageType.Radiant,
	Immune_Thunder = StatGroup.Immune | DamageType.Thunder,
	Immune_Toxin = StatGroup.Immune | DamageType.Toxin,
	Immune_Weapon = StatGroup.Immune | DamageType.Weapon,

	//Resist DamageType
	Resist_Physical = StatGroup.Resist | DamageType.Physical,
	Resist_Acid = StatGroup.Resist | DamageType.Acid,
	Resist_Cold = StatGroup.Resist | DamageType.Cold,
	Resist_Fire = StatGroup.Resist | DamageType.Fire,
	Resist_Force = StatGroup.Resist | DamageType.Force,
	Resist_Lightning = StatGroup.Resist | DamageType.Lightning,
	Resist_Necrotic = StatGroup.Resist | DamageType.Necrotic,
	Resist_Psychic = StatGroup.Resist | DamageType.Psychic,
	Resist_Radiant = StatGroup.Resist | DamageType.Radiant,
	Resist_Thunder = StatGroup.Resist | DamageType.Thunder,
	Resist_Toxin = StatGroup.Resist | DamageType.Toxin,
	Resist_Weapon = StatGroup.Resist | DamageType.Weapon,

	//Vulnerable DamageType
	Vulnerable_Physical = StatGroup.Vulnerable | DamageType.Physical,
	Vulnerable_Acid = StatGroup.Vulnerable | DamageType.Acid,
	Vulnerable_Cold = StatGroup.Vulnerable | DamageType.Cold,
	Vulnerable_Fire = StatGroup.Vulnerable | DamageType.Fire,
	Vulnerable_Force = StatGroup.Vulnerable | DamageType.Force,
	Vulnerable_Lightning = StatGroup.Vulnerable | DamageType.Lightning,
	Vulnerable_Necrotic = StatGroup.Vulnerable | DamageType.Necrotic,
	Vulnerable_Psychic = StatGroup.Vulnerable | DamageType.Psychic,
	Vulnerable_Radiant = StatGroup.Vulnerable | DamageType.Radiant,
	Vulnerable_Thunder = StatGroup.Vulnerable | DamageType.Thunder,
	Vulnerable_Toxin = StatGroup.Vulnerable | DamageType.Toxin,
	Vulnerable_Weapon = StatGroup.Vulnerable | DamageType.Weapon,

	//OngoingDamage DamageType
	OngoingDamage_Physical = StatGroup.OngoingDamage | DamageType.Physical,
	OngoingDamage_Acid = StatGroup.OngoingDamage | DamageType.Acid,
	OngoingDamage_Cold = StatGroup.OngoingDamage | DamageType.Cold,
	OngoingDamage_Fire = StatGroup.OngoingDamage | DamageType.Fire,
	OngoingDamage_Force = StatGroup.OngoingDamage | DamageType.Force,
	OngoingDamage_Lightning = StatGroup.OngoingDamage | DamageType.Lightning,
	OngoingDamage_Necrotic = StatGroup.OngoingDamage | DamageType.Necrotic,
	OngoingDamage_Psychic = StatGroup.OngoingDamage | DamageType.Psychic,
	OngoingDamage_Radiant = StatGroup.OngoingDamage | DamageType.Radiant,
	OngoingDamage_Thunder = StatGroup.OngoingDamage | DamageType.Thunder,
	OngoingDamage_Toxin = StatGroup.OngoingDamage | DamageType.Toxin,
	OngoingDamage_Weapon = StatGroup.OngoingDamage | DamageType.Weapon,

	//DamageType DamageType
	DamageType_Physical = StatGroup.DamageType | DamageType.Physical,
	DamageType_Acid = StatGroup.DamageType | DamageType.Acid,
	DamageType_Cold = StatGroup.DamageType | DamageType.Cold,
	DamageType_Fire = StatGroup.DamageType | DamageType.Fire,
	DamageType_Force = StatGroup.DamageType | DamageType.Force,
	DamageType_Lightning = StatGroup.DamageType | DamageType.Lightning,
	DamageType_Necrotic = StatGroup.DamageType | DamageType.Necrotic,
	DamageType_Psychic = StatGroup.DamageType | DamageType.Psychic,
	DamageType_Radiant = StatGroup.DamageType | DamageType.Radiant,
	DamageType_Thunder = StatGroup.DamageType | DamageType.Thunder,
	DamageType_Toxin = StatGroup.DamageType | DamageType.Toxin,
	DamageType_Weapon = StatGroup.DamageType | DamageType.Weapon,

	//WeaponProf WeaponProf
	WeaponProf_SimpleMelee = StatGroup.WeaponProf | WeaponProf.SimpleMelee,
	WeaponProf_MilitaryMelee = StatGroup.WeaponProf | WeaponProf.MilitaryMelee,
	WeaponProf_SuperiorMelee = StatGroup.WeaponProf | WeaponProf.SuperiorMelee,
	WeaponProf_ImprovisedMelee = StatGroup.WeaponProf | WeaponProf.ImprovisedMelee,
	WeaponProf_SimpleRanged = StatGroup.WeaponProf | WeaponProf.SimpleRanged,
	WeaponProf_MilitaryRanged = StatGroup.WeaponProf | WeaponProf.MilitaryRanged,
	WeaponProf_SuperiorRanged = StatGroup.WeaponProf | WeaponProf.SuperiorRanged,
	WeaponProf_ImprovisedRanged = StatGroup.WeaponProf | WeaponProf.ImprovisedRanged,

	//Combat Combat
	Combat_Initiative = StatGroup.Combat | Combat.Initiative,
	Combat_Attack = StatGroup.Combat | Combat.Attack,
	Combat_AttackDamage = StatGroup.Combat | Combat.AttackDamage,
	Combat_ThreateningReach = StatGroup.Combat | Combat.ThreateningReach,
	Combat_Regeneration = StatGroup.Combat | Combat.Regeneration,

	//ActionType ActionType
	ActionType_Standard = StatGroup.ActionType | ActionType.Standard,
	ActionType_Move = StatGroup.ActionType | ActionType.Move,
	ActionType_Minor = StatGroup.ActionType | ActionType.Minor,
	ActionType_Free = StatGroup.ActionType | ActionType.Free,
	ActionType_Immediate = StatGroup.ActionType | ActionType.Immediate,
	ActionType_Opportunity = StatGroup.ActionType | ActionType.Opportunity,
	ActionType_ActionPoint = StatGroup.ActionType | ActionType.ActionPoint,

	//Condition Condition
	Condition_Blinded = StatGroup.Condition | Condition.Blinded,
	Condition_Dazed = StatGroup.Condition | Condition.Dazed,
	Condition_Deafened = StatGroup.Condition | Condition.Deafened,
	Condition_Dominated = StatGroup.Condition | Condition.Dominated,
	Condition_Dying = StatGroup.Condition | Condition.Dying,
	Condition_Grabbed = StatGroup.Condition | Condition.Grabbed,
	Condition_Helpless = StatGroup.Condition | Condition.Helpless,
	Condition_Immobilized = StatGroup.Condition | Condition.Immobilized,
	Condition_Marked = StatGroup.Condition | Condition.Marked,
	Condition_Petrified = StatGroup.Condition | Condition.Petrified,
	Condition_Prone = StatGroup.Condition | Condition.Prone,
	Condition_RemovedFromPlay = StatGroup.Condition | Condition.RemovedFromPlay,
	Condition_Restrained = StatGroup.Condition | Condition.Restrained,
	Condition_Slowed = StatGroup.Condition | Condition.Slowed,
	Condition_Stunned = StatGroup.Condition | Condition.Stunned,
	Condition_Surprised = StatGroup.Condition | Condition.Surprised,
	Condition_Unconcious = StatGroup.Condition | Condition.Unconcious,
	Condition_Weakened = StatGroup.Condition | Condition.Weakened,
	Condition_Invisible = StatGroup.Condition | Condition.Invisible,

	//PowerUsed Power
	PowerUsed_DwarvenSecondWind = StatGroup.PowerUsed | Power.DwarvenSecondWind,
	PowerUsed_ElvenAccuracy = StatGroup.PowerUsed | Power.ElvenAccuracy,
	PowerUsed_ElvenGrace = StatGroup.PowerUsed | Power.ElvenGrace,
	PowerUsed_Cleave = StatGroup.PowerUsed | Power.Cleave,
	PowerUsed_ReapingStrike = StatGroup.PowerUsed | Power.ReapingStrike,
	PowerUsed_SureStrike = StatGroup.PowerUsed | Power.SureStrike,
	PowerUsed_TideOfIron = StatGroup.PowerUsed | Power.TideOfIron,
	PowerUsed_CoveringAttack = StatGroup.PowerUsed | Power.CoveringAttack,
	PowerUsed_PassingAttack = StatGroup.PowerUsed | Power.PassingAttack,
	PowerUsed_SpinningSweep = StatGroup.PowerUsed | Power.SpinningSweep,
	PowerUsed_SteelStrike = StatGroup.PowerUsed | Power.SteelStrike,
	PowerUsed_BruteStrike = StatGroup.PowerUsed | Power.BruteStrike,
	PowerUsed_ComebackStrike = StatGroup.PowerUsed | Power.ComebackStrike,
	PowerUsed_VillainsMenace = StatGroup.PowerUsed | Power.VillainsMenace,
	PowerUsed_BoundlessEndurance = StatGroup.PowerUsed | Power.BoundlessEndurance,
	PowerUsed_GetOverHere = StatGroup.PowerUsed | Power.GetOverHere,
	PowerUsed_NoOpening = StatGroup.PowerUsed | Power.NoOpening,
	PowerUsed_Unstoppable = StatGroup.PowerUsed | Power.Unstoppable,
	PowerUsed_ScoutCarefulAttack = StatGroup.PowerUsed | Power.ScoutCarefulAttack,
	PowerUsed_ScoutHitAndRun = StatGroup.PowerUsed | Power.ScoutHitAndRun,
	PowerUsed_ScoutNimbleStrike = StatGroup.PowerUsed | Power.ScoutNimbleStrike,
	PowerUsed_ScoutTwinStrike = StatGroup.PowerUsed | Power.ScoutTwinStrike,
	PowerUsed_ScoutDireStrike = StatGroup.PowerUsed | Power.ScoutDireStrike,
	PowerUsed_ScoutEvasiveStrike = StatGroup.PowerUsed | Power.ScoutEvasiveStrike,
	PowerUsed_ScoutCunningStrike = StatGroup.PowerUsed | Power.ScoutCunningStrike,
	PowerUsed_ScoutDoubleStrike = StatGroup.PowerUsed | Power.ScoutDoubleStrike,
	PowerUsed_ScoutHuntersTrap = StatGroup.PowerUsed | Power.ScoutHuntersTrap,
	PowerUsed_ScoutPincerStrike = StatGroup.PowerUsed | Power.ScoutPincerStrike,
	PowerUsed_ScoutSplitStrike = StatGroup.PowerUsed | Power.ScoutSplitStrike,
	PowerUsed_ScoutSuddenStrike = StatGroup.PowerUsed | Power.ScoutSuddenStrike,
	PowerUsed_ScoutCrucialAdvice = StatGroup.PowerUsed | Power.ScoutCrucialAdvice,
	PowerUsed_ScoutUnbalancingParry = StatGroup.PowerUsed | Power.ScoutUnbalancingParry,
	PowerUsed_ScoutYieldGround = StatGroup.PowerUsed | Power.ScoutYieldGround,
	PowerUsed_InspiringWord = StatGroup.PowerUsed | Power.InspiringWord,
	PowerUsed_CommandersStrike = StatGroup.PowerUsed | Power.CommandersStrike,
	PowerUsed_FuriousSmash = StatGroup.PowerUsed | Power.FuriousSmash,
	PowerUsed_TacticalStrike = StatGroup.PowerUsed | Power.TacticalStrike,
	PowerUsed_PackTactics = StatGroup.PowerUsed | Power.PackTactics,
	PowerUsed_GuardingAttack = StatGroup.PowerUsed | Power.GuardingAttack,
	PowerUsed_HammerAndAnvil = StatGroup.PowerUsed | Power.HammerAndAnvil,
	PowerUsed_NoQuarter = StatGroup.PowerUsed | Power.NoQuarter,
	PowerUsed_OfficersFavor = StatGroup.PowerUsed | Power.OfficersFavor,
	PowerUsed_BastionOfDefense = StatGroup.PowerUsed | Power.BastionOfDefense,
	PowerUsed_LeadTheAttack = StatGroup.PowerUsed | Power.LeadTheAttack,
	PowerUsed_PinTheFoe = StatGroup.PowerUsed | Power.PinTheFoe,
	PowerUsed_TeamOnslaught = StatGroup.PowerUsed | Power.TeamOnslaught,
	PowerUsed_AidTheInjured = StatGroup.PowerUsed | Power.AidTheInjured,
	PowerUsed_CrescendoOfViolence = StatGroup.PowerUsed | Power.CrescendoOfViolence,
	PowerUsed_KnightsMove = StatGroup.PowerUsed | Power.KnightsMove,
	PowerUsed_ShakeItOff = StatGroup.PowerUsed | Power.ShakeItOff,
	PowerUsed_CarefulAttack = StatGroup.PowerUsed | Power.CarefulAttack,
	PowerUsed_HitAndRun = StatGroup.PowerUsed | Power.HitAndRun,
	PowerUsed_NimbleStrike = StatGroup.PowerUsed | Power.NimbleStrike,
	PowerUsed_TwinStrike = StatGroup.PowerUsed | Power.TwinStrike,
	PowerUsed_EvasiveStrike = StatGroup.PowerUsed | Power.EvasiveStrike,
	PowerUsed_CunningStrike = StatGroup.PowerUsed | Power.CunningStrike,
	PowerUsed_DoubleStrike = StatGroup.PowerUsed | Power.DoubleStrike,
	PowerUsed_HuntersTrap = StatGroup.PowerUsed | Power.HuntersTrap,
	PowerUsed_PincerStrike = StatGroup.PowerUsed | Power.PincerStrike,
	PowerUsed_SplitStrike = StatGroup.PowerUsed | Power.SplitStrike,
	PowerUsed_SuddenStrike = StatGroup.PowerUsed | Power.SuddenStrike,
	PowerUsed_CrucialAdvice = StatGroup.PowerUsed | Power.CrucialAdvice,
	PowerUsed_UnbalancingParry = StatGroup.PowerUsed | Power.UnbalancingParry,
	PowerUsed_YieldGround = StatGroup.PowerUsed | Power.YieldGround,
	PowerUsed_DecrepitSkeleton_Longsword = StatGroup.PowerUsed | Power.DecrepitSkeleton_Longsword,
	PowerUsed_DecrepitSkeleton_Shortbow = StatGroup.PowerUsed | Power.DecrepitSkeleton_Shortbow,
	PowerUsed_Skeleton_Longsword = StatGroup.PowerUsed | Power.Skeleton_Longsword,
	PowerUsed_BlazingSkeleton_BlazingClaw = StatGroup.PowerUsed | Power.BlazingSkeleton_BlazingClaw,
	PowerUsed_BlazingSkeleton_FlameOrb = StatGroup.PowerUsed | Power.BlazingSkeleton_FlameOrb,
	PowerUsed_BoneshardSkeleton_Scimitar = StatGroup.PowerUsed | Power.BoneshardSkeleton_Scimitar,
	PowerUsed_BoneshardSkeleton_Boneshard = StatGroup.PowerUsed | Power.BoneshardSkeleton_Boneshard,
	PowerUsed_BoneshardSkeleton_BoneshardBurst = StatGroup.PowerUsed | Power.BoneshardSkeleton_BoneshardBurst,
	PowerUsed_SecondWind = StatGroup.PowerUsed | Power.SecondWind,
	PowerUsed_TotalDefense = StatGroup.PowerUsed | Power.TotalDefense,
	PowerUsed_StandUp = StatGroup.PowerUsed | Power.StandUp,
	PowerUsed_DropProne = StatGroup.PowerUsed | Power.DropProne,
	PowerUsed_Walk = StatGroup.PowerUsed | Power.Walk,
	PowerUsed_Shift = StatGroup.PowerUsed | Power.Shift,
	PowerUsed_SpendActionPoint = StatGroup.PowerUsed | Power.SpendActionPoint,
	PowerUsed_OpportunityAttack = StatGroup.PowerUsed | Power.OpportunityAttack,
	PowerUsed_Skeleton_FeyStep = StatGroup.PowerUsed | Power.Skeleton_FeyStep,
	PowerUsed_HobgoblinResilience = StatGroup.PowerUsed | Power.HobgoblinResilience,
	PowerUsed_HobgoblinGrunt_Longsword = StatGroup.PowerUsed | Power.HobgoblinGrunt_Longsword,
	PowerUsed_HobgoblinArcher_Longsword = StatGroup.PowerUsed | Power.HobgoblinArcher_Longsword,
	PowerUsed_HobgoblinArcher_Longbow = StatGroup.PowerUsed | Power.HobgoblinArcher_Longbow,
	PowerUsed_HobgoblinSoldier_Flail = StatGroup.PowerUsed | Power.HobgoblinSoldier_Flail,
	PowerUsed_HobgoblinSoldier_FormationStrike = StatGroup.PowerUsed | Power.HobgoblinSoldier_FormationStrike,
	PowerUsed_OrcRaider_Greataxe = StatGroup.PowerUsed | Power.OrcRaider_Greataxe,
	PowerUsed_OrcRaider_Handaxe = StatGroup.PowerUsed | Power.OrcRaider_Handaxe,
	PowerUsed_OrcRaider_WarriorsSurge = StatGroup.PowerUsed | Power.OrcRaider_WarriorsSurge,
	PowerUsed_Imp_Bite = StatGroup.PowerUsed | Power.Imp_Bite,
	PowerUsed_Imp_TailSting = StatGroup.PowerUsed | Power.Imp_TailSting,
	PowerUsed_Imp_TailStingSecondary = StatGroup.PowerUsed | Power.Imp_TailStingSecondary,
	PowerUsed_Imp_Vanish = StatGroup.PowerUsed | Power.Imp_Vanish,
	PowerUsed_Gravehound_Bite = StatGroup.PowerUsed | Power.Gravehound_Bite,
	PowerUsed_Gravehound_DeathJaws = StatGroup.PowerUsed | Power.Gravehound_DeathJaws,
	PowerUsed_ZombieRotter_Slam = StatGroup.PowerUsed | Power.ZombieRotter_Slam,

[WhiteShark]

I'm not sure how I will go about visually representing other effects like ongoing damage or temporary buffs yet.

Buffs may be harder since they're not standardized, but, for ongoing damage, perhaps you could dynamically generate an icon of a colored number, the color representing the damage type and the number representing the amount.

[J1M]

I'm not sure how I will go about visually representing other effects like ongoing damage or temporary buffs yet.

Buffs may be harder since they're not standardized, but, for ongoing damage, perhaps you could dynamically generate an icon of a colored number, the color representing the damage type and the number representing the amount.

I like that idea.

[Kalarion]

One-time disclaimer: I am a hobbyist. Never worked in the game industry professionally, never completed a project to the point of putting it on a storefront. I'll place any technical details after the screenshot/video so those only interested in the progress can easily bypass those details.

...

Why this disclaimer? Are there rumblings that necessitated it?

There's no simple "everything stacks" or "everything is an additive or multiplicative bonus". There are all sorts of conditional effects that mean that an effect needs to be aware of the entire encounter state in order to know if it applies. Examples:

...

Do you foresee this causing processing bottlenecks or requiring sacrifices?

[J1M]

One-time disclaimer: I am a hobbyist. Never worked in the game industry professionally, never completed a project to the point of putting it on a storefront. I'll place any technical details after the screenshot/video so those only interested in the progress can easily bypass those details.

...

Why this disclaimer? Are there rumblings that necessitated it?

There's no simple "everything stacks" or "everything is an additive or multiplicative bonus". There are all sorts of conditional effects that mean that an effect needs to be aware of the entire encounter state in order to know if it applies. Examples:

...

Do you foresee this causing processing bottlenecks or requiring sacrifices?

The disclaimer is there because I'm going to drop into an authoritative tone when talking about my own project and I don't want this thread to become arguing about component-entity systems and whether or not a game engine should have a scripting language.

The conditional effects are more of an issue related to the complication of implementation and ensuring the rules are resolved in a way that matches what would be expected at a kitchen table. I don't anticipate needing to worry about performance in that way, but if I do there are optimizations I can explore. Simple example: the existence of an effect like "extra critical damage dice" means that either a) the generic way of calculating damage from an ability needs to assume every power could have this and all powers need data defined for that property or b) there needs to be a mechanism to inject a modification to how much damage a power does (but only if the attack roll was a crit). TLDR: it increases complexity more than its a performance problem.

I'll talk more about this in a future post, but even the existence of "extra damage dice" instead of "extra flat damage" adds additional complexity and prevents certain approaches of implementation because the value isn't known until it happens.

[J1M]

I'm not sure how I will go about visually representing other effects like ongoing damage or temporary buffs yet.

Buffs may be harder since they're not standardized, but, for ongoing damage, perhaps you could dynamically generate an icon of a colored number, the color representing the damage type and the number representing the amount.

I like that idea.

Seems like a good opportunity for a bikeshedding conversation. I suppose gray could be added to the potential choices, but I didn't want to use it unless it was necessary. That won't be the icon, it's just a color test.

[WhiteShark]

Could Radiant be made white and Necrotic black? If so, you could then move Radiant's yellow over to Lightning, move Lightning's current blue over to Force, and move Necrotic's purple over to Thunder.

Acid's color is appropriate, but it looks deceptively close to Poison's color, at least to me on my monitor. Maybe that's something that can be tweaked with brightness.