Skip to content

Update SOC version, make base SRB2 SOC throw a warning

Sal requested to merge dehacked-versioning into next

What it says on the tin.

Not sure what the future standard for updating PATCHVERSION should be:

  1. It should just be "1" to mean that it's for v1, update to "2" for v2, etc. (What it is currently)
  2. It should be "10" to mean v1.0, so that it can be updated for v1.1 only if needed.
  3. It should just have the whole version number, and change it to latest version if the Dehacked tables are changed. (What was initially committed)

Not totally sure, since this is a feature I find no usefulness out of. The age of freeslots and named types removed a lot of potential for incompatibility between versions, so I think I'm leaning towards the first one for simplicity.

Edited by Sal

Merge request reports