Reply to Re: Bugfixes for freedink on Linux
If you don't have an account, just leave the password field blank.
One thing I would note, is that it seems from this thread https://www.dinknetwork.com/forum.cgi?MID=207925#207973
...that Seth is using get_version to refer to the DinkC version, rather than a game version. I'm not sure if you mean the same thing by it?
Also, I don't know how useful a get_version_minor would be to DMOD developers. What would be the use cases for this? How many DMOD developers would work around specific game subversions? Ideally, those minor versions should be identical to the major versions in terms of command availability...
I do think get_fork sounds useful though, to distinguish future FreeDink and other possible ports that might appear. Although I would've named it something like get_engine_id
I don't think this would really solve any of the existing problems of distinguishing the original 1.08 from FreeDink 109.6 (Original Beuc Edition) though... This whole version business just seems to get more and more complicated doesn't it?
...that Seth is using get_version to refer to the DinkC version, rather than a game version. I'm not sure if you mean the same thing by it?
Also, I don't know how useful a get_version_minor would be to DMOD developers. What would be the use cases for this? How many DMOD developers would work around specific game subversions? Ideally, those minor versions should be identical to the major versions in terms of command availability...
I do think get_fork sounds useful though, to distinguish future FreeDink and other possible ports that might appear. Although I would've named it something like get_engine_id
I don't think this would really solve any of the existing problems of distinguishing the original 1.08 from FreeDink 109.6 (Original Beuc Edition) though... This whole version business just seems to get more and more complicated doesn't it?