Fix #128

[Kilip1000]

Fixes #128.
This is done by taking the maximum of the light level applied in the method, and the original light level with no changes applied.

[CLAassistant]

All committers have signed the CLA.

[ryanhcode]

we would then be doing double the light queries

[Kilip1000]

we would then be doing double the light queries

Do you mean to say that preserving the original light-level is not worth it, unless the execution of those light queries is at no additional cost? I, frankly, believe that's infeasible/impossible to do.

[ryanhcode]

No, there is a way to both preserve the original light level here and also to incorporate the sub-level light levels

[Kilip1000]

No, there is a way to both preserve the original light level here and also to incorporate the sub-level light levels

How's that possible if the original value does not get evaluated/incorporated?

[ryanhcode]

also, calling Math.max on an already packed light value pair isn't a valid operation. I'm working on a fix that shouldn't add any more additional queries and should fix this

[Kilip1000]

Ah, right, I forgot one of the light values is a higher power of two than the other and would thus unintentionally take priority!
I'm sorry for wasting your time 😓

[ryanhcode]

you're all good! thank you for bringing the issue to light