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

Author's opinion on enabling alwaysrun in SP? #278

Open
dobosken opened this issue Mar 10, 2020 · 1 comment · May be fixed by #282
Open

Author's opinion on enabling alwaysrun in SP? #278

dobosken opened this issue Mar 10, 2020 · 1 comment · May be fixed by #282

Comments

@dobosken
Copy link
Contributor

dobosken commented Mar 10, 2020

Howdy.

What is the author's stance on allowing alwaysRun to be enabled in singleplayer?
It is not vanilla behaviour, however personally I don't foresee it negatively affect any Doom 3 player no matter their stance on the subject.

Those that want it, get it. Those that don't want it, won't have to change a thing as it's not the default behaviour.

My current implementation just rips out the multiplayer check for that specific feature. It is still controlled by the cvar and the toggle in the multiplayer menu.
I assume the main thing that would have to be addressed here, is the fact that the toggle from the multiplayer menu would now affect the game in singleplayer.

Adding another cvar just to control the same feature in sp seems superfluous to me. What would be a good approach, assuming this feature is accepted by the author?

@DanielGibson
Copy link
Member

hmm I would indeed use a separate cvar for singleplayer, otherwise I wouldn't mind the feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants