mojira.dev

GrygrFlzr

Assigned

No issues.

Reported

MC-1023 Potion of Weakness removes ability to destroy paintings and item frames Fixed MC-1004 Custom spawners with no delay variance crash the game Fixed

Comments

  1. Issues that are hidden are security issues, issues that are closed are already resolved in some manner, but continue to be argued on, thus closing the issue 'locks' the comments section. Users can also set their own issues to private (as you can probably tell), and unless it is a security issue we'll unhide those.

  2. We're only concerned with the latest version, although it helps the search filters when we list older ones.

  3. There's no dedicated function, as far as I know, but you can filter issues that you created or issues that you're watching.

  4. Your display name can be changed, your username cannot.

  5. Normally the oldest one, but if there are already several duplicates created before we've encountered them, then the one with the best description will be used as the main one.

  6. Invalid is for... invalid things such as feature requests or tech support. Works as Intended refers to behavior that players might deem as bugs but have been deemed features by Mojang. I don't see how they're interchangeable.

  7. Presumably one of the default JIRA resolutions.

  8. skip

  9. Hover your mouse over the screenshot, it gives the username and time they posted it.

  10. What grey line? If there's more than one, those appear so that they're easily read.

  11. No, in those cases the bug the player is talking about is a different bug. It completely defeats the point of the bug tracker if one report contains 50 different bugs, people wouldn't know which bugs are fixed. The report will be updated if it is a clarification to the bug (eg. exceptions, better ways to reproduce).

  12. They should, but human errors -> linked to different issue. When that 'root' issue is found to be a duplicate of an existing one, it gets linked, but JIRA doesn't have an efficient interface for transferring all the links to the other issue.

  13. By default it's sorted by last update time. Yes, JIRA has its own query system to do that.

  14. No, either Mojang employees themselves mark it as intended or we have evidence (eg. a tweet from Dinnerbone) that mentions that behavior is intended.Other times its really painfully obvious that it's intended.

  15. Unsure about this from the user side, mods definitely can.

  16. Unsure.

  17. The JIRA bug tracker.

  18. We really don't have a place for questions like this (and the JIRA bugtracker is only for issues with the software itself).

Sonic and violine1101, I believe Jesper is referring to the deobfuscated code being mostly useless to Mojang, not saying that this issue is not fixable.
Bob, modded servers such as Bukkit/Spigot do not require the client side to be modded, but is still not vanilla behavior of a server. The reason web links do not work is because the chat format has been modified to be only plain text by default; the client will only render links if explicitly specified.
Vanilla servers currently do not make arbitrary links clickable, but it is possible to send predefined, clickable links via the tellraw command. This issue is only a matter of verifying whether this behavior is intended.

Confirmed on 1.8.1-pre3.

John Chen, this is a bugtracker, not a mod hosting site. Feel free to host the mod else-where and link to it, but it does not belong as an attachment for this issue.

Confirmed on 1.8.1-pre3.

Confirmed on 1.8.1-pre3

Thanks, that was a mistake.

This site is only for bug reports. For technical support please use the Mojang Support Center.
Further attempts to seek support on the comments section of this issue will be removed.

Duplicate of MC-68718 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Duplicate of MC-68726 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Yes, LSHIFT is how you get out.

Duplicate of MC-1794 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Duplicate of MC-63020 and MC-63070 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Yes, the issue was originally about both side chunks and F5, and has been split.
The F5 issue is located at MC-63070.

Duplicate of MC-63020 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Duplicate of MC-63020 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Duplicate of MC-63070 – If you have not, please use the search function in the future, to see if your bug has already been submitted.

Marking as duplicate of MC-63020 due to issue split.

Marking as duplicate of MC-63020 due to issue split.