Bug #754

Legacy mod's etconfig.cfg gets affected by other mods

Added by Saukko over 5 years ago. Updated over 5 years ago.

Status:New% Done:


Target version:2.78
OS: Arch:


So basically how does this work:

You have etconfig.cfg in legacy mod folder, alright.
But the things take a bad turn right after you play in any other mod.
When you play in another mod, it will take all the CVARs from that specific mod and put them into legacy mod’s etconfig.cfg.
So in my opinion if there are any mod specific CVARs it should keep them for the mod itself and not put them into the legacy etconfig.cfg or any other. Every mod should have its own etconfig.cfg to work with.



#1 Updated by IR4T4 over 5 years ago

  • Target version changed from 2.72 to 2.78

Also available in: Atom PDF