Bad idea to match Lockpick RCM version number to Atmosphere

[Trp202]

Thank you for new ideas. The one matching the version number to the atmosphere release seems bad in different ways.

First: Lockpick RCM is VERSION 1.12.0, and actually there is no atmosphere version with this release number.
Atmosphere is as now at 1.11.2 and would not logically be compatible with Lockpick 1.12.0.
Second: It makes much more logic to match the Lockpick RCM match to the actual working firmware on the Switch. For example Lockpick 22.5.0 with Firmware 22.5.0, and an upgrade version for Lockpick would look like Lockpick v22.5.0 (2) or Lockpick v22.5.0_02

[Kofysh]

Thank you for new ideas. The one matching the version number to the atmosphere release seems bad in different ways.

First: Lockpick RCM is VERSION 1.12.0, and actually there is no atmosphere version with this release number. Atmosphere is as now at 1.11.2 and would not logically be compatible with Lockpick 1.12.0. Second: It makes much more logic to match the Lockpick RCM match to the actual working firmware on the Switch. For example Lockpick 22.5.0 with Firmware 22.5.0, and an upgrade version for Lockpick would look like Lockpick v22.5.0 (2) or Lockpick v22.5.0_02

Yeah, fair point. Matching to Atmosphere's version doesn't really hold up here, Lockpick is at 1.12.0, Atmosphere's at 1.11.2, and there's no meaningful link between the two numbers anyway.

Tying it to the actual supported firmware makes more sense since that's what people actually care about when picking a release. Something like v22.5.0 for the firmware it targets, and v22.5.0_02 (or similar) for a follow-up fix on that same target, would be a lot clearer than chasing Atmosphere's numbering.