[Issue] Leading 0's needed in delivery times to sort correctly 01,02,03 days vs 1,20,2,35,37,38,3 days

[kevinschulthies]

Brief Description *

Bug for Mekhq Should have a leading 0 on Warehouse "Status" column for delivery times....2 gets put AFTER 20 days.... if you had leading 0's 01 days, 02 days, 03 days, they'd sort correct I think :)

I dont like how complex it is to report something. I help bug fix for a variety of games, I screen shot, markup, drop into bug channels typically on discord. Maybe someone would like to offer that and then transfer it here. I likely wont report any more in the future.

3. Steps to Reproduce

No response

Attach Files

Severity *

Critical (Game-breaking/Crash): The game crashes or a core feature (like saving, loading, or network connection) is completely unusable.

MegaMek Suite Version *

50.04

Operating System *

Window11

Java Version *

?? no idea one of the newest

Final Verification

• I confirm this is a single, unique issue that hasn't been reported before
• I have included all necessary information and files to help reproduce this issue
• I have asked on MegaMek Discord about this issue
• I have confirmed this issue is being opened on the correct repository: MegaMek, MegaMekLab, or MekHQ

[IllianiCBT]

While I appreciate that it's a bit of a chore, please remember that we're not a professional game studio. Nor do we have the backing of some publisher. We're not even an indie studio. We literally have a budget of 0 dollars. We're a group of passionate fans donating our time and expertise to craft what is probably the best Mek management simulator in the world.

Why does that concern you? Well, it means we don't have a group of staff whose job it is to track down bugs on Discord, log them, and then make sure they're flagged with the appropriate teams. Instead, we need to lean on users, like yourself, to help carry the load.

After all, what would you prefer we spend our time doing: scrolling through Discord and checking for bugs, or actually fixing those bugs?

[rjhancock]

1. Leading zeros wont solve the problem and it can be solved by simply converting the time in days to an Integer and sorting that way.
2. We ask you check on Discord FIRST as we've had a history of people report duplicate bugs or the issue may already be fixed either in a later version OR in a nightly.
3. If neither of those are the case, we ask they report the bug here so that it gets logged properly.

This is the process that works for us as we are all volunteers. We do this because we CHOOSE to. We already have a rather large back log of issues that we are working on PLUS features we want to implement PLUS our own lives to attend to.

This bug is a minor inconvenience at best.

[kevinschulthies]

You guys do epic, work thanks 😊 Yeah I jump into a couple discussions on discord. Been enjoying everyone’s work for years with Megamek and thought I’d make my first quick suggestion (little did I release how complex your feedback system was). I didn’t mean any disrespect but was trying to help, but I’ll just stay silent to everything because of the complexity of it all and will just enjoy the system for what it is. The current way to report anything is crazily complex (and im sure it helps in some ways isolate or categorizie bugs etc) Thanks again, Kevin From: Richard J Hancock ***@***.***> Sent: April 5, 2025 11:57 PM To: MegaMek/mekhq ***@***.***> Cc: kevinschulthies ***@***.***>; Author ***@***.***> Subject: Re: [MegaMek/mekhq] [Issue] Leading 0's needed in delivery times to sort correctly 01,02,03 days vs 1,20,2,35,37,38,3 days (Issue #6563) 1. Leading zeros wont solve the problem and it can be solved by simply converting the time in days to an Integer and sorting that way. 2. We ask you check on Discord FIRST as we've had a history of people report duplicate bugs or the issue may already be fixed either in a later version OR in a nightly. 3. If neither of those are the case, we ask they report the bug here so that it gets logged properly. This is the process that works for us as we are all volunteers. We do this because we CHOOSE to. We already have a rather large back log of issues that we are working on PLUS features we want to implement PLUS our own lives to attend to. This bug is a minor inconvenience at best. — Reply to this email directly, view it on GitHub <#6563 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKMGIFZW6KSOHVSVNGPF4CD2YC62ZAVCNFSM6AAAAAB2RJ5GCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGIZTMNZVG4> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BKMGIF55LAPPM4UY27TQTQD2YC62ZA5CNFSM6AAAAAB2RJ5GCCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVFYZHBK.gif> Message ID: < ***@***.***> ***@***.***> <https://avatars.githubusercontent.com/u/460240?s=20&v=4> rjhancock left a comment (MegaMek/mekhq#6563) <#6563 (comment)> 1. Leading zeros wont solve the problem and it can be solved by simply converting the time in days to an Integer and sorting that way. 2. We ask you check on Discord FIRST as we've had a history of people report duplicate bugs or the issue may already be fixed either in a later version OR in a nightly. 3. If neither of those are the case, we ask they report the bug here so that it gets logged properly. This is the process that works for us as we are all volunteers. We do this because we CHOOSE to. We already have a rather large back log of issues that we are working on PLUS features we want to implement PLUS our own lives to attend to. This bug is a minor inconvenience at best. — Reply to this email directly, view it on GitHub <#6563 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKMGIFZW6KSOHVSVNGPF4CD2YC62ZAVCNFSM6AAAAAB2RJ5GCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOBRGIZTMNZVG4> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/BKMGIF55LAPPM4UY27TQTQD2YC62ZA5CNFSM6AAAAAB2RJ5GCCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTVFYZHBK.gif> Message ID: < ***@***.***> ***@***.***>

[rjhancock]

The current system is a result of the user base not providing us with enough context to work with issues that arise, submitting duplicate tickets without searching for them first, or reporting bugs that have either been fixed in a later released version or the nightly and soon to be released.

We ask the users to do a little extra work (and yes, it is a LITTLE extra work) to ensure we the team get what we need and can focus on fixing bugs and adding features instead of continently asking questions to get anything resembling what we need to determine if the issue is a bug, user error, and a feature request.

We do not have the resources to keep doing that for every issue. You can see the backlog in the three projects has exceeded several THOUSAND issues that need to be worked through still and triaged at a minimal. We need help. Period. Part of that help is having you, the user, do some of the leg work before submitting a ticket to make sure we don't spend hours trying to triage it. Hours we could have spent fixing the issue or any of a hundred others.

So the process is NOT needlessly complex, it is as complex as it is to ensure we get actionable tickets to make it better for all.

Again, we are a volunteer team with limited time to fix bugs and add features. The more work the submitter does to get us the details we need, the faster we can get it fixed and add more features.