Logical_Cyclops

This bug still occurs in 1.14, and 1.15, and 1.15.1. Mojang PLEASE fix this bug, it makes no sense for something like this to be postponed for so many versions. This hinders our ability to map make; we shouldn't have to be making workarounds to bugs that are supposed to get fixed within a reasonable time frame. Five years of not fixing this is unacceptable in my opinion. I'd like to see this get fixed in 1.16.

Affects 1.15 and 1.15.1 pre-release 1.

Have been doing some experimentation with potions and stuff in 1.15.

Putting Potion:"minecraft:water" seems to make it display the duration more accurately, and I say more accurately b/c potions are one second off for the duration that they say they'd last for (This applies with vanilla potions as well, but this is an entirely different issue).

So doing:

_/give @p minecraft:tipped_arrow{Potion:"minecraft:water",CustomPotionEffects:[

{Id:15,Amplifier:0,Duration:60}

]}_

Makes it accurately display the duration to be 3 seconds. B/c Duration is specified in ticks.

Every 20 ticks = 1 second. So if you want to convert 3 seconds into ticks you'd do 20 * 3 for e.g;

Same concept with splashed potions:

_/give @s minecraft:splash_potion{display:{Name:'

{"text":"Potion of Resistance","color":"gold","bold":"true","italic":"false"}

'},Potion:"minecraft:water",CustomPotionEffects:[\\{Id:11,Duration:200},
{Id:12,Duration:200}]_

But with lingering potions it's 8 seconds off...

_/give @s minecraft:lingering_potion{display:{Name:'

{"text":"Potion of Resistance","color":"gold","bold":"true","italic":"false"}

'},Potion:"minecraft:water",CustomPotionEffects:[\\{Id:11,Duration:200},
{Id:12,Duration:200}]_

It shows 2 seconds rather than 10, because *20 * 10 = 200*. Where 200 ticks = 10 seconds. For those that disagree with this, the Duration is specified in ticks- if ** you look at how long the duration lasts when you apply the potion effect, you will see that it does give you the potion effect for 10 seconds (disregarding it being 1 second off technically due to some other bug). This is not specified in seconds at all. It's some sort of incorrect number conversion in minecraft's code when it comes to displaying the duration. Although, come to think of it, we can just use the Lore:[] datatag to workaround this until this gets fixed. Mojang would probably have little reason to fix this when we can use the aforementioned datatag to make it correctly show the duration anyway, for if Mojang's intent is to not bother with fixing this, I'd like for them to mark this as 'Works as intended' so that I can cease giving updates on an issue that seems to have a pretty reasonable workaround that pretty much defeats the purpose of fixing this.

Though I'm thinking an easy way for them to fix is this is that instead of making the duration specified in ticks, they should make it specified in seconds. B/c a potion's duration cannot seem to be made to work in ticks. Making it nonsensical for it to even allow duration specification in ticks in the first place. So they could remove "Duration" as a usable datatag for custom potions and instead rename it to EffectDuration or something similar that distinguishes it from Duration- as it is used in a lot of other things and entities where it'd sensically have a use for it to be acceptably specified in ticks, but with the case of something like potions where you functionally cannot specify duration in ticks, it should be replaced with a different datatag name that treats that value you put in it into seconds. From there it should become easier for Mojang to fix this issue, should they bother with fixing it, but again they ought to mark it as either 'works as intended' or 'Won't fix' or whatever else to indicate that this behavior is intentional and can be worked around by specifying the duration with the Lore:[] datatag. Anyway I digress, I'm kinda glad that things are easier to customize now in minecraft anyhow 😃

Affects 1.15.1 pre-release.

I'm guessing this'll probably get fixed in a bug fix update of 1.15; ever since 1.13+ fireballs have been a pain in the ass to work with. The good ol' /execute summon to create a fireball mechanic doesn't work anymore, and now not even summoned fireballs can be hit ;(.

Nevermind you can close this issue

My report isn't a report about something game breaking. The bot is incorrect on this one. Mods please correct this or do whatever that needs to be done in regards to my report that isn't what the bod did.

Dinnerbone, can the prefix/suffix thing be a supported feature in /team option, rather then to do the old hacky solution of doing it through NBT editing? I liked how one could add prefixes/suffixes into teams before that became patched in 18w01a. Please give a response on this, I would greatly appreciate it if you do 🙂

Would a mod please confirm it? D:

Confirmed for Minecraft 1.12.2, and for 1.13 snapshot 17W43B.

Funny how every single colored glass, except white glass... alters the color of the beacon's beam color. The white glass should be making the beam color pure white. Although I was struck with the mandela effecting believing that I remembered that white glass would make a beacon alter its color to white at first. As from doing some testing, it seems that it functioned in the aspect of where white glass would not alter a beacon's beaming color like that ever since in the update of which beacons were added. If you look closely at the beacon's beaming light, it's edges are colored with a slight shade of blue, yet white glass does not alter this!? how can this be intended? I would like a Mojangsta to see this and outright claim if this is intended or not, or if they simply won't do any changes.

And how come the effected versions of this bug report hasn't been updated to minecraft 1.12?

Would a moderator please update the affected versions of this bug report to minecraft 1.12?

I suggest for you to address this issue on https://help.mojang.com/, as this is not the place to ask for help for technical issues dealing with being able to run minecraft smoothly.

This is still an issue in 1.12 because when I try muting the entity.lighting.impact sound, it doesn't get muted all the way. It would get muted at the very end of the sound being played. I can submit evidence to support confirmation of this bug, if needed.

I've figured out how to do it now 😃

This happen to me before. It's not a bug; the cause of this is an outdated graphics driver, update your graphics driver and see if it resolves the problem. If it still doesn't work, go to options... then video settings... and then make sure Use VSync is turned on. If that STILL does not work, then you need to contact mojang support for assistance with that issue that's related to how your computer graphics driver works.

Unable to reproduce the bug, I've tried it multiple times with different potion effects and it seems to clear it out perfectly fine. Are you playing 1.9 in a world that has been previously loaded in 1.8? or has it been corrupted before?

That isn't a bug, there are a few possible reasons as to why that's happening: it's a hardware related issue, Possibly your trying to play on a corrupted a corrupted world, Playing a 1.8 world in 1.9; but to find out for sure what's happening, copy and past the crash report log into the description, the mods will then help you out from there.

No, it's this one:MC-101033