BattletechModders / BattletechModders/LowVisibility
Melee attack at close target shows bogus max stealth-range penalty
- Dominant language
- C#
- Stars
- 8
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
As per ticket-0106:
Thank you for your patience!
HarkonnenLast Thursday at 9:08 PM
this about an issue with stelath + melee "i dont want to create ticket" guy was talking about
Attachment file type: archive
low_visibility.log.zip
3.53 MB
basicaly, a melee attack at close target show a bogus maximu stealth-range penalty
it doesnt actually apply it, as can be seen in actuall to hit percentages
just confusing
@FrostRaptor
LadyAlektoLast Thursday at 9:11 PM
it does fit
melee is just a weapon
with a very short range, so long range penaltys will be applied
HarkonnenLast Thursday at 9:11 PM
but it show no penalty for tagrets that are not close
LadyAlektoLast Thursday at 9:12 PM
that now is weird but i fail to understand the issue
HarkonnenLast Thursday at 9:13 PM
it confuses people. there is no actuall penalty, but it shows one fro close targets
LadyAlektoLast Thursday at 9:14 PM
hmmm
HarkonnenLast Thursday at 9:16 PM
if you look at actual to hit% for close and far targets, its clearly not aplied, as +6 would have droped it to 10-15% range instead of ~40%
LadyAlektoLast Thursday at 9:21 PM
yeah still hmm why it shows at all
maybe @FrostRaptor needs to add the rt aim fork too^^
HarkonnenLast Thursday at 9:30 PM
btw, an unrelated issue i found while testing this - narc and tag fire in melee despite having "NotUseInMelee": true, @KMiSSioN
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the attached low_visibility.log.zip and reproducing the melee attack against close and distant targets. Compare the displayed stealth-range penalty with the actual to-hit percentages. The issue does not name a source file or test, and completion would require clarifying the intended display behavior; the separate narc and tag melee behavior should be treated as unrelated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100