HitFlash

HITFLASH

Red when it connects. Yellow when it doesn't.

The lightest way to learn exactly when a monster's attack lands on you.

Why this exists

Most weapons in Wilds live or die on one window: the few frames where you counter, guard-point, dodge through, or commit a finisher into the attack that is already on you. Get it right and you punish for free. Get it wrong and you eat the hit.

The problem is that the game does not tell you which one happened.

Mid-fight — particles, camera shake, a monster's body across half the screen, your own animation still playing — the difference between "I blocked it clean" and "I still took 40 damage" is almost impossible to read. The health bar moves a little. Something flashes somewhere. You look away for a second and you have learned nothing.

So you cannot drill the timing, because you cannot see the result.

HitFlash closes that loop.

The instant a blow is resolved against you, the edges of the screen answer:

• []Red edge — you lost HP. That attack came through. Your timing was wrong, or you were not guarding.[/]

  []Yellow edge — it hit you and you lost nothing. Blocked, guard-pointed, invincibility frames, damage nullified. Your window was correct.[/]

  Both last 0. 1 seconds with no fade — a hard, unmistakable cut, not a soft glow you might miss while watching the monster. You stop guessing after every exchange and start seeing whether your timing was right.

  If you only want to learn when you got hit — not hitbox volumes, not frame-data overlays, not per-part damage breakdowns — this is the lightest tool that does it. One Lua file, no dependencies, nothing to configure to get started.

  ---

  What it is not

  Strictly read-only. It never changes damage, never swallows an event, never touches invincibility frames, never alters game balance. Every hook it installs returns nothing to the game, so the original logic runs exactly as shipped. It watches, and it draws. That is all.

  • []✓ No dependencies beyond REFramework — one file[/]

    []✓ Works solo and in multiplayer — only your hits flash[/]

    []✓ Visible with the REFramework menu closed[/]

    []✓ Cannot desync, corrupt a save, or affect quests[/]

    ---

    Requirements

    • []REFramework (recent build)[/]

      Install

      Extract into Monster Hunter Wilds\GAME:

      ├─ reframework\

      │  └─ autorun\

      │     └─ HitFlash.lua

      └─ MonsterHunterWilds.exeLaunch the game. It loads by itself — nothing to enable. Vortex and mod managers install the archive normally.

      Uninstall: delete reframework\autorun\HitFlash.lua (and optionally reframework\data\HitFlash_config.json holding your settings).

      ---

      Settings

      Press Insert → Script Generated UI → HitFlash. Everything is remembered between sessions.

      Out of the box:

      • []Red / yellow edge duration — 6 frames (0. 1 s @60 fps)[/]

        []Edge thickness 160 px with 8 spatial gradient layers fading inward from the screen border[/]

        []No fade-out — constant intensity, then it vanishes the instant the timer expires. Turn on Fade out for a soft tail[/]

        []Damage number — on: white digits with a black outline from a built-in pixel font, sitting top-left below the HUD bars so it never covers them, visible for 2 seconds[/]

        []Full-screen tint and centre marker — off[/]

        Tuning knobs:

        []Red / yellow duration — 3–180 and 2–120 frames[/]

        []Resolve window — how many frames a hit may sit with no HP loss before it counts as blocked (1–30, default 6)[/]

        [*]Edge thickness / gradient layers / outer opacity — 20–400