Description:
When your creating in creative mode a box for example where no light can hit the inside, the daylight sensor will still trigger a redstone signal around (15000) when you say for example (/time set 15000).
When you say (/time set night) the daylight sensor is not triggering on that moment a redstone signal.
Also the light of the torch is not inflicting the daylight sensor on anyway.
I do not know or this suppose to be happening like this in fact.
(That for example when there is a torch, the daylight sensor need to make a redstone signal because of the light, like it normally would do in open air).
How to get the bug:
1 - make a box for example with a daylight sensor en redstone in it like on the picture.
2 - when the box is closed, it's not inflicting by the light of the torch.
3 - you see at 13000 ticks (/time set night) it's still doing normal and not triggering a redstone signal.
4 - you see at 15000 ticks (/time set 15000) it's triggering a redstone signal.
Extra info:
The torch does not inflict in anyway the redstone signal.
I other words, when the torch is taken away for example the daylight sensor will still trigger at 15000 ticks (/time set 15000).
The daylight sensor does this behavior not in open air.
And will just work normal if you repeat the same things.
(Like for example on the picture)
Only it will trigger 2 redstone dust at 13000 ticks. (/time set night).
And it will trigger 0 redstone dust at 15000 ticks. (/time set 15000).
Related issues
Attachments
Comments
migrated
Can reproduce. In a closed off room:
When time is set to 15000, daylight sensor triggers. When time is set to 0, daylight sensor turns off.
When daylight sensors were first added, I tested it in creative, and oddly they would not emit a signal at night, but they would in a completely enclosed space. For instance, if I dug a hole large enough for TNT and the daylight sensor, it would ignite upon covering the hole.
It seems this issue still persists (more edge-case than I thought). CAN CONFIRM in 13w48b with fully enclosed (all light levels reading 0) daylight sensor and /time set 1500. It increases in power with the moonrise...... makes it almost like a night sensor. Might be an intended feature, however, breaks the sensors' primary function, as an enclosed sensor will power at night when it should not, making it impossible to make exposed-room (during the day) traps/devices.
If it is intended, I can't help but feel there is a smarter way of making a "moonlight detector" than changing the behavior when there is no sky light. Such as stacking 2 daylight detectors creating a "24-hour clock" (well, powered day and night) that powered both during day and night, which then someone could use a regular daylight sensor to subtract from the double-tall signal to create a night-only sensor.
Would probably be best if the daylight sensor were basically turned into a slab. Then a double-tall daylight sensor slab would be the thing I talked about the previous paragraph. I'm sure builders would like it to be able to blend in with slabs and also be placed flush with floors, too.
The torch does not inflict in anyway the redstone signal.
Works as intended, the daylight sensor only reacts to... day light 🙂
An I think I've read in the Wiki that enclosed daylight sensors are meant to send an inverted redstone signal.
Koala_eiO, this bug isn't about the torch, they just added that in as info (I read this part wrong, the first time, too), it's about it acting as a night sensor.
The wiki is user-maintained, so it cannot be used to find out if something is intended or not. Even if this was intended, it ruins exposed-cavern detection (which, is more general-use) in favor of a particularly edge-case use.
neurospex
The title to this bug needs to be updated to be more descriptive.
"Daylight Sensor - Does not behave like it should be!" could be any misbehavior. Perhaps something like this would help:
"Daylight Sensor - Emits signal at night when not exposed to sky"
Personally, this "bug" is a great feature that I use in a lot of builds. I consider it a moonlight detector and find it to be very helpful. I hope this is left as is.
However, I would like to see arguments against this behavior. Perhaps there are ways to address those arguments while leaving this behavior intact.