Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ETLegacyTeam opened this issue Mar 5, 2020 · 0 comments
Open

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

ETLegacyTeam opened this issue Mar 5, 2020 · 0 comments
Labels
🐞 Bug Something isn't working cat: general Category engine (client/server) P3: Normal Priority 3
Milestone

Comments

@ETLegacyTeam
Copy link
Member

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

@ETLegacyTeam ETLegacyTeam added 🐞 Bug Something isn't working cat: general Category engine (client/server) P3: Normal Priority 3 labels Mar 5, 2020
@ETLegacyTeam ETLegacyTeam added this to the Future milestone Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Bug Something isn't working cat: general Category engine (client/server) P3: Normal Priority 3
Projects
None yet
Development

No branches or pull requests

1 participant