selective-1b1 author here!
Yep, that does mean exactly that!
It’s probably not the absolutely nicest looking piece of code I ever wrote, however it’s reliable and performative across all platforms and devices (afaik, can’t test for every single contingency).
It’s much more powerful than simply that though:
selectiveOneByOne
allows one to apply 1b1 to only specific clozes (e.g. only c1 and c2)minNumberOfClozes
allows you to set a minimum number of clozes for which the 1b1 feature should appear (e.g. for every cloze with more than three instances in a note [so “c1 c1 c1” would activate, but “c1 c1” would not])alwaysOneByOne
allows you to select whether or not the 1b1-Field needs to be non-empty to activate 1b1 (to just activate any non-empty string will do)
So one could run a custom setup where only specific clozes of specific cards get the 1b1 treatment, whereas someone else could have every cloze with >4 instances do the same.
It’s a bit complicated to granularly go through every single possible set-up one could use, however that provides exceptional flexibility to the people that seek it.
Some people dislike 1b1 completely, some only for clozes with a lot of instances etc.
Most people, however, just use our default setting (currently it is 1b1 for all clozes with >=3 instances) which has been received quite well so far