I have just finished adding a scrolling version display feature to the OS, which I will be posting as a beta release shortly this evening. In the process I've realized that I need to tighten up the versioning definitions for the OS, modules, and patches somewhat.
This will all go in the next manual release, but for now here is the new Versioning Bible:
1) OS, patches, and modules with have versions of the form "a.bb.cc"
2) a has a range of 0-255, b has a range of 0-99, c has a range of 0-99
3) Module revisions defined as $00_01_01_01 have in the past been listed (by me, and by Workbench) as 1.1.1, but they should properly be listed as 1.01.01. Workbench will be updated to reflect the change, and I will update the effect module posts and source accordingly. The new beta OS displays the revisions properly.
4) Patch revisions will be viewable/settable within the next release of Workbench, coming soon.
5) Beta OS releases will be designated by an odd revision in the bb field. Tonight's beta release will accordingly be "2.01.00". Stable releases will be designated by an even revision in the bb field.
6) When updating the revision of effect modules, the a field must be updated if and only if socket interfaces are added or removed. bb should be updated when making fundamental changes to the sound or algorithm, and cc should be updated if making minor changes. The OS/Workbench will be updated soon (not in tonight's beta) to store the major (i.e. "a" field) revision of each module used to build a patch, and the OS will ignore incompatible module versions (i.e. ones in which the major revision has changed) when searching for modules during a patch load.