Lock on Prio

Lock-On Priority

Makes Epic Fight's lock-on reliably win control of camera rotation and movement facing when it conflicts with ShoulderSurfing, BetterLockOn, and/or SSRCameraFixes — plus a small fix so the character stops looking at pass-through blocks (tall grass, flowers, etc.) that the crosshair happens to be over.

What it fixes

• Camera/head whip during lock-on — when multiple mods (Epic Fight's own ShoulderSurfing compat, BetterLockOn, SSRCameraFixes) all try to control the camera's facing at once, the result can be a rapid back-and-forth jitter. This mod re-syncs the camera to Epic Fight's own authoritative lock-on rotation as the guaranteed last write of the frame.
• Character running straight at the target regardless of movement input — a known issue with BetterLockOn's own movement-facing logic. This mod hands full movement/facing control to lockonmovementfix during lock-on instead.
• Looking at grass/pass-through blocks — Epic Fight's look-direction raycast used a block's outline shape instead of its collision shape, so decorative blocks like tall grass would visually pull the character's gaze down. Redirected to use collision shape instead.

Priority behavior

This mod is a compatibility layer, not a replacement for any of the mods above. It automatically picks one of two behaviors depending on what's installed:

1. SSRCameraFixes installed → full trust, hands off completely. SSRCameraFixes
   • BetterLockOn's native behavior is used as-is.
2. SSRCameraFixes absent → lockonmovementfix becomes the sole movement/facing authority during lock-on (BetterLockOn still provides target selection/UI, just not movement-facing).

Requirements

• Epic Fight (required)
• ShoulderSurfing, BetterLockOn, lockonmovementfix — all optional, but at least ShoulderSurfing + one of BetterLockOn/lockonmovementfix is the intended use case (third-person lock-on play).

Known limitations

• When SSRCameraFixes is not installed, ShoulderSurfing's own "Camera Coupling" toggle has no effect on lock-on movement/facing specifically (it still works normally everywhere else). This is an intentional trade-off for reliable, jitter-free movement.
• The pass-through-block look fix depends on an internal (non-API) BetterLockOn method name; if a future BetterLockOn update renames it, this specific fix will silently stop applying without affecting anything else.

Compatibility

Client-side only. Built for Forge 1.20.1.