Revision  #0035

[Marshall]

However, RP version not for users, for programs

Not quite - here I think there is some misunderstanding.
If a mod requires the RP then it will specify what Version is required. LB mods will tell LB what Build [internal integer version] is required. LB will use this internally to check the RP version. LB will translate the Build into the string Version and display it to the user [e.g: "This mod requires version %s of RockPatch", GetRPVersion(ModRPBuild)]
Mod authors need to tell LB Mod Creator (or their own programs) what version is required, by giving it the build number.
That is why we need a standard integer form of the version number as well as the version name.
Version name is merely what gets displayed to the ordinary user, but has to be consistent: At the moment, if an LB mod requires RP Build 10802 then LB will claim the mod needs version 1.08b.

I'd prefer to keep XYYZZ because it is the same as the TX so is simpler for both my program and the users to understand. However, if you really want to incorporate revision number too then that can be done.
The real big problem I have is this "SE/TE" nonsense. I can't get that from an integer unless it is a predefined list of version names - which means you can't add extra ones at a later date.
If revision is an always-growing number and doesn't reset with each new version then why can't you just scrap revision? - that is what Build is for! Do you really need to know exactly how many times you have compiled the exe?

Also I think about UseRockPatch=[bool] tag and RockPatchVersion=[??] tag (in RULESMD.INI).

That's a good idea and will help, however Launch Base will already help one step further by not loading the game in the first place - it will tell the user that RP is not installed, or not correct version before launching the mod. The above safeguard will, of course, help in non-LB situations.