|
I'm not sure the logic is completely correct here.
Bikey'ing does not compare or prevent differing versions within mods, so these conflicts continue to be a problem if not everyone has used the PwS Repo and kept it up-to-date.
Bikey'ing stops people running non-allowed mods which means you can prevent mod-conflicts or those mods which are known to produce lag or are buggy.
It is known that some mods produce lag (high server load or high bandwidth usage) which can equate to server/client fps drops.
On a non-bikey'd server these mods can be run.
Therefore on a non-bikey'd server fps can suffer.
Conversely on a bikey'd server where the mods have been tested for compatibility and with everyone downloading and running up-to-date versions, fps and server stability are likely to be higher.
When we changed from non-bikey'd private server Op's to bikey'd, there was a massive difference in server and client fps, plus almost total stability. Much of this was because we reduced the mod count and tested everything carefully, reducing the probability of running mods that cause problems.
-nologs is very important for client-side FPS. I'd like to see proof of how not running this command can affect other clients or the server though.
So my conclusion is that there is no point in bikey'ing a server when the mod list on it is huge, as some of those mods will be buggy or conflict and fps/stability will as a result still be poor.
If the mods are restricted to a core set which have been tested and approved I believe public server fps and stability would improve. But probably most client problems are caused by the client's set-up, rather than coming from the server (such as -nologs, or running graphical settings beyond the client hardware's capability).
HOWEVER!
Much of the attraction of the public server is that people can join with any mod set they have running so long as it includes the pre-requisites, such as the Map and Alive.
People can use it as a sandbox to test out new mods and discover cool things they didn't know they were missing ("I can't see your gun/shoes/hat/vehicle" - "because you don't have this mod, it's soooo cool" - "ok I'll get it").
The barrier to getting on the server is lower without bikey'ing (although if this is really the prime argument we should just run vanilla ArmA!).
For these benefits, we lose some stability and open up the possibility of cheating/hacking, but this seems relatively rare thankfully.
So when I go on the public server I expect a different experience to that which we get as 3CB on private Op's. Currently I'm happy with that balance.
|
