well i hope not.. i hope the game stays at 32 players max.. why? because 50 player servers are a lag fest already and the performance is suffering very bad (every single 50player server i played on was lagging and my fps weren't that good ether)
...and now imagine UT3 engine plus 50player servers ....uuuhhhaaa *goosebumps*
+
maps are ALL sooo imbalanced with >33player setup. if rohos maps would be designed for 50 player(which i hope is not) from the start it would be an other story.. but than u would need to play clanmatches with 16vs16 or something and this is ****ed up the more players needed the higher the chance that teams cant field min of 16...
so i my eyes default map layout should be for 32players
The problems of one game are not automatically going to be problems for another game.
RO:Ost was designed for 32 players, all the maps where, the netcode was, it was all ment to be 32 max. So yes, when they added in 50 player support later, it did create some problems, mostly because server admins decided to run it even though they coulden't and shoulden't (on servers that where not powerfull enough to do it, and they still had all the 32 player stock maps in their rotation, when they should have been running larger custom maps to support the extra players).
There where good 50 player servers too, that did run good custom maps for this sort of thing, and where hosted on beefy enough machines, but for every one of thouse, there where probably 3 others that where laggy because the server wasen't powerfull enough, and which ran maps that where far to small.
HoS is designed from the ground up to support 64 players, all the maps are larger to facilitate it, and the UE3 engine is made to do this, it's optimized for it (the fact that it supports multiple cores is a huge step up in this regard, the UE2.5 engine of Ro:Ost didn't have that), and we've seen UE3 do it just fine in other games.
So no, the fact that Ro:Ost had problems with this (mostly due to server admins wanting to bite off more than their server could chew) does not mean that HoS will, HoS is designed for this, RO:Ost was not.