#Meta-request: Please stop releasing
valid isle
I'm mostly curious but why is that needed ?
Like I mentioned in #mod_development the problem here is mostly that this is a hotfix for every versions available it seems
paper phoenix
Are you asking why having unique versions identifiers for different published builds of the game is needed?
solar willow
42.15.2 is the game version to play on. If you are refering to git hash changes, pls check those instead https://steamdb.info/depot/108604/history/
paper phoenix
Yesterday's 42.15.2 and Today's 42.15.2 are NOT the same game.
coarse canopy
Yea, if you wanna make changes to the game the version number should change. Even if its a security update and 'should change nothing'
About 29 .java files changed between yesterday and today. Not exactly a trivial change.
paper phoenix
If they want to avoid calling it 42.15.3 for some reason, 42.15.2B or 42.15.2.Hotfix1 or something similar would be fine.
Right now the only way to tell which version you are using is to see if you're on hash 03e1475bbf4997cd00cfdc0eb609f8f861f4897f or hash 52e59f16e85ce81db89891a19fb283a0cad15b75
coarse canopy
All the previous versions should be incremented too if they have been updated.
valid isle
Are you asking why having unique versions identifiers for different published bu...
Bruh I don't get why no one's understanding what I mean
I mean that B42.14 too needs to be updated so they'd need to bother changing that version number too ?
paper phoenix
Yes, they should.
coarse canopy
Bruh I don't get why no one's understanding what I mean
I mean that B42.14 too n...
Yes, and B41.x if they are updating it still, needs to be incremented
its the entire reason we have B42.x.hotfix
valid isle
Maybe there's limitations to them doing it
valid isle
its the entire reason we have B42.x.hotfix
Agreed
paper phoenix
The only limitations on their version numbering are self-imposed.
coarse canopy
You make 1 tiny change.. like say, B42.15.1 hotfix was.. You should update the hotfix number.
valid isle
But everytime they did a wide version patch like that it has never incremented, so that's what I mean by a limitation, maybe they have something stopping them from doing that
coarse canopy
Security by obscurity doesn't work.
paper phoenix
But everytime they did a wide version patch like that it has never incremented, ...
What could possibly be limiting them? There's no external party enforcing a release naming convention.
valid isle
What could possibly be limiting them? There's no external party enforcing a rel...
What do I know ????
I'm doing logical suppositions of why they aren't doing it rn
The observation is they never increment it when it's an update applied to older versions too. Now why that's the case idfk
coarse canopy
So they never increment it when its a security update, then.
solar willow
the version naming convention is team-specific. 🙂
valid isle
So they never increment it when its a security update, then.
That's linked yea, but simply bcs that's the only kind of update which justifirs updating older versions too
coarse canopy
"We're not going to tell you if your on the secure version or not" Is kinda.. a weird stance to make.
.. must suck for people using the GOG version.
valid isle
.. must suck for people using the GOG version.
Why that ?
coarse canopy
Why that ?
they are going to be on a version without those security updates and won't be able to even tell if they do have them or not.
solar willow
like download again?
coarse canopy
like download again?
based on what notification did the GOG player get?
"Version update! version 41.72" "thats the version I already have!"
(not that I think GOG does msg you about updates)
solar willow
is not that the verion have a build hash already
coarse canopy
Build hashes are not listed very often. And we already have version numbers for this very purpose and to be easily human readable, something build hashes are not.
Plus, if any of these security changes do cause bugs Its going to be harder tracking down when the bug first occurred if people are just reporting B42.15.2 bugs, especially with more and more users saving their zomboid version and preventing steam to update so their saves don't get made unusable.
solar willow
imo, the priority is security and stability, so it might not be clear yet.
regarding broader concerns
reef fjord
Honestly? There should be a .env or package.json file or something of the like that has build information.
The reason? Really helpful for 3rd-party tools. I'm sure that server tools could also benefit from this as much as mine would.