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

12/13 logistics artifact 0.50.02 - Callsign in logs only lists at the bottom in graveyard/survivors, no longer shows in the round by round feed, exacerbating kill credit assignments for targets that weren't hard-killed #6272

Open
7 tasks done
OrbMonky opened this issue Dec 15, 2024 · 4 comments
Assignees
Labels
Can't Reproduce Reports Anything relating in game reporting Severity: Low Issues described as low severity as per the new issue form

Comments

@OrbMonky
Copy link

Prerequisites and Pre-Issue Checklist

  • I'm reporting the issue to the correct repository:

  • MegaMek

  • MegaMekLab

  • MekHQ

  • I've tested the issue against at least the latest MILESTONE version

  • I've asked on the MegaMek Discord about the error

  • I've reviewed the BattleTech rules and MegaMek documentation, and I've confirmed that something isn't working as intended.

  • I've searched the Github tracker and haven't found the issue listed

Severity *

Low (Minor/Nuisance): Minor glitches or cosmetic issues that don’t affect gameplay and occur rarely.

Brief Description *

The name and callsign shows here
image
but not at the actual kill feed here where it previously did
image
this creates additional work needed to assign kills for mission-killed units that where not hard-killed, which is frequently the case.

This primarily comes up when you have two units with the same variant of the same mech, mekhq often confuses or re-numbers them with #2-#9999(?) depending on how many you have, usually during mothballs/salvageing a new one/refitting a new one etc. so it is not reliable to say 'Stalker STK-00-V 'Magna' #2' and know which personnel is getting the kill because MekHQ can represent it differently than what is ported to megamek. Callsigns however were very reliable.

It is still WORKABLE in this state as the callsign is stated at the bottom but there doesn't seem to be a reason to remove the callsign from the round report combat feed

Steps to Reproduce

  1. assign two units of the same exact type/chassis/refit etc
  2. assign one of them a callsign (or both)
  3. kill stuff, immobilize stuff, force ejections
  4. try to sort it out

Operating System *

Windows 10

Java Version *

17

MegaMek Suite Version *

None

Custom MegaMek Version

12/13 Logistics Overhaul '0.50.02-SNAPSHOT'

Attach Files

No response

Final Checklist

  • I've checked to make sure that this issue has not already been filed
  • I'm reporting only one issue in this ticket for clarity and focus
@HammerGS HammerGS added Reports Anything relating in game reporting Severity: Low Issues described as low severity as per the new issue form labels Dec 15, 2024
@psikomonkie psikomonkie self-assigned this Dec 24, 2024
@psikomonkie
Copy link
Collaborator

Hey @OrbMonky !

but not at the actual kill feed here where it previously did

Your comment about the kill feed mentions "previously did". Do you know what version you were on that has this, or, even better, would you be able to get me a screenshot of what you think it should look like?

Thanks,
Psi

@OrbMonky
Copy link
Author

It should be present in 0.50.00, and most recent historical ones, at least as far back as 2022.

I found this image online for it;
Untitled
Note how it places the callsign, in this case 'ROCKY', on both the mek and the pilot event reporting.

@psikomonkie
Copy link
Collaborator

Hey @OrbMonky , that's the same thing I see on the latest:
image

I'm unable to replicate this bug.

@OrbMonky
Copy link
Author

If it works in the latest it may be a transient issue, good to hear it seems to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Can't Reproduce Reports Anything relating in game reporting Severity: Low Issues described as low severity as per the new issue form
Projects
None yet
Development

No branches or pull requests

3 participants