This is a Sticky over at ofp Multiplayer The same apply for arma. it is important for server admins to know about modified files. and mod makers to make addons that dont reconfig defult addons. if the server is not useing it but the player still has theys modified files in my book thats a cheat. not talking about sounds but mods like SLX whare you can pull out a knife and kill some one with it. but the realy simple way Prevent mods off youre server is to make it Equalmodrequires=1 but people cant conenct if thay have a mod folder Suicidesquad.com does this and a few others.
There is currently quite busy discussion about modifications of config.bin (or its text equivalent config.cpp) in other topics of this forum. Let me explain why we implemented "config modified" message.
When modifying config.bin, you can control many aspects of the game, some very important (like reload times or other waepon, ammunition or vehicle parameters, some not that important, like weapon sounds or other "minor" things.
We considered a lot what parts of config should be protected against cheating, and after some thinking and experimentation we decided that modifing almost any field in config can be used to get some advantage.
Let me consider two favourite config.bin modification types that seem innocent: sound replacement packs and face set replacements.
Sound replacement packs
Most sound replacement packs currently available replace original ingame sounds by other sounds, that are considered more reallistic or simply nicer by its creator. Exactly the same technique can be used for cheating: consider replacing very quite H&K sound (or sound of footsteps of eastern soldiers) by some distinct and very loud tone. This would give you quite big advantage, as enemy would be unable to approach you unheaderd.
Face set replacements.
Most common face set replacements replace original faces with some cammo type / spec ops faces. The very same same technique could be used for cheating: imagine replacing all faces with bright yellow face. This would make spotting enemy much easier.
While the message about modified config does not necessary mean given player is cheating, it tells you is it is impossible to guarantee he is not, as identical techniques can be used for non-cheatig and cheating config modifications. When seeing this message, it is upon your decision if you will believe the player when he tells you he is not cheating.
If you are using some config modification that is causing this message, you should understand why some people / servers may be unwilling to play with you. They see you are using modified config and they cannot know if you modified it in cheating or non-cheating way. If they want to stay on the safe side, they will often kick you or even ban you from the server. Seeing the number of people that used config modification to cheat, you can hardly blame them.
Is modified "config message" reliable?
The answer is not easy. We can tell it was not reliable before 1.45, as addons installed to Addons folder were able to modify some protected config entries. We fixed this and we are convinced this is no longer possible in 1.45. Unless you modify your config, you should not see this message, no matter what unofficial addons you have installed in your Addons folder.
Why not disconnecting player with modified config?
As I wrote above, we were not sure in previous version if our test of config modification were reliable and we did not want to kick any player using any addons unless they really used config modification.
We think that the detection is working right since 1.45, but we want to wait a little to be sure. Once we will see this really works well, we will implement server side option that will automatically disconnect players using config modification. Remmeber: this will be server side options and server administrator will be able to decide if he wants this feature or not.
Can unofficial addons cause "modified config" message?
If you have unoffical addon installed into following folders:
it should not cause this message. Unfortunatelly there was bug in 1.42 and before which caused some addons could modify protected parts of config and the message was shown. This should be no longer possible in 1.45 and later.
If you think you have any addon that installs only into folders listed above and it shows the message in 1.45 and later, please send it to email@example.com for investigation.
ok ok but how do i turn on filechecks? copy and paste the checkfile commands from my server config over to youre server config.