The misinformation and assumption posted elsewhere warrants a little explanation I think.
This feature is not
the work of EvenBalance, it's not
the work of EA/DICE, It's nothing
to do with Origin.
This feature was thought of and coded by MaydaX in his role as PBBans website and Hub developer.
At the moment the Enforce MBi Bans (EA GUID)
option is only available to PBBans streaming admins.
It's not on by default and the relevant flag must be selected by the streaming server admin.
The newer EA games(BFBC2, MOH and BF3) all have a common pbguid linked to their EA account.
Previously, when a banned MOH player joined a BFBC2 server, provided he had not raised a cheat violation on BFBC2, he could do so with impunity because the Hub only checked his pbguid against the BFBC2 MBI (Master Ban Index)
Now the option is there for PBBans streaming admins to allow the Hub to check every incoming player against the BFBC2 / MOH / BF3 Master Ban Indexes.
If the incoming players pbguid is found on any of the 3 he will not be able to join the server.
It should be noted that the Hub is doing the checking and not the server so no game server resources are used in the checking process.
It's something akin to a zero tolerance policy being enforced by the Hub on the newer EA game releases that share a common pbguid.
It's entirely optional, so if a server admin disagrees with with any of the above, all he has to do is not check the Enforce MBi Bans (EA GUID)
This feature is unique to PBBans but will probably go the way of every other feature we have pioneered by being copied in its entirety by other sites with no credit given, seems to be the way of the world these days