Hey @danielguti,
That’s a good point!
The indexes in OSC values are 0-based, so the first section is 0, the 2nd is 1, etc.
However, the jumpToSection command was introduced in an earlier version and used a 1-based index which at the time I thought would be easier to understand but now makes it more confusing when used in combination with the newer OSC values.
I can’t change this behavior without breaking existing setups, but to convert from the OSC value to the command value, you can just add 1. For example, if queuedIndex is 5, send /setlist/jumpToSection 6 to jump to that section.
I hope this helps! 