Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unarmed combat when reach set too low #13

Open
MariusKlug opened this issue Aug 18, 2024 · 0 comments
Open

Unarmed combat when reach set too low #13

MariusKlug opened this issue Aug 18, 2024 · 0 comments

Comments

@MariusKlug
Copy link

FYI I have found that setting the reach too low causes NPCs to attack only unarmed. I am playing in VR and wanted to lower the reach further because in VR it is quite apparent if you get hit without actually getting hit. I assumed the reach would also apply to unarmed (h2h) combat, as that is a parameter in the patcher, but it appears that this is not the case.

I'm now using fCombatDistance 105, fCombatBashReach 61, fObjectHitWeaponReach 81, fObjectHitTwoHandReach 105, fObjectHitH2HReach 41. With fCombatDistance 100 and the rest the same I found some orcs in the Nightcaller Temple to fight H2H, which I saw a mace in their inventory afterwards. I havent tested 105 there yet but will do so soon and hope that fixes this issue.

I don't quite understand the cause of this, but I am willing to accept this occasional glitch in return of more accurate general combat. It used to drive me nuts that I got hit by wide sweeping longsowrd attacks that i was not even able to block because they were out of range of my shield. So this fixes that, for which I am grateful.

If anyone knows and can point me to a deeper understanding of the unarmed, hand to hand combat issue, please let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant