Vexor64
- Vexor64
- vexor64
- Europe/Stockholm
- No
- No
The fact that it has always been this way is no excuse. So please, reopen this perfectly good report on a nonsensical and inconvenient bug within Minecraft.
The fact that it has always been this way is no excuse. Making things work differently is what fixing bugs is all about.
So please, reopen this perfectly good report on a nonsensical and inconvenient bug within Minecraft.
The fact that it has always been this way is no excuse. Making things work differently is what fixing bugs is all about.
So please, reopen this perfectly good report on a nonsensical and inconvenient bug within Minecraft.
The fact that it has always been this way is no excuse. Making things work differently is the very essence of bugfixing. As for this report not outlining how this could be problematic, that's because it is already indirectly implied.
So please reopen this perfectly good report on an utterly nonsensical and outright inconvenient bug within Minecraft. (Don't forget to update the affected versions if you do so.)
I think it's okay to remove 16w38a from the list of affected versions, since it's merely a development version.
I think it's okay to remove 16w38a from the list of affected versions, since it's merely a development version which has already been replaced by something newer.
Could somebody please remove 16w38a from the affected versions list? It's no longer needed.
This should be resolved as a duplicate of
MCPE-11236.
This should be resolved as duplicate of
MCPE-11236.
This should be resolved as a duplicate of
MCPE-11236.
Have you got any good excuses as to why this is a feature suggestion??
Why is this invalid? What qualifies it as being so?
If you can't find any answers then you might as well reopen it.
Why is this invalid? What qualifies it as being so?
If you can't find any answers then you might as well reopen it.
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
I can safely bet that you lazy moderators didn't even read the comment's message. Let me clarify:
Please reopen this at once. There is absolutely no reason to resolve this as invalid.
WHAT ARE YOU WAITING FOR? JUST DO IT!!
You're absolutely right. So please, reopen this. It does not in any way look like it was intended.
You're absolutely right. So please, reopen this. It does not in any way look like it was intended.
You're absolutely right. So please, reopen this. It does not in any way look like it was intended.
You're absolutely right. So please, reopen this. It does not in any way look like it was intended!
You're absolutely right. So please, reopen this. It does not in any way look like it was intended!
You're absolutely right. So please, reopen this. It does not in any way look like it was intended!
Happen. Happen Happen.
Happen. Happen Happen...
Vexor64, postponed means "it will be fixed in the future, not now". Do you have any info about it being fixed soon?
Vexor64, please stop commenting and then removing your comment in a few minutes. You can just edit your message if you need so.
And no, we can't remove 16w38a, because it is archived. We can only change current version(s) (which is 1.11.2 right now)
Even if we could, we wouldn't do that, because 16w38a was affected by this bug, and all versions are equally important to be saved as affected, whether they are major, minor, or snapshots.
Vexor64 you can stop now repeatedly updating your "Please reopen this at once. There is absolutely no reason to resolve this as invalid." comment to have it stay on top of the activity list.
It doesn't do anything good except that you're email-spamming people that are watching this ticket and may get you banned for abusive behavior.
Vexor64 This report will not be reopened, end of story.
Vexor64, this report is a request to re-open the original report (MC-96212) about horses no longer being able to get into boats. This report is not a valid report in itself. As previously mentioned in older comments, the original report had been marked for review. For any discussions relating to the bug tracker, please do so on the Mojira subreddit.
Vexor64 In addition, I'd like to point out that feature requests belong in the /r/minecraftsuggestions subreddit or at https://feedback.minecraft.net ... if you think something should be changed in the game, please post there with any suggestions you have.

Incorrect resolution. Please reopen immediately.
I totally disagree. This looks like a fully fledged report on a bug which does not make sense at all to exist in the game of Minecraft.
This report, as well as
MC-64879, should both be resolved as duplicates ofMC-82235.The fact that it has always been this way is no excuse. Making things work differently is the very essence of bugfixing. As for this report not outlining how this could be problematic, that's because it's already indirectly implied.
So please reopen this perfectly good report on an utterly nonsensical and outright inconvenient bug within Minecraft. (Don't forget to update the affected versions if you do so.)
Could you please just update the status to "reopened"? Don't postpone any longer.
I give up in trying to persuade you. How do I become a moderator?
Could somebody please remove 16w38a from the list of affected versions? It's no longer needed.
Thanks for the helpful advice.
The only version that matters is the latest version, not some small random development version that has already been superseded by the full version it was released for (in this case, 1.11). Don't you agree?
Since you're so unwilling, could you please tell me how to become a moderator so I can remove it myself?
This is a duplicate of
MC-98160. Can somebody please resolve it that way?Please reopen this at once. There is absolutely no reason to resolve this as invalid.
You heard what the submitter said. Please reopen this, or at least re-review it.
Please reopen this immediately. There is absolutely no reason to resolve this as invalid.
WHY?