I have 13 players on my Brave New Oarc server, and we're trying out Better Linked Chests mod. I love the ability to add a name to the address, but you keep a single array of each name/address all players. That only works if you are playing with one force. You would need to change:
global.name_id_table={}
You could do a few things to fix this - one of which is to use the first address for the index of the force.
The next is to keep a list of names/address based on each force.
if not global.name_id_table[player.force.name] then
global.name_id_table[player.force.name] = {}
end
Then everywhere you use global.name_id_table you would add the players force.name
Linked-Chests base code makes sure that each force only has access to the contents of boxes, even with the same address, for each force. You would change to track the names that each team assigns to the address. Every team can use 1:0:0:0 for different contents, without their contents being shared between teams.
If this is not clear, I can show you after logging back into a game I host with 13 players, that my steel box is now named plastic, and every other name is messed up - but the contents are good, and not mixed up with other teams.
I have modified how Ender-Linked-Chests work to add addressing and logistic wire within my Brave New Oarc code. If you don't want to address this, I can just add the address helper UI to that. I did modify Alien Modules to work for Forces, so that would be a good example that is not too much code to view how the single array was modified to support something like global.name_id_table[player.force.name]
Let me know if there is something I can do to help, this is a nice addition to Oarc, if you fix the naming. For now I have to list it as not supported.