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

Should there be a skylight number in the Nether? #79

Open
mk-pmb opened this issue Sep 23, 2024 · 4 comments
Open

Should there be a skylight number in the Nether? #79

mk-pmb opened this issue Sep 23, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@mk-pmb
Copy link

mk-pmb commented Sep 23, 2024

Since the Nether has no sun, should there really be two numbers?
I think it would be nicer (less clutter) to omit the skylight number in sun-less dimensions (probably also includes the End) if it would be zero. Non-zero values should still show, to help detect buggy chunks.

@andi-makes
Copy link
Contributor

Thank you for opening this issue!

I think adding an option to hide the skylight number when the skylight level is zero and enabling it by default is the best way of implementing your suggestion. I'll look into implementing it!

@andi-makes andi-makes added the enhancement New feature or request label Sep 28, 2024
@mk-pmb
Copy link
Author

mk-pmb commented Sep 29, 2024

My gut feeling is that I'd want dimension exceptions though, so that I can still have it always show it in the overworld. I don't understand the reason though. Maybe it's just the power of being used to it.
There could be a mental load argument in case a user wants to verify zero (only in dimensions where there's reasonable doubt), which with a global option would require additional conclusion to interpret the absence of a stimulus. However, without a proper UX study, that's just FUD.

@andi-makes
Copy link
Contributor

Thank you for your additional input!

With how Lighty is structured right now, dimension specific configs aren't possible, but something that would enable that is planned. So while your idea might not be quite possible right now, it will be in the future when I got around to implementing the dimension specific configs.

You probably have a point with the sky light number missing in the overworld being confusing for others, that would probably result in many bug-reports now that I think of it a little bit more. I wouldn't worry about the "absence of a stimulus" or an UX study though, based on my experience people don't really care how the overlay looks like, as long as it works.

That said, it will take a bit until the base functionality for dimension-specific configs is implemented, so no guarantees on when I get around to implementing this feature.

@mk-pmb
Copy link
Author

mk-pmb commented Oct 2, 2024

people don't really care how the overlay looks like, as long as it works.

A lot of my Minecraft "gameplay" is actually research into how it works exactly, including in fringe conditions. I'm used to lots of mods working "good enough", i.e. they decrease the workload for what I want to discover to a level that the experiement is actually feasible with my energy available. Nonetheless, I always appreciate when developers are nice enough to put in a little more effort to lower the bar even further, because then I can achieve more in a day, or achieve the usual progress in even a lower mood.
There have been times where implementing an experiment has been so cumbersome that I gave up and rather did something comparatively "easy" like debugging weird linux drivers. :D (Especially WorldEdit. I understand why they fight hard to keep their project scope as minimal as possible. The correct solution would be to hire someone who makes me a custom WE mod, but I never got around to that.)

btw, if you can accept payments via SEPA onto an account for which it's safe to publish the IBAN, do so and some €€€ may randomly appear there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants