FWIW this grew as a historical thing from the time it was "repeat count" rather than "play count" and my improvements were to gradual to tackle it between MS2 and MS3.
When the "big rewrite" of interpretation logic for 3.5 happened, I didn't feel like breaking compatibility within the 3.x releases.
But to me, for 4.x it indeed would be a "Good Thing (tm)" to remove the '+1' from the logic. There are a lot more UX improvements possible, which likely will have to wait for later 4.x implementations, but at least the logic underlying value can be corrected between major versions.
Comments
Not a bug, works as designed. At best a feature request, AKA Suggestion
"Workaround" is to just use it as documented in the handbook
FWIW this grew as a historical thing from the time it was "repeat count" rather than "play count" and my improvements were to gradual to tackle it between MS2 and MS3.
When the "big rewrite" of interpretation logic for 3.5 happened, I didn't feel like breaking compatibility within the 3.x releases.
But to me, for 4.x it indeed would be a "Good Thing (tm)" to remove the '+1' from the logic. There are a lot more UX improvements possible, which likely will have to wait for later 4.x implementations, but at least the logic underlying value can be corrected between major versions.