Hi. Thanks for the reply. I was already using a similar setup with arrays, but my logic was faulty somewhere. Didn´t find where exactly because today I erased all those nodes, and decided to rethink it from scratch.
Also, because this will be for a mobile game, I don´t want to be able to check another box, until you have unchecked the previous one. That way, if you misclick (mistouch) nothing really happens.
For anyone with the same problem, let me explain what I did because it´s a clean solution and it works very well.
So, I have 9 check boxes, numbered 0-9.
I created TWO variables, which I called “RequestedBox”, and “CheckedBox”. Checked box defaults at 10 (so that by default isn´t any valid number) and RequestedBox defaults at 11 (not important. It just has to be different from the other variable default).
Now, when any of the boxes gets clicked by the user, I store that box value in “RequestedBox”.
If CheckedBox is 10 (everything unchecked), I check the appropiate box (and then I do some other stuff that I need with text inside) and set “CheckedBox” to that number.
If it´s not 10, that means something is already checked, so now I compare if “CheckedBox” and “RequestedBox” are the same number or not.
If they are equal it means the user is clicking on the same box already checked. So I uncheck it, and restore “CheckedBox” to its default value of 10.
If they are NOT equal it means the user clicked some other box different to the checked one, so I uncheck the box the user just clicked (so in effect he´s not doing anything by clicking)
This works wonderfully. Elegant, clear on the BP screen (well…clearer) and simple.
Sometimes coming back with a fresh mind is all you need…