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

Adding a demofilter #32

Merged
merged 6 commits into from
Jun 16, 2019
Merged

Adding a demofilter #32

merged 6 commits into from
Jun 16, 2019

Conversation

Ch0wW
Copy link
Contributor

@Ch0wW Ch0wW commented Jan 15, 2019

Requested by the community, to be able not to record everything from every gamemode.

I also added these options under the "Network options" submenu.

…ing.

If splitnetdemos was enabled when the autorecording was previously enabled, it properly disables it.
@Ch0wW
Copy link
Contributor Author

Ch0wW commented Jan 15, 2019

Also, here's a screenshot of how it looks ingame.
image

Copy link
Contributor

@seanmleonard seanmleonard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks sound. I'm just leary about introducing 7 more CVARs. Perhaps there's another way to encode the filter options without so many CVARs.

@Ch0wW
Copy link
Contributor Author

Ch0wW commented Jan 31, 2019

The problem, is that I first planned a byte system, but it'd be absolutely messy for the player if modifying from the .cfg . Individual CVARs were far easier to manage in case of a problem though.

@nstlaurent nstlaurent changed the base branch from master to development March 27, 2019 11:15
@@ -216,6 +226,11 @@ value_t OnOffAuto[3] = {
{ 2.0, "Auto" }
};

value_t DemoRestrictions[2] = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whys is 0 allow and 1 restrict? This is OK as far as setting in the application. This is confusing in odamex.cfg because having cl_autorecord_filter_duel set to 1 would imply that it would record but it's the opposite.

To me it seems we should flip the DemoRestrictions values and default the cvar to 1.

@nstlaurent nstlaurent merged commit 922392d into odamex:development Jun 16, 2019
AlexMax pushed a commit that referenced this pull request Feb 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants