Incorrect Jump Point to Planet Travel Times

What went wrong

When conducting a normal transit from Tigress to Xhosa VII, I noticed the estimated travel time was significantly higher than I had expected. On inspecting the Xhosa VII system, it showed a time to jump point of 124.32 days. This seemed unusually high, and on a follow-up fact check I found that sources from Sarna.net and official CGL books showed a much lower transit time from jump point to planet. I've included screenshots of the system and its information in MekHQ, as well as a clip from the Draconis Reach book (pg. 120) detailing what I believe to be the most recent CGL data for the system. I've also attached the campaign save zip from the bug reporting built into MekHQ.

I did notice that in addition to the transit time mismatch, the star type and surface gravity were also off, although I don't believe the latter is likely to have an impact on the transit times.

What you expected instead

I expected a transit time of something around between a few days to a month for the in-system jump point to planet Dropship hop.

Steps to reproduce

1. Launch MekHQ.
2. Load campaign save or start new campaign.
3. Open Interstellar Map tab and search "Xhosa VII" in Find Planet search bar.

Attach your files

Scrapyard Knights31510919_Clover-part1.zip

Relevant log lines

MegaMek Suite Version

MekHQ v0.51.00

Operating System

Windows 11 10.0 (amd64)

Java Version

Eclipse Adoptium 21.0.11

Before you submit

• This report only contains one issue or request, and I haven't already reported it

• I am on the right repository - MegaMek for battles, MegaMekLab for unit design, MekHQ for campaigns, mm-data for unit and planet data

• I have asked about this on the MegaMek Discord (optional)

Load the attached campaign save in MekHQ and open the Interstellar Map tab, then search for Xhosa VII in Find Planet. Compare the displayed jump-point-to-planet travel time, star type, and surface gravity with the cited Sarna.net and Draconis Reach sources. Done means the planet data matches the verified references and the reproduced travel-time discrepancy is resolved.