This simply illustrates the fact that "writing" code with interface builder has it deadly sins which should be avoided.
Don't rely on all those "interface builders", "Designers" and other stuff designed to please the weak-minded :-) in serious work. While helping in designing something visual — to certain extent, those tools create absolutely non-supportable code and problems like yours. Marketing people pretend that would they promote "automates" programming, but in fact it makes the programming
much more manual
and suggests an inexperience developer to repeat the same mouse click to create identical code instead of using various kind of abstraction and simple parametrization.
You case is a bright example of such a false "help" from an interface builder. If you programmed your functionality manually, you could find an automated solution of your problem. In particular, look — you have 6 player objects. This is already bad; really maintainable code should be abstracted from the constant 6, I mean, this constant should be a parameter of design — you change it and get any number of objects.
In your case, you could easily use the array of pointers to players. For code examples, see:
http://stackoverflow.com/questions/1123434/objective-c-how-to-implement-an-array-of-pointers-in-a-method-declaration[
^].
—SA