![[QA] Janosik](../../../data/avatars/users/10122.svg)
[QA] Janosik
- Janosik
- janosik
- Europe/Stockholm
- Yes
- No
I guess [QA] Janosik mistakenly did that.
[QA] Janosik closed this issue as "Works As Intended" with no explanation why it's intended. I strongly disagree with that because it's certainly behaving differently from the PC version, and since redstone mechanics is a really complicated system, having two different mechanics would not make things better.
[QA] Janosik closed this issue as "Won't Fix" but why? He/she gave us no explanation.
Someone please reopen the issue, or tell us why it's an intended difference. I just can't stand getting it simply ignored and then permanently forgotten. MCPE-11279 is another example which has been dismissed by [QA] Janosik for no apparent reason. There would be no point reporting bugs then.
Please reopen this. [QA] Janosik closed it as "Works As Intended" with no explanation why it's intended. Note that there are some other issues (like MCPE-11953) which has been dismissed that way, rendering the bug report pointless.
Can someone reopen this issue? [QA] Janosik resolved this issue as "Works As Intended" for no reason.
Can someone reopen this issue? [QA] Janosik resolved this issue as "Won't Fix" for no reason.
Can someone change the resolution to "Duplicate"? [QA] Janosik resolved this issue as "Fixed" for no reason.
Someone please reopen; this is one of many issues closed by [QA] Janosik for no reason. It's getting harder for me to refrain from saying that what he is doing is something like a vandalism. See this thread for details.
[Mojang] Shoghi Cervantes, and why [QA] Janosik resolved the issue as "Works As Intended" like MCPE-11953.
[Mojang] Shoghi Cervantes, I have a favor to ask of you. There are some more issues that have been unnaturally closed by [QA] Janosik and I listed all of them in this thread. I would highly appreciate it if you could check them as well. Thank you for your consideration.
Reopened because this one has been marked as "Fixed in Future Release" by [QA] Janosik on 2016-08-15 but still not fixed.