Have you ever thought to yourself "I wish there was an additional consequence for when an attack roll exactly equals a target's AC"? Well, there's a houserule that does exactly that; it states that when an attack roll lands directly on a target's AC, that attack does half damage to the target. This extension automates that handy-dandy houserule for you!

Additionally, do you think it's weird that the chat window displays the tag [RESISTED] when a target takes 0 damage (i.e. is immune)? And [PARTIALLY RESISTED] when a target takes partial damage from the attack (e.g.: has resistance)? Well, we sure did. The syntax is fine enough in a vacuum, but doesn't really work with 5e's existing terminology. So we fixed it so that the tags will display thusly:

• [RESISTED] The target is resistant to all incoming damage
• [IMMUNE] The target is immune to all incoming damage
• [VULNERABLE] The target is vulnerable to all incoming damage
• [PARTIALLY RESISTED] When being hit with an attack that does more than one type of damage, the target is resistant to at least one damage type, but not all of them.
• [PARTIALLY IMMUNE] When being hit with an attack that does more than one type of damage, the target is immune to at least one damage type, but not all of them.
• [PARTIALLY VULNERABLE] When being hit with an attack that does more than one type of damage, the target is vulnerable to at least one damage type, but not all of them.
• Currently not supported: Damage absorption is a Thing in 5e, but the [ABSORBED] and [PARTIALLY ABSORBED] tags are currently used in Fantasy Grounds to reflect that damage has been dealt to Temporary HP rather than HP. Given the rarity of damage absorption in 5e--and how hard it would be to change those tags to something else for the purposes of displaying absorption--we have decided to leave that alone for now.

This extension works for FGU, D&D 5e.

What it does:

• Adds an option to turn on the Glancing Blows houserule (for your convenience, it's default state is set to On)
• Halves the damage to creature that has been hit by a Glancing Blow
• Display the [GLANCING BLOW] tag in the chat window to denote that an attack exactly hit the target's AC
• Display the [GLANCING BLOW] tag in the chat window to denote the source of the damage being halved to a target
• Displays our own version of the Damage Adjustment tags, as listed above
• Is compatible with the Master's Amulet extension

          UPDATE v1.1.1 includes the following changes:

• Fixed a bug where Glancing Blow damage is not halved correctly if a player/client rolls the damage instead of the DM/host
• Many small bug fixes to accommodate changes made in various updates to Fantasy Grounds
• Updates to the logo for the extension as well as the icon that displays when a Glancing Blow is rolled, to match the aesthetics of recent updates to Fantasy Grounds
• Incorporated changes made by rhagelstrom to improve compatibility with various other extensions

EDIT: Something went wrong with our fixes; the damage is only halved correctly when it is rolled manually, which we didn't catch initially because we had been using manual rolls to do the testing (much easier to check for a Glancing Blow when it's not depending on a 5% chance dice roll :P ). Hoping to find a fix soon.

What it doesn't do:

• Help you get over this cold you've had for like a bloody week now
• Convince your DM that you actually do need a second 9th-level spell slot
• Motivate you to finally write that one-shot you've been thinking about

I have thoroughly tested this (in FGU; I do not know if it would work in FGC), but please let me know if there are unexpected bugs! I hope this improves your D&D VTT experience :)

This extension is free, because it only modifies SRD material, but I accept donations (see link below) if that is something you're interested in doing :)
https://ko-fi.com/kaeltheadventurer

Risk Warning: Extensions are code that is added to or overrides portions of code in the Fantasy Grounds Unity (FGU) application, and when the underlying code in FGU changes, sometimes it will break extensions. When you run multiple extensions, they can conflict with each other by trying to overwrite the same parts of the FGU code. Using extensions comes with risk, no matter who or where they come from.

Don't forget to love each other :)