Reply to Re: Bugfixes for freedink on Linux
If you don't have an account, just leave the password field blank.
Did many authors actually do a check for DinkHD using get_version and lock the dmod out? I didn't think many did.. Also if they did, wouldn't be hard to patch those dmods no that DinkHD has been brought up to speed and remove those DinkHD lockouts.. I doubt there's be many.
DinkHD already has a command to get the client version "get_client_version()", so yes "get_version" gets the DinkC version (which in the latest build is "111"), but get_client_version gets the build number ("197" in the latest DinkHD release).
As for Version Checker, I'm going back to barebones, and retiring any future updates. It will use get_version to get 108, 110(with an additional check of get_client_version >= 197), and I will include sections for authors to automatically run it with custom prompts. It's still useful this way all in one script.
I will then include sections that, rather than checking for versions, check if the &arg bug and soundbank bug is currently present. So you will simply use external to call the procedure, and &return will give you the result of which bugs are currently present in whatever engine the player is using.. An author can then check for these at anytime and adjust scripts to work around these issues (they are both easy to create alternate scripts to make them work). Only time I will do updates (after this next one I will be releasing soon), is if any other game altering bugs come up in any future releases, which I will also add a procedure for(same as &arg and soundbank bugs).
DinkHD already has a command to get the client version "get_client_version()", so yes "get_version" gets the DinkC version (which in the latest build is "111"), but get_client_version gets the build number ("197" in the latest DinkHD release).
As for Version Checker, I'm going back to barebones, and retiring any future updates. It will use get_version to get 108, 110(with an additional check of get_client_version >= 197), and I will include sections for authors to automatically run it with custom prompts. It's still useful this way all in one script.
I will then include sections that, rather than checking for versions, check if the &arg bug and soundbank bug is currently present. So you will simply use external to call the procedure, and &return will give you the result of which bugs are currently present in whatever engine the player is using.. An author can then check for these at anytime and adjust scripts to work around these issues (they are both easy to create alternate scripts to make them work). Only time I will do updates (after this next one I will be releasing soon), is if any other game altering bugs come up in any future releases, which I will also add a procedure for(same as &arg and soundbank bugs).
