thinking also about how to do that some elegant way, but maybe worth mentioning that connecting route object to even 128 object can be done in a minute or two using the [thispatcher] scripting / "script connect" message + a counter and uzi...
Django that is pretty nice and succinct coding! before I start manually connecting 128 bpatchers to receivers...is it possible to create one bpatcher with 'receiver#' (not sure of syntax) embedded with code so that as I duplicate it in the parent, max increments it with a unique identifier?
I think i've seen this before in other patches but i'm uneducated with syntax...
You're totally getting credit for this bit of code! Thanks!
mssngmrblz: ok, it took me bit more than 1-2 minutes, because messages won't replace $1 with number, if the $1 is closed in . so i had to use combine object. but maybe 3-4 minutes and when you have it built, you can reuse. I think this is a must, if you work on a patch with 128 bpatchers...
(please note one stupid thing i did in this example was giving the scripting names starting with . that was stupid, because the inlets/outlets are numbers from 0 and you usually want to connect first of the many objects to first of the many inlets/outlets. so you better start with  on end of the scripting name, and then just duplicating or copy/pasting will create , , ...[n])
+1 for the toolbox...connecting 128 objects can be done with one mouse selection and a keystroke.
When you originally create the bpatchers, give them the array name: my_bpatcher
...then when you duplicate, they'll auto-name with   etc.
Problem: How to give each one an argument? Arguments won't auto-increment with this method.
Possible solution: [thispatcher] to [sprintf script sendbox my_patcher[%u] argument %u]
Can't test it now, but can [thispatcher] send a message to [bpatcher] to set its arguments?
If so, you're done with a [route #1] in the bpatcher.