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

QOL In Multiplayer games only, Disable new game and quit game menu options when player is Dead #7749

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

wkdgmr
Copy link
Contributor

@wkdgmr wkdgmr commented Feb 12, 2025

Quality of life change for Multiplayer game sessions only. This is to help prevent accidental gear loss when navigating the menu upon death.

There is a lot of Risk in navigating the menu when the player is dead and their loot is on the ground. One wrong click in a Multiplayer session that is not a rejoinable game can be devastating

QoL

image

image

@wkdgmr
Copy link
Contributor Author

wkdgmr commented Feb 12, 2025

I'm not sure why those other commits are showing. This change is just gamemenu.cpp

@StephenCWills
Copy link
Member

StephenCWills commented Feb 12, 2025

Merge will do that. If you make sure your branch is up-to-date before making commits and/or rebase instead of merge, that won't happen. But probably, your tools (Visual Studio?) are doing the merge for you automatically, perhaps without you even realizing.

@wkdgmr
Copy link
Contributor Author

wkdgmr commented Feb 12, 2025

I guess my question is: If this was approved would I need to redo this PR as this seems scuffed?

@qndel
Copy link
Member

qndel commented Feb 12, 2025

I guess my question is: If this was approved would I need to redo this PR as this seems scuffed?

no because we squash commits while merging anyway
your change failed clang format
I still don't know what this is about, maybe add a before/after pic?

@StephenCWills
Copy link
Member

@wkdgmr You don't have to be so quick to redo PRs. The one you closed earlier could have been reopened. And Git has the tools to add additional changes or even rewrite history on a branch if you need to. If you want help with these things, I can guide you. Feel free to ask on Discord.

@kphoenix137
Copy link
Collaborator

Related PR: #3902 (comment)

@wkdgmr
Copy link
Contributor Author

wkdgmr commented Feb 12, 2025

I guess my question is: If this was approved would I need to redo this PR as this seems scuffed?

no because we squash commits while merging anyway your change failed clang format I still don't know what this is about, maybe add a before/after pic?

I provided photos above. When the player is dead (in any Multiplayer game session), New Game and Quit Game is disabled and the player can only choose to Restart in Town. This behavior is in line with how Restart in Town is disabled when the player is alive.

The logic behind this is it is fairly common for players to accidentally select New Game or Quit Game after dying in the dungeon. This is a high risk situation when a players loot is dropped and they are forced to interact with the Game Menu in order to proceed. Leaving the game in this state if playing a Multiplayer session that does not have another player in it to keep the game open and rejoinable can result in the loss of gear causing unneeded frustration for the player.

This seems like a pretty straightforward QoL to prevent players from accidentally leaving multiplayer game sessions when forced to interact with the Game Menu upon Death

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.

4 participants