You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
-*S
The text was updated successfully, but these errors were encountered:
Author: @saukko28 (Saukko)
Date: 2015-01-03
Redmine Issue: 754, https://dev.etlegacy.com/issues/754
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.
-*S
The text was updated successfully, but these errors were encountered: