Is it possible to get a ban for change Engine.ini?

[GOOD FELLA]

Judging by the Easy Anti-Cheat policy, this anti-cheat takes into account the replacement or addition of files to the game. That is, really software (let’s say a cheat) that can give cruel advantages, well, in terms of WallHack, SpeedHack, hacking of a rank, blood points, perks, add-ons, etc. Without offense is considered the replacement of icons and avatars of characters. But going through the forums Reddit and official DBD forum, I realized that people get banned for replacing icons and avatars. Ah, here for Engine.ini and GameUserSettings
In short, for FPSUP in YouTube, and indeed on the Internet there are many configs.
But, all configs completely remove the shadow and fog. Also fire and other effects.
Which really gives a good advantage for a maniac, but not for the Surviv.
There are, of course, configs that still additionally give a big red glow to the maniac, but this is already really imbalanced and gives a good advantage for the survivor.
I would like to know if it is possible to get a ban if you install such a config.
And if so, which ban? Temporary? Game? or vac?
My friend plays with that config 2 months, and don't get a ban.
Sorry for my bad English.

[Prydain]

The general stance is that the devs say don't do it, but they won't actively do anything about it either. However if EAC ( The games anti-cheat ) flags and bans you over modifying the files, they won't help you get unbanned. So its basically a grey area of do it at your own risk. They won't actively ban you for doing it, but won't help you if the automated system bans you.

[Eagle_of_Fire]

In any game in which there is an anti-cheat, you have to expect the anti-cheat software to do a checksum check on files. If you open and save over a file, the checksum change.

You can guess the rest from here.

[GOOD FELLA]

Originally posted by Prydain:

The general stance is that the devs say don't do it, but they won't actively do anything about it either. However if EAC ( The games anti-cheat ) flags and bans you over modifying the files, they won't help you get unbanned. So its basically a grey area of do it at your own risk. They won't actively ban you for doing it, but won't help you if the automated system bans you.

But the EAC does not see the editing of the config, no?

[Twink Enjoyer]

Originally posted by CampeR:

Judging by the Easy Anti-Cheat policy, this anti-cheat takes into account the replacement or addition of files to the game. That is, really software (let’s say a cheat) that can give cruel advantages, well, in terms of WallHack, SpeedHack, hacking of a rank, blood points, perks, add-ons, etc. Without offense is considered the replacement of icons and avatars of characters. But going through the forums Reddit and official DBD forum, I realized that people get banned for replacing icons and avatars. Ah, here for Engine.ini and GameUserSettings
In short, for FPSUP in YouTube, and indeed on the Internet there are many configs.
But, all configs completely remove the shadow and fog. Also fire and other effects.
Which really gives a good advantage for a maniac, but not for the Surviv.
There are, of course, configs that still additionally give a big red glow to the maniac, but this is already really imbalanced and gives a good advantage for the survivor.
I would like to know if it is possible to get a ban if you install such a config.
And if so, which ban? Temporary? Game? or vac?
My friend plays with that config 2 months, and don't get a ban.
Sorry for my bad English.

i havent heard of anyone getting banned for changing anything in those configs, these config changes have been used for years and im pretty sure some pretty big youtubers and streamers use the config since i dont see fog in their videos.

[GOOD FELLA]

Originally posted by Eagle_of_Fire:

In any game in which there is an anti-cheat, you have to expect the anti-cheat software to do a checksum check on files. If you open and save over a file, the checksum change.

You can guess the rest from here.

Logically, when a game starts, all files are checked, including Engine.ini and GameUserSettings.ini. And then you can get a ban. It’s just that EAC is too fast, faster than VAC. But people calmly play with such settings, even on streams it can be seen. And they do not care deeply.

[Eagle_of_Fire]

Originally posted by CampeR:

Originally posted by Eagle_of_Fire:

In any game in which there is an anti-cheat, you have to expect the anti-cheat software to do a checksum check on files. If you open and save over a file, the checksum change.

You can guess the rest from here.

Logically, when a game starts, all files are checked, including Engine.ini and GameUserSettings.ini. And then you can get a ban. It’s just that EAC is too fast, faster than VAC. But people calmly play with such settings, even on streams it can be seen. And they do not care deeply.

Of course they do. This is why you have cheaters ruining the game... In any MP game I ever played.

I just played a game, like 20 mins ago... The guy was playing Huntress and like 4 times I got a hatchet throw at my head while I could be 100% sure they didn't know I was there. The only reason why I didn't die is because I played a lot of Huntress myself and he was so bad (probably new to Huntress) that I evaded 8 out of 11 hatchets thrown at me.

In case you wanted to know, two times out of the three hits I didn't even see her or hear her heartbeat. One of those times I was almost at the other side of the map and I could see her aura because of my perk (a survivor was on the hook).

So anyways... I'm not saying there is NO cheaters. I'm saying that if you actually try to cheat you have to expect the anti-cheat to be on your back. One of these days or right after an update or whatever, they'll get you if you do it. (If they care about it too...)

[GOOD FELLA]

Originally posted by Happy Thanksgiving:):

Originally posted by CampeR:

Judging by the Easy Anti-Cheat policy, this anti-cheat takes into account the replacement or addition of files to the game. That is, really software (let’s say a cheat) that can give cruel advantages, well, in terms of WallHack, SpeedHack, hacking of a rank, blood points, perks, add-ons, etc. Without offense is considered the replacement of icons and avatars of characters. But going through the forums Reddit and official DBD forum, I realized that people get banned for replacing icons and avatars. Ah, here for Engine.ini and GameUserSettings
In short, for FPSUP in YouTube, and indeed on the Internet there are many configs.
But, all configs completely remove the shadow and fog. Also fire and other effects.
Which really gives a good advantage for a maniac, but not for the Surviv.
There are, of course, configs that still additionally give a big red glow to the maniac, but this is already really imbalanced and gives a good advantage for the survivor.
I would like to know if it is possible to get a ban if you install such a config.
And if so, which ban? Temporary? Game? or vac?
My friend plays with that config 2 months, and don't get a ban.
Sorry for my bad English.

i havent heard of anyone getting banned for changing anything in those configs, these config changes have been used for years and im pretty sure some pretty big youtubers and streamers use the config since i dont see fog in their videos.

Yes, sure. Check "TrueTalant" YouTube channel.
He has no blur, no fog and no rain effects. And he has had this since 2017. But at the same time he has a red rank and a lot of played hours.

[GOOD FELLA]

Originally posted by Eagle_of_Fire:

Originally posted by CampeR:

Logically, when a game starts, all files are checked, including Engine.ini and GameUserSettings.ini. And then you can get a ban. It’s just that EAC is too fast, faster than VAC. But people calmly play with such settings, even on streams it can be seen. And they do not care deeply.

Of course they do. This is why you have cheaters ruining the game... In any MP game I ever played.

I just played a game, like 20 mins ago... The guy was playing Huntress and like 4 times I got a hatchet throw at my head while I could be 100% sure they didn't know I was there. The only reason why I didn't die is because I played a lot of Huntress myself and he was so bad (probably new to Huntress) that I evaded 8 out of 11 hatchets thrown at me.

In case you wanted to know, two times out of the three hits I didn't even see her or hear her heartbeat. One of those times I was almost at the other side of the map and I could see her aura because of my perk (a survivor was on the hook).

So anyways... I'm not saying there is NO cheaters. I'm saying that if you actually try to cheat you have to expect the anti-cheat to be on your back. One of these days or right after an update or whatever, they'll get you if you do it. (If they care about it too...)

I completely agree, but this is one of those questions when the correct answer is not to be expected.
Simply, if you look at the other side, cheating is not there, but it gives a good overview, which is important for this game.

[Old Habits Die Hard]

The Devs have always been able to lockout any alterations made in any of the ini files that they wanted too, and EAC never has and likely never will check ini files, this is why some changes you can make freely such as:

bUseVsync
FrameRateLimit

Starting with 3.6.0 the only changes allowed to be made to Engine.ini are turning off smoothframes. This means anything that people were previously using that were under [/script/engine.rendereroverridesettings] such as r.DefaultFeature.AntiAliasing=0 will no longer work.

So no more bright-as-the-sun-neon-see-from-40m-away red stains etc.

[Local Dog]

Originally posted by Breakaway:

The Devs have always been able to lockout any alterations made in any of the ini files that they wanted too, and EAC never has and likely never will check ini files, this is why some changes you can make freely such as:

bUseVsync
FrameRateLimit

Starting with 3.6.0 the only changes allowed to be made to Engine.ini are turning off smoothframes. This means anything that people were previously using that were under [/script/engine.rendereroverridesettings] such as r.DefaultFeature.AntiAliasing=0 will no longer work.

So no more bright-as-the-sun-neon-see-from-40m-away red stains etc.

Can i ask where did you read that or they stated it on stream? Just curious

[Old Habits Die Hard]

Originally posted by Ʇhe aposʇle:

Originally posted by Breakaway:

The Devs have always been able to lockout any alterations made in any of the ini files that they wanted too, and EAC never has and likely never will check ini files, this is why some changes you can make freely such as:

bUseVsync
FrameRateLimit

Starting with 3.6.0 the only changes allowed to be made to Engine.ini are turning off smoothframes. This means anything that people were previously using that were under [/script/engine.rendereroverridesettings] such as r.DefaultFeature.AntiAliasing=0 will no longer work.

So no more bright-as-the-sun-neon-see-from-40m-away red stains etc.

Can i ask where did you read that or they stated it on stream? Just curious

I'm not sure if they did I don't bother watching their streams lol

But I noticed when switching to the PTB that it erased the lines I had in my Engine.ini to turn off AA which is:

[/script/engine.rendereroverridesettings]
r.DefaultFeature.AntiAliasing=0

And left smoothframes in there which is:

[/script/engine.engine]
bSmoothFrameRate=False

So I decided to try various things to see what it would allow, and found that the only thing it would allow was smoothframes=false and wouldn't allow any of the commonly used override settings such as

r.EmitterSpawnRateScale=0
r.LightFunctionQuality=0
r.DefaultFeature.Bloom=False
r.DefaultFeature.MotionBlur=False
r.DefaultFeature.LensFlare=False
r.DepthOfFieldQuality=0
r.DefaultFeature.AmbientOcclusion=False
r.DefaultFeature.AmbientOcclusionStaticFraction=False
r.DefaultFeature.AntiAliasing=0

Just to name a few, I tried all of them and they are all ignored completely.

[GOOD FELLA]

Originally posted by Breakaway:

The Devs have always been able to lockout any alterations made in any of the ini files that they wanted too, and EAC never has and likely never will check ini files, this is why some changes you can make freely such as:

bUseVsync
FrameRateLimit

Starting with 3.6.0 the only changes allowed to be made to Engine.ini are turning off smoothframes. This means anything that people were previously using that were under [/script/engine.rendereroverridesettings] such as r.DefaultFeature.AntiAliasing=0 will no longer work.

So no more bright-as-the-sun-neon-see-from-40m-away red stains etc.

That's cool. Finally there will be an equal game. Can I find out where you got this information?

[Old Habits Die Hard]

Originally posted by CampeR:

Originally posted by Breakaway:

The Devs have always been able to lockout any alterations made in any of the ini files that they wanted too, and EAC never has and likely never will check ini files, this is why some changes you can make freely such as:

bUseVsync
FrameRateLimit

Starting with 3.6.0 the only changes allowed to be made to Engine.ini are turning off smoothframes. This means anything that people were previously using that were under [/script/engine.rendereroverridesettings] such as r.DefaultFeature.AntiAliasing=0 will no longer work.

So no more bright-as-the-sun-neon-see-from-40m-away red stains etc.

That's cool. Finally there will be an equal game. Can I find out where you got this information?

I just tried it myself, if you make a change to the ini and the game overwrites it that means you're not allowed to change it and it's being ignored (and it writes in what value is being used if any), if it leaves it alone it's allowed.

All of those changes will work on 3.5.2 but don't work in 3.6.0.

I've noticed on the main dbd forums people are starting to realize it and complaining because the AA disable doesn't work but so far as usual bhvr hasn't commented.

[Prydain]

Originally posted by CampeR:

Originally posted by Prydain:

The general stance is that the devs say don't do it, but they won't actively do anything about it either. However if EAC ( The games anti-cheat ) flags and bans you over modifying the files, they won't help you get unbanned. So its basically a grey area of do it at your own risk. They won't actively ban you for doing it, but won't help you if the automated system bans you.

But the EAC does not see the editing of the config, no?:gng:

It shouldn't no. But in the case that it does and EAC bans you, the devs are just saying they won't help you out there. Fairly sure I remember people contacting EAC and even they said they don't ban for it but its a grey area in general.

[Old Habits Die Hard]

For the record I only personally used the disableAA lines and smoothframes because BHVR posted the lines for disable AA and I hate smoothframes and I highly doubt anyone could possibly consider them to be "cheating" but I know the other overrides are the most commonly used ones because I'm a nerd and like to learn everything I can about things I enjoy.