Repository navigation
feature: config file, config cvar and forced cvars for plugin settings, Deathmatch weapon rotation - #5
Merged
Conversation
…s, Deathmatch weapon rotation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A registry entry can describe a plugin's config file and the cvars it forces, and Deathmatch now does.
config_cvar,config_default,config_shippedandforced_cvars, validated, with the shipped default checked againstconfig_schema(including duplicate entries, which make Deathmatch drop the whole file)dm_modes_fileas its config cvar, and the 107 cvars it resets on every map