[Extension] - 5E - AGGRO: Smart Targeting System for NPCs

Forge Link: https://forge.fantasygrounds.com/shop/items/2021/view

Introducing Aggro – Smart Targeting for NPCs in Fantasy Grounds

Are your players constantly shouting, "Why is he attacking me instead of the barbarian?"
Are you a DM who wants to enjoy impartial targeting while battling it out in an arena with your players?
Or are you simply looking for a way to streamline combat decisions without overthinking?

Well… this is for you!

---

https://i.imgur.com/k3u34bL.jpeg

Aggro is a new extension designed to bring intelligent, automated targeting to your games. By using customizable variables with adjustable weights, it calculates targeting priorities for NPCs. At the start of an NPC's turn, Aggro determines targets based on probability—higher Aggro values mean a greater chance of being selected.

---

Key Features

Two Targeting Systems

• Logical Chance: Target selection remains random, but higher threat levels significantly increase the chances of being targeted. This maintains a balance of consistency and unpredictability.
• Pure Logical: The actor with the highest threat level is always selected as the target.

Choose between Auto Target or Target Advisor

• Auto Target will do the calculations and auto select the target for you.
• Target Advisor will calculate the aggro values, but will not select target, instead, it will advise you of the best option (better with "Pure Logical")

You can also choose whether to display full threat calculations in the chat or only the final target selection message.

https://i.imgur.com/J5kxjB5.jpeg

https://i.imgur.com/pkjLLAp.jpeg

---

Customizable Threat Variables

Aggro's targeting system is powered by the following variables, all adjustable via the Options menu:

• Base Value: A default Aggro value assigned to all actors at the start of a turn. Think of it as a "random motive" factor.
• Proximity Threat: Closer targets receive higher Aggro values. The nearest target gets 100%, the second-closest gets 50%, the third 25%, and so on.
• Damage Threat: Targets that deal the most damage to the NPC are prioritized. The top-ranked actor receives 100% of the damage Aggro, with subsequent ranks halving the previous value.
• Persistence Threat: Actors already targeted in previous turns gain this Aggro value, ensuring consistent NPC behavior.
• Critical Hit Threat: Actors who land a critical hit on the NPC gain increased Threat until the NPC's next turn.
• Miss Penalty: Each time an NPC misses a target, that target's Aggro decreases. This penalty is cumulative and resets upon a successful hit, making difficult-to-hit targets less attractive.
• Out of Reach Penalty: Targets outside the NPC’s base movement range (or effective attack range) have their Aggro reduced by 100%. Targets beyond dashing range (or maximum range) receive triple this penalty, making faraway targets less appealing.
• Injured Opponent Penalty: Bloodied actors (50% HP or less) have their Aggro reduced by 100%, while wounded actors (more than 50% HP but not full) receive half the penalty.
• Minimum Target Value: Prevents an actor’s Aggro from dropping to 0 or below, ensuring they remain a potential target.
• NPC Cruelty: Determines if dying actors (0 HP) are valid targets. When turned off, NPCs will ignore actors with 0 HP.

Don’t like a variable? Set its value to 0, and it will no longer affect targeting.

https://i.imgur.com/g0KEmgU.jpeg

---

New Effects: AGGRO, INDEPENDENT, NOTHREAT, CRUEL

Usage: AGGRO: [n]
Where [n] is a number (positive or negative) that adjusts the target’s Aggro value.
Examples:

Code:

---

Taunt: AGGRO: 300

---

– Increase a target's Aggro by 300.

Code:

---

Innocent Face: AGGRO: -200

---

– Decrease a target's Aggro by 200.

INDEPENDENT: Skip threat calculation and auto targeting. Use it for manual targeting.

NOTHREAT: Excludes the actor from the valid targets list.

CRUEL: Bypass the check for "NPCs Cruelty: off" for this particular NPC.

---

Important Notes

• Always drag tokens from the Combat Tracker to the map. Dragging tokens directly from a PC sheet or NPC list will prevent the extension from functioning properly.
• This extension is not compatible with language translations, as it depends on capturing certain messages from the ruleset to work properly.

---

Changelog

1.5.0
New Feature

• Users can now configure which factions are eligible to roll for AGGRO.

UI Refinements

• Threat values now have their own configuration window to avoid cluttering the Fantasy Grounds Options menu.
• The AGGRO token widget can now be set to always on, always off, or shown only when hovering over a token.
• The widget position and size can be chosen by the user.

Bug Fixes

• Discreet mode for the host was behaving like Verbose mode. FIXED.

1.4.1
Changes/Bug Fixes:

• Fixed certain features, such as spellcasting, critical hits, and damage threat, not being accounted for in client rolls.
• Fixed system messages notifying clients about the initial threat value options.
• Changed the extension settings so they are visible only to the host, preventing clients from seeing threat values.

1.4.0
New Features:

• LoS-Aware Aggro: Characters will not be listed as potential targets if they do not have line of sight to the current actor (don't forget to activate this in the options windows and turn LoS on in the image).
• Opportunity Attack-Aware Aggro: Intelligent actors will avoid targeting characters when doing so would trigger opportunity attacks. Optimized for 5E.
• New Threat Modifier: Legacy: Carries over a percentage of the previous threat value to the next turn if the new value is lower.
• Target Priority Widget: Displays a skull icon above the tokens of the top three targets to help the GM choose between them. This is especially useful when automatic targeting is disabled.
• Expanded support for spells in Pathfinder 1 and 2.
• Added Starfinder to the ruleset compatibility list. Although it is not officially supported, most, if not all, features should work due to its similarities to Pathfinder. Try at your own risk.

Also, multiple bug fixes.

1.3.0

New Features:

• Spellcasting Aggro! Caster receive the base spell threat value + additional level bonus (both customizable).
• Healing Aggro: also receive additional aggro based on healing level.
• Intelligence based aggro: Define the minimum intelligence to be considered 'intelligent' and 'rational'. Intelligent actors will calculate all variables plus spell and healing aggro. Rational actors will calculate everything but those two and irrational actor will only consider basic aggro modifiers.
• Neglected target aggro: Actors that are not being targeted by anyone will receive this bonus to threat.

1.2.1

New Features:

• 3 New Effects: INDEPENDENT, NOTHREAT and CRUEL.
• New feature to decide if attacked neutral NPCs engage in battle.
• New target advisor mode to show aggro calculations without actually targeting.

Fixes an Small Changes:

• Fixed effective and max range calculations for melee combatants.
• Renamed options.

1.1.2

Fixes:

• Fixed a bug related to tied actors with the same threat modifiers resulting in a console error and no target selected when in "Pure Logical" mode.

1.1.1

New Features:

• NPCs now have the option to target any actor in Combat Tracker. (Select between "PC Only", "Any Friendly" or "All But Hostile").
• Added a option to choose the target message's display mode for players.
• Included a message feedback in Verbose mode to show the current NPC effective and maximum range. (If the NPC has no ranged attack, effective range is NPC speed + reach. Maximum range is NPC speed x 2 + reach. For ranged attacks, it takes the effective and maximum range from the weapon or ranged spell attack. If there is only a single value for range, maximum range = effective range.)

Fixes:

• Fixed "Injured" threat bonus displayed as a penalty.
• Fixed console error when NPC ranged attack have only one range value.

1.0

• Initial Release

Coming Next
Exciting future updates include:

• Status Effects Threat: Assign custom threat values to statuses like Invisible, Dash, Prone, Paralyzed, etc.
• Improved Range Calculation: Incorporate save-based spells and powers, like dragon's breath, into the "Out of Reach" penalty.
• NPCs Quirks: A chance to randomly assign an effect to a NPC representing some personal beef or soft spot, like: "HATES: Dwarves" (Dwarves get threat +200 against him), "LOVES: TINY" (Tiny sized actors receive -200 threat against him).

I'm constantly checking this post to see the feedback and suggestions to update this list.

---

Have Suggestions or Found a Bug?

I’d love to hear your feedback! Reply to this post with your thoughts or report any issues you encounter.

Want to be a beta tester for future versions? Send me a message!

This has a lot of potential.

This is super cool.

Interesting concept. Nice work.

Very cool!

I really won't be able to use it until it can target NPCs, unfortunately, as my groups are always running around with extras (who should often be juicy targets).

Does "11-Injured Opponent Penalty" make it so the monster is less likely to try to finish off a bloodied opponent? If so it's really the only one that stands out as counterintuitive at a glance...

I would love to see another option for 'Message Visibility' to be able to have either discreet or verbose but optionally not broadcast to players.

Quote:

---

Originally Posted by rocketvaultgames

I really won't be able to use it until it can target NPCs, unfortunately, as my groups are always running around with extras (who should often be juicy targets).

---

I'm working on expand the effect to all actors in scene right now. I may update this extension sooner than i thought.

Quote:

---

Does "11-Injured Opponent Penalty" make it so the monster is less likely to try to finish off a bloodied opponent? If so it's really the only one that stands out as counterintuitive at a glance...

---

It's the opposite. Wounded and bloodied targets are more likely to be targeted because they are viewed as weak. I don't know why i called it a penalty, its really a bonus to threat levels. It will be fixed in next version.

Quote:

---

I would love to see another option for 'Message Visibility' to be able to have either discreet or verbose but optionally not broadcast to players.

---

That makes sense. Should be easy to implement.

Quote:

---

Originally Posted by Alanrockid

I'm working on expand the effect to all actors in scene right now. I may update this extension sooner than i thought.



It's the opposite. Wounded and bloodied targets are more likely to be targeted because they are viewed as weak. I don't know why i called it a penalty, its really a bonus to threat levels. It will be fixed in next version.



That makes sense. Should be easy to implement.

---

That all sounds fantastic. I'm definitely excited about the future possibilities for this extension!

Regarding Message Visibility: I'm not sure it's worth the complexity, but I could see a situation where some users would prefer Discreet for Players and Verbose for GM, so having separate options for Player and GM with all 3 options each might be best:

Players - Muted / Discreet / Verbose
GM - Muted / Discreet / Verbose

Very interesting concept. Of course, the end game for something like this would be for the extension to actually set the targeting for the active NPC creature with the most aggro so all you have to do is roll.

Quote:

---

Originally Posted by Griogre

Very interesting concept. Of course, the end game for something like this would be for the extension to actually set the targeting for the active NPC creature with the most aggro so all you have to do is roll.

---

You mean the extension selecting the target for player characters as well?

I was just thinking monsters selecting party members with FGU's targeting rather than just a chat message. I prefer players to have more agency.

Quote:

---

Originally Posted by Griogre

I was just thinking monsters selecting party members with FGU's targeting rather than just a chat message. I prefer players to have more agency.

---

It's not just a message, the NPC should actually target the characters, the text is just for clarification of the chances and motives. Or isn't working like that for you?

I'm looking forward to it. I bought this as soon as I saw it and will now finally get to use it, tonight. A thought (and one you probably already had from the sounds of it), if a wizard is dropping fireballs and scorching everyone, that should draw some attention. Also, I'm not sure if this would be attainable but most intelligent creatures would definitely look to take out spellcasters ASAP so I'm not sure if that could be factored in, too.

Quote:

---

Originally Posted by Dax Doomslayer

I'm looking forward to it. I bought this as soon as I saw it and will now finally get to use it, tonight. A thought (and one you probably already had from the sounds of it), if a wizard is dropping fireballs and scorching everyone, that should draw some attention. Also, I'm not sure if this would be attainable but most intelligent creatures would definitely look to take out spellcasters ASAP so I'm not sure if that could be factored in, too.

---

Yes, NPC intelligence affecting how it perceives threats is in my plans for a future update, just not the priority right now, as there are some other features that i would like to implement first.

Spells are a little bit trickier because the current system searches for specific patterns in the NPC actions that are not really homogeneous for spells. Also, i need to implement some way to distinguish if a saving throw spell is actually threatening (casting zone of truth in the middle of combat is not exactly menacing). Ranged spell attacks are working fine, though.

Some cool features i would like to implement in future versions besides the ones I've listed on the original post are:

- Spell Level Threat: The higher the level of the spell cast, the bigger the threat.
- NPCs Quirks: A chance to randomly assign an effect to a NPC representing some personal beef, like: "HATES: Dwarves" (Dwarves get threat +200 against him), "LOVES: TINY" (Tiny sized actors receive -200 threat against him).
- Healer Threat: "Yeah...we need to take out this bastard that keep bringing the Barbarian back to combat."

Quote:

---

Originally Posted by Alanrockid

Yes, NPC intelligence affecting how it perceives threats is in my plans for a future update, just not the priority right now, as there are some other features that i would like to implement first.

Spells are a little bit trickier because the current system searches for specific patterns in the NPC actions that are not really homogeneous for spells. Also, i need to implement some way to distinguish if a saving throw spell is actually threatening (casting zone of truth in the middle of combat is not exactly menacing). Ranged spell attacks are working fine, though.

Some cool features i would like to implement in future versions besides the ones I've listed on the original post are:

- Spell Level Threat: The higher the level of the spell cast, the bigger the threat.
- NPCs Quirks: A chance to randomly assign an effect to a NPC representing some personal beef, like: "HATES: Dwarves" (Dwarves get threat +200 against him), "LOVES: TINY" (Tiny sized actors receive -200 threat against him).
- Healer Threat: "Yeah...we need to take out this bastard that keep bringing the Barbarian back to combat."

---

This all seems great. I would suggest an option to turn off the auto targeting but keep the rest of the messaging.

I envision this being best acting essentially as the computer in an MMO and tracking 'threat'.... the beauty of the TTRPG is that the human can override what the computer spits out.

But it is fantastic to have that target suggestion served up to you every turn... maybe even an option to single click accept the suggested target(s) would be good...


I have not had time to test compatibility with other extensions at all, but running with AGGRO on but muted for tonight's session, it did spit an error to the GM on NPC turns (with 100 other extensions running):

Attachment 63104

And I was seeing (GM side only) some graphical issues that may or may not be related to AGGRO (but wasn't happening yesterday before AGGRO) where the health bars and targeting arrows would be offset from tokens... moving the tokens snapped them back. Not sure of the rhyme or reason at this point.

Attachment 63105

Quote:

---

Originally Posted by rocketvaultgames

This all seems great. I would suggest an option to turn off the auto targeting but keep the rest of the messaging.

I envision this being best acting essentially as the computer in an MMO and tracking 'threat'.... the beauty of the TTRPG is that the human can override what the computer spits out.

But it is fantastic to have that target suggestion served up to you every turn... maybe even an option to single click accept the suggested target(s) would be good...


I have not had time to test compatibility with other extensions at all, but running with AGGRO on but muted for tonight's session, it did spit an error to the GM on NPC turns (with 100 other extensions running):

Attachment 63104

And I was seeing (GM side only) some graphical issues that may or may not be related to AGGRO (but wasn't happening yesterday before AGGRO) where the health bars and targeting arrows would be offset from tokens... moving the tokens snapped them back. Not sure of the rhyme or reason at this point.

Attachment 63105

---

Line 328 is calculating distance, reach and max range. A nil value in one of them could mean the original distance methods were modified by some extension, the token was moved to the map from anywhere else but the CT or, my main guess: The function did find a ranged attack in the NPCs actions, but it failed to capture the desired pattern.

To set the effective and maximum range for ranged attacks, the script searches for any action in that NPCs sheet that has "range, "ranged" or [R] on its description. Then, it captures the numbers inside the patterns "range [range]/[max range] ft" or "ranged [range]/[ranged] ft".

So if your NPC has a ranged attack written in some other format, it could cause that variable to be nil.

Can you confirm if that is the case?

(about the graphic glitch, i see no reason why this extension could cause it...maybe its a coincidence? :confused:)

Quote:

---

Originally Posted by Alanrockid

Line 308 is calculating distance, reach and max range. A nil value in one of them could mean the original distance methods were modified by some extension, the token was moved to the map from anywhere else but the CT or, my mains guess: The function did find a ranged attack in the NPCs actions, but it failed to capture the desired pattern.

To set the effective and maximum range for ranged attacks, the script searches for any action in that NPCs sheet that has "range, "ranged" or [R] on its description. Then, it captures the numbers inside the patterns "range [range]/[max range] ft" or "ranged [range]/[ranged] ft".

So if your NPC has a ranged attack written in some other format, it could cause that variable to be nil.

Can you confirm if that is the case?

(about the graphic glitch, i see no reason why this extension could cause it...maybe its a coincidence? :confused:)

---

The token was definitely moved to the map from the CT.

Here's an NPC that is throwing the error:

Attachment 63106

It is definitely possible that it is another extension's compatibility. I won't have time to look in depth until later this week at the earliest. I just wanted to mention it in case it was an obvious fix on your end.

I'll have to do some checking on the graphical glitch as well.

Quote:

---

Originally Posted by rocketvaultgames

The token was definitely moved to the map from the CT.

Here's an NPC that is throwing the error:

Attachment 63106

It is definitely possible that it is another extension's compatibility. I won't have time to look in depth until later this week at the earliest. I just wanted to mention it in case it was an obvious fix on your end.

I'll have to do some checking on the graphical glitch as well.

---

Yeah, it's exactly what I've imagined. The ranged attack of the NPC "Hurl Flame" has only one range: "range 150 ft.". The extension was expecting 2 values in the format [range]/[max_range].

I'll have to add some logic to just repeat the first value in case of the second value is nil. For now you can just edit the NPC action to be "range 150/150 ft." and you should be good.

Version updated:

Changelog
1.1.1
New Features:
NPCs now have the option to target any actor in Combat Tracker. (Select between "PC Only", "Any Friendly" or "All But Hostile").
Added a option to choose the target message's display mode for players.


Fixed:
Fixed "Injured" threat bonus displayed as a penalty.
Fixed console error when NPC ranged attack have only one range value.

Amazing extension! I am loving testing this out as the fighter goliath has a item I gave him to become pretty much the tank, a ring of the challenger, which I can create a custom aggro threat and then he can pretty much absorb the damage!

I have read the threads here and hope to see this extend to NPCs as well! I use a lot of NPCs and the adventuring party are all playable monster races, so the NPCs are not cut and dry that if a human is being attacked by a goblin then you will help the human. You have a goblin in your party and make moral decisions. So seeing how the aggro meter will look on each of them would be amazing!

Hello Alan,

I can only repeat what other already wrote: I see huge potentials in the Extension. The (biased) calculation is a significant help in large battles - having (as GM) the option to accept or not accept the choice would be nice, but since you can mute the output to the players now (with version 1.1.1) while getting the whole (verbose) calculation as GM, changing the target afterwards is no issue ;)

As Rocketvault already pointed out: there are some "early adopter's bugs":

1. The extension also sets targets for Player NPCs (conjured monsters, familiars, pack animals, etc.). As these NPCs are fully player controlled, they should not be part of the automation. Perhaps a similar option like for selection of targets would be possible (Select target for: "All NPCs", "Any Hostile", or "All But Friendly").
2. I have the following error in a specific situation with ONLY this extension loaded:
   
   Code:

   ---

   s'Saving aggro data...'
s'Aggro data save complete'
[ERROR] Script execution error: [string "Aggro:scripts/manager_aggro.lua":717: bad argument #1 to 'ipairs' (table expected, got nil)

   ---

   Situation on map: hostile where the error is generated when turn starts is adjacent to a player character and a player NPC (conjured "pet"). No target is selected for the hostile on turn start. Both adjacent tokens calculate the same threat value (200 - 100 from base, 100 from proximity). Issue is repeatable (moved turn counter back to last PC, advance turn - produces the same error) but vanishes if one token is selected as target before the turn.
   Error also occurs when one token is lifted 5' into the air which results into the same calculation, but vanishes when the token is lifted 10' (which changes its calculation to 150 - 100 base, 50 proximity). I therefore assume that the same calculation result causes the issue. Option for Target Selection is set to "Pure Logical". When set to "Logical Chance", surprisingly, none of the two is chosen as target but one of the next closer ones (150 - 100 from base, 50 from proximity).

Hope this helps in further debugging/development!

Quote:

---

I can only repeat what other already wrote: I see huge potentials in the Extension. The (biased) calculation is a significant help in large battles - having (as GM) the option to accept or not accept the choice would be nice, but since you can mute the output to the players now (with version 1.1.1) while getting the whole (verbose) calculation as GM, changing the target afterwards is no issue

---

As suggested, I'm implementing an option to switch between auto target or leave the aggro just as advice.

Quote:

---

1. The extension also sets targets for Player NPCs (conjured monsters, familiars, pack animals, etc.). As these NPCs are fully player controlled, they should not be part of the automation. Perhaps a similar option like for selection of targets would be possible (Select target for: "All NPCs", "Any Hostile", or "All But Friendly").

---

I'm working on an INDEPENDENT effect to make a NPC ignore the aggro calculations. That would be an easy fix for pets or allies controlled by players.

Quote:

---

[ERROR] Script execution error: [string "Aggro:scripts/manager_aggro.lua":717: bad argument #1 to 'ipairs' (table expected, got nil)

---

The line 717 and your description points to an error in the tiebreaker function for pure logical. I have a hunch about what is causing it and i'll fix it ASAP.

About "Logic Chance" selecting a third target other than that two, might be just pure chance. A higher aggro means higher chance of being targeted, but does not nullify the chance of a low aggro being selected if jinxed enough (and to be honest, a 50 threat difference is a very low value). :p Try to "force" an aggro to one of the two closer tokens with an AGGRO: 99999 effect to see if that was just a coincidence.

This may be a bit much for the extension, but is there any thought about negative weighing aggro for creatures that would suffer an Opportunity Attack if they were to go after a creature? Or having spellcasters generating more aggro for intelligent creatures? Just some thoughts. This is a pretty cool little extension!

Quote:

---

Originally Posted by Dax Doomslayer

This may be a bit much for the extension, but is there any thought about negative weighing aggro for creatures that would suffer an Opportunity Attack if they were to go after a creature? Or having spellcasters generating more aggro for intelligent creatures? Just some thoughts. This is a pretty cool little extension!

---

Spellcasting threat and intelligence based aggro are already on my todo list for future updates (spellcaster threat is probably coming first).

Checking for adjacent targets reaction (to prevent opportunity attacks) is something that i intended to do on the original release, but got delayed because of the level of complexity (mostly because it would require the intelligence based aggro). So, until the intelligence update is released, this feature is postponed... :p

Wow - that's terrific. This is definitely a neat little extension already!!

Quote:

---

Originally Posted by Arnagus

Hello Alan,

I can only repeat what other already wrote: I see huge potentials in the Extension. The (biased) calculation is a significant help in large battles - having (as GM) the option to accept or not accept the choice would be nice, but since you can mute the output to the players now (with version 1.1.1) while getting the whole (verbose) calculation as GM, changing the target afterwards is no issue ;)

As Rocketvault already pointed out: there are some "early adopter's bugs":

1. The extension also sets targets for Player NPCs (conjured monsters, familiars, pack animals, etc.). As these NPCs are fully player controlled, they should not be part of the automation. Perhaps a similar option like for selection of targets would be possible (Select target for: "All NPCs", "Any Hostile", or "All But Friendly").
2. I have the following error in a specific situation with ONLY this extension loaded:
   
   Code:

   ---

   s'Saving aggro data...'
s'Aggro data save complete'
[ERROR] Script execution error: [string "Aggro:scripts/manager_aggro.lua":717: bad argument #1 to 'ipairs' (table expected, got nil)

   ---

   Situation on map: hostile where the error is generated when turn starts is adjacent to a player character and a player NPC (conjured "pet"). No target is selected for the hostile on turn start. Both adjacent tokens calculate the same threat value (200 - 100 from base, 100 from proximity). Issue is repeatable (moved turn counter back to last PC, advance turn - produces the same error) but vanishes if one token is selected as target before the turn.
   Error also occurs when one token is lifted 5' into the air which results into the same calculation, but vanishes when the token is lifted 10' (which changes its calculation to 150 - 100 base, 50 proximity). I therefore assume that the same calculation result causes the issue. Option for Target Selection is set to "Pure Logical". When set to "Logical Chance", surprisingly, none of the two is chosen as target but one of the next closer ones (150 - 100 from base, 50 from proximity).

Hope this helps in further debugging/development!

---

The console error should be fixed with the new updated version. Thank you for your feedback!

Quote:

---

Originally Posted by Alanrockid

The console error should be fixed with the new updated version. Thank you for your feedback!

---

Thanks a lot! Confirmed that the issue is gone.

As for the AGGRO - any change away from the calculated 200 caused a target to be selected and the error to be gone. I can reproduce a random selection or targets with lower AGGRO than adjacent tokens, so the choice of the third token seem to have been pure chance. Nevertheless I was not able to reproduce a chance selection of any of the two adjacent tokens when both had the same AGGRO result. I tried 10 times, several different tokens were selected (from AGGRO 150 to 125) but not those two. With the update, any token (including the two adjacent) might be selected randomly, so issue is gone as well.

Quote:

---

Originally Posted by Alanrockid

I'm working on an INDEPENDENT effect to make a NPC ignore the aggro calculations. That would be an easy fix for pets or allies controlled by players.

---

That would do the trick indeed (although I need to find a way to apply the effect automatically to summoned monsters/conjured animals - perhaps cloning the NPCs specifically for those spells and adding an additional trait/ability "Summoned" for using EE to apply the effect).
Looking forward to have it. :)

Quote:

---

Originally Posted by Arnagus

That would do the trick indeed (although I need to find a way to apply the effect automatically to summoned monsters/conjured animals - perhaps cloning the NPCs specifically for those spells and adding an additional trait/ability "Summoned" for using EE to apply the effect).
Looking forward to have it. :)

---

You can already achieve what you want using the excellent (and free) extension "Advanced Effects". This extension allows you to add fixed effects that are already active whenever the actor is added to Combat Tracker. It works with both PCs and NPCs. Just add a "INDEPENDENT" (next update...it won't be long) effect to the summoned NPC sheet and it will do the trick.

https://www.fantasygrounds.com/forum...cs-characters)Advanced Effects' Forge Page

Quote:

---

This extension was originally created by Celestian and is current maintained by Rhagelstrom

---

I am looking into the extension and is there a way to stack the bonus aggro?

Example:

Rogue/ranger multiclass:

Sneak attack: DMG: 1d6: AGGRO: 100

Dread Strike: DMG: 1d8: AGGRO: 150

I would like to see the bonus aggro be 250 but it only calculates one of them.

Thank you

Quote:

---

Originally Posted by charros

I am looking into the extension and is there a way to stack the bonus aggro?

Example:

Rogue/ranger multiclass:

Sneak attack: DMG: 1d6: AGGRO: 100

Dread Strike: DMG: 1d8: AGGRO: 150

I would like to see the bonus aggro be 250 but it only calculates one of them.

Thank you

---

It should be calculating all aggro effects. Can you share a print of your AGGRO effects?

Are you using more than one 'AGGRO: value' in the same effect? Each instance of AGGRO must be in a different effect, so:

https://i.imgur.com/f4ozvcF.png
this would work because it's two different instances of AGGRO in different effects.

https://i.imgur.com/ORVVvvw.png
This would only return the first instance of AGGRO in the same effect.

(Nevermind the Allosaurus attacking itself on screenshots...i'm testing a new feature :P)

Very cool extension! Excited to see what all it can do.

Weirdly enough, I seem to be unable to get it to flag damage, critical hit, or miss threat. Everything else seems to be working fine.

I did have a lot of other extensions active, but I'm not sure which one might be causing the discrepancy.

Upon further testing, I turned off all of the other extensions and it still wasn't applying the threat from damage. I didn't tweak any of the default settings, so I'm not sure if something went wrong with a recent update or what.

Either way, looking forward to seeing where this extension grow!

Quote:

---

Originally Posted by Darth Decisive

Upon further testing, I turned off all of the other extensions and it still wasn't applying the threat from damage. I didn't tweak any of the default settings, so I'm not sure if something went wrong with a recent update or what.

Either way, looking forward to seeing where this extension grow!

---

Please check if you are adding the character to the Combat tracker first and only then dragging them to the map. When you drag a token directly from the sheet to the map, things may seem ok (it even creates the CT entry for that char), but some features won't work properly. The behavior your describe fits exactly the behavior of a token dragged from outside the Combat Tracker. Can you confirm if the problem persists if you delete the token from map and CT and put it back on, but from the combat tracker?

Quote:

---

Originally Posted by Alanrockid

You can already achieve what you want using the excellent (and free) extension "Advanced Effects". This extension allows you to add fixed effects that are already active whenever the actor is added to Combat Tracker. It works with both PCs and NPCs. Just add a "INDEPENDENT" (next update...it won't be long) effect to the summoned NPC sheet and it will do the trick.

---

That would work as well but in both cases, I need to have a summoned version of the NPC which applies the effect, either as trait (EE) or as „per creature“ effect (AE).

This reminds me to review all PC actions/traits for „perceived threat“ (what would a hostile observer consider threatening) and to add an AGGRO ;) like others are already exploring in this thread.

Quote:

---

[ERROR] Script execution error: [string "Aggro:scripts/manager_aggro.lua"]:367: attempt to concatenate local 'nMaxRange' (a nil value)

---

Any idea what might cause this error? It only procs on a homebrewed monster; it seems to work fine on the duergar and other monsters in the intiative while testing...
I added them to the initiative first, before adding them to the map, to avoid errors as you suggest, but still doesn't seem to want to generate aggro for them.

Quote:

---

Originally Posted by Fingersome

Any idea what might cause this error? It only procs on a homebrewed monster; it seems to work fine on the duergar and other monsters in the intiative while testing...
I added them to the initiative first, before adding them to the map, to avoid errors as you suggest, but still doesn't seem to want to generate aggro for them.

---

Yes, I've already noticed that bug and it's fixed in the next update that should be up tonight with some new features and fixes.

Quote:

---

Originally Posted by Alanrockid

Yes, I've already noticed that bug and it's fixed in the next update that should be up tonight with some new features and fixes.

---

Fabulous news! :D

Quote:

---

Originally Posted by Fingersome

Fabulous news! :D

---

Wait, did you update the extension already? Because come to think, nMax range error was already fixed in 1.1.1
The bug that still remains in 1.1.1 (and its fixed in the coming version 1.2.1) is that the formula to calculate effective and max range for melee actors was using bad parameters, so it is always calling the default number "30" to avoid a nil error.

Quote:

---

Originally Posted by Alanrockid

Please check if you are adding the character to the Combat tracker first and only then dragging them to the map. When you drag a token directly from the sheet to the map, things may seem ok (it even creates the CT entry for that char), but some features won't work properly. The behavior your describe fits exactly the behavior of a token dragged from outside the Combat Tracker. Can you confirm if the problem persists if you delete the token from map and CT and put it back on, but from the combat tracker?

---

I removed the PC from the combat tracker completely, then re-added them, and drug them from there to the map. I then put a new NPC on the combat tracker and pulled them to the map from there. For whatever reason, it still seems to be unable to track any of the damage aggro values, even if I dump a few hundred points of damage from the PC to the NPC.

Attached a couple images showing the chat log if it helps. Gilveradin Windrunner was the attacker, and Arackokra was the NPC.