Weird distance bug on controller (& possible application)

[tinybike]

Reported by a nexus user, need to confirm this etc but sounds like it happens regularly. No idea if the accompanying idea is feasible, need to check out the bug myself first.

On Controller play there's a bug that basically reduces the attack range to almost zero, you can still melee attack but you have to use the directional buttons to select the target as the radial won't pop up at all.
(This bug literally occurs in every fight irrelevant of party size and I just briefly use mouse to play when it does).

On using directional keys you can only pick up what is directly Infront or beside the character, (like real life melee range) but you can't select something even like 5m away.

So could this "Bug" then be applied to enemies, with a script that they must run at you and then are blocked from attack as this "bug" when implemented on them would prevent that.
It would basically be the same thing right, since once outside range they couldn't attack and would have to run at you.

It wouldn't allow reactions for teleport but would still allow manual teleport to escape the range determined by this "bug".

[The-Draiken]

Feel the Need to give an update on this bug, the cause and the fact that once a player gets used to it, it is beneficial in a way.

The bug is caused fundamentally by the fact that an enemy somewhere on the battle field has attacked that character but hasn't finished their series of attacks within that "turn" on the character.
Maybe their running at you but not yet reached, maybe they've launched an arrow but it's not yet hit, maybe they have cast a spell, or they are to attacking you twice in one go (Ai having two attacks per round??, that's what it seems like on testing) but whatever it is, they are attacking you and before they have finished, you have already paused the game on controller play.

Why this is beneficial, is because normally there are soo many things happening on the battlefield, you might not have line of sight for everything and it allows the player to "Know" that something is coming (once they understand what actually causes the bug), and actually manually react to the incoming attack with all your abilities present.

Additionally incase the attacker is literally 1:1 in front of the player( it's the distance of the circle around the player character but nothing more is allowed) they can strike back, but even if that striking back has enough damage to kill the enemy in a single hit, that process of attacking you from the enemy side is uninterruptable, they will still 100% hit you, but just die immediately after. (It's like a weird kind of accidental Balanced feature)

If a Player also has the Mod PF2e Spells, there's a cantrip in that mod that's named Shield, it is cast as a bonus action and will reduce the damage of any attack by 5 as a reaction once cast, and then can't be cast again for 10 turns/1 minute.
The spell and this bug almost seem made for each other with how they both work.

It seems very Strange how drastically different controller play works as Compare to KBM, from this to the fact bonus actions and some buffs can be freecast in controller, to projectile attacks being easier to dodge.
I think it's important to mention these differences on the description page for the time being until you know what you want to do with all of it.

Though I will say the "bugs' I discover, almost seem like they were made for RTWP.