Skip to content

Add setting to disable damage flash #16009

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

FreshAlacrity
Copy link

Goal: Add a new boolean setting for the client under Accessibility in a new section called Damage

Partial progress towards resolving #15805. The 'Damage' section is intended to also hold a damage tilt setting (and potentially a damage flash color setting) from the same issue.

How to test

  • Build and launch Luanti
  • Open a new Development Test world with Enable Damage turned on
  • Find a damage source (I used lava)
  • Take damage; notice that the screen flashes red as usual
  • Open the Settings menu and under Accessibility scroll to the bottom of the options
  • Toggle off 'Damage flash' and hit enter or click Set
  • Return to the game and take damage; the screen still tilts but does not flash red

Adds a new boolean setting for the client under Accessibility in a new section called Damage
See luanti-org#15805 for more information
@FreshAlacrity
Copy link
Author

On a very personal note, I'm really excited to contribute to Luanti! I haven't made any contributions to big projects before, so I tried to pick something small and I would really appreciate any feedback about how I can do better in the future 😃

@Zughy Zughy added Feature ✨ PRs that add or enhance a feature Roadmap: supported by core dev PR not adhering to the roadmap, yet some core dev decided to take care of it labels Apr 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@ Client rendering Feature ✨ PRs that add or enhance a feature Roadmap: supported by core dev PR not adhering to the roadmap, yet some core dev decided to take care of it @ Startup / Config / Util
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants