Open Luiji opened 13 years ago
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 29.07.2011 18:51, schrieb Luiji:
Thoughts? Concerns? Questions?
(Currently on vacation with poor internet connection, sorry for being late)
I think it's a good idea to have this version check. It'd also remind user to update their SMC installation if "WARNING: Minimal SMC version
Just curious - I know @Quintus started working on a new server application for levels, scripts, and other content for the new "Secret Chronicles of Dr. M" line of releases.
Will any of the work on smc-get be leveraged for this?
It might be a good idea to have a Minimal and Recommended -Version attribute in the YAML specifications for SMC.
Printing a warning if the version of TSC is outdated is a good idea. As @Luiji said, it would not need to be "strictly" enforced.
It might be a good idea to have a Minimal and Recommended -Version attribute in the YAML specifications for SMC. Recommended would usually refer to the earliest version that has a certain background or something not as potent to the level's function and Minimal would be for enemies of a specific version. Level contributors could leave these entries empty if they want though, i.e. in case they don't feel like verifying which versions correspond to which features.
We should also document all of the graphics and enemies of SMC and at which versions they were added (this would be pertinent to getting contributors to spend time setting Minimal-Version: and Recommended-Version:).
There would also be an attribute in SMC-GET's configuration file called 'SMC-Version:' which would indicate which version of SMC the user has.
Minimal: and Recommended: should not be enforced strictly, however, and instead just output a stern warning.
Thoughts? Concerns? Questions?