Just easy right? So please, show me your coding skills so I can see how you would keep the 2 separate.

https://github.com/Happimir/ set of different projects i have worked on. Here's psuedocode on how to accomplish this: if(playerObject.selectedGameMode() == "PvP") { game.loadMap(); game.setTeams(); game.setPvPTraits(); // this is where you set the specific buffs, you can already tell if someone is doing pvp or not. } Happy?

Now imagine doing that over for every map with the addition of new weapons while also changing specific lines because the the specific weapon is too strong. Are you happy now?

The set of weapons that are relevant at end game, versus the set of all weapons the game offers makes this a manageable issue. It is bad code practice to make your application have to apply these changes to all things. Instead, make an interface that has two separate implementations. Assume you have an interface called GameSettings. It can then be implemented via two concrete classes of PveSetting and PvpSetting. The methods are shared, but each one is unique in its own way. A prime example of this interface idea is how many languages implement the List interface: ArrayList and LinkedList. They both fulfill the same role, i.e giving you a list object, but their strengths and weaknesses differ greatly

They could do that. But you also still know that the game is always evolving right? The influx of weapons for the dlc's would be pretty varfying so just saying It's bad coding to make manual changes that are not just all across the board is not true. Besides do you know value by value the coding of the weapons? How many different modifications and it has and all? Human error will also play into this. No matter how much work is done, a single line of coding can mess up perhaps a balance patch that would be for pvp but instead is in pve.