PlayerUnknown’s Battlegrounds developer Bluehole has updated the list of bannable offences in the game.
Now, editing config files in Battlegrounds will get you banned. Players noticed this new update after a discussion ensued about whether or not it’s fair to edit config files to get rid of the fog, one of the many features added with the September patch.
The statement previously read, “We don’t recommend users to alter their default game configuration .ini files or launch options. If advanced users wish to do so, we cannot guarantee the game will work as intended and are unable to provide support related to any changes to these files.”
Now, the answer to the “Is it okay to edit configuration files?” question reads, “No, editing any game files to gain an unfair advantage is against the Rules of Conduct. This includes changing any game configuration files to result in changes that cannot be made via the in-game settings menu.”
Players on Reddit are very split over this, since the new language seems to cover everything from adding small adjustments to removing big features like fog or disabling shadows in order to gain an advantage. Bluehole previously had a lax approach to .ini file editing, but it now looks like things are tightening up.
Andro Dars, community manager for PUBG, chimed in to say that the change was made to make the statement clearer, not add any confusion. “[Sic] this far, the only group of people who have been banned for changing game files are those who have removed textures from the game,” Dars pointed out.
Unfortunately, Dars did not specifically comment on the many other reasons player edit config files for, such as locking the frame-rate, adjusting some graphics options beyond what’s possible through the in-game menu, and more. This effectively lumps everyone who edits .ini files together, creating a grey area where only the most egregious risk a ban.
Editing config files in PlayerUnknown’s Battlegrounds will now get you banned, so don’t try to get rid of the fog posted first on http://ift.tt/2k0LiGW
No comments:
Post a Comment