Brian Santos da Fonseca

Confirmed for 1.16.5 and now I want to jump off a (Minecraft?) cliff

Since it seems like Mojang did not plan to fix this bug since 1.12 nor plans to do it in the future, I'd like to document a workaround for this for future players reading this bugreport.
To bypass this bug, the player can perform a sequence of commands to clone a multi-line book and quill from a chest and instantly add it to a player's inventory, without triggering the bug.
The commands are:

/summon item ~ ~10 ~ {PickupDelay:0,Tags:["temp"],Item:{id:"minecraft:writable_book",Count:1b,tag:{pages:["a"]}}}
/data modify entity @e[type=item,tag=temp,limit=1] Item set from block 0 100 0 Items[0]
/tp @e[type=item,tag=temp] @p

The first command will summon a vessel to hold the currently problematic NBT we are trying to use (that Mojang considers problematic for no reason, since it is perfectly valid NBT).
The second command looks for a chest at the coordinates 0 100 0 (can be changed to any coord), grabs the NBT from the book and quill on the chest, and puts it on the item that was summoned using the first command
The third command teleports the summoned item to the nearest player, making it instantly be picked up, which is similar behavior to a /give command.

I hope this helps someone. I would say I also hope Mojang fixes this bug but I know they won't. Have a nice day yall!

"these things just had to be said" that's just your ego feeding into your obsession of defending someone who is wrong, nothing that you said makes sense and by this point you're just trying to diminish others including me and modders to compensate for your lack of arguments.
Can you please stop reviving this discussion now before I get banned because of your nonsense? Thanks

I told Dhranios I didn't want to discuss opinions here, but they didn't listen. Thanks Anthony

> and fix everything they break in the progress of every change
and (not) fix what they break in the progress of every change, clearly. You're forgetting they're not fixing things here
> Do not assume game development is easy for 1 moment
Yes, Mojang/Microsoft really must suffer with the lack of money and people to hire, good thing they can wipe their tears away with our cash
> Microsoft is not in control of Mojang
This part sounds ok, I can understand that. Although Mojang is also not in control of Mojang either, since if they were, there wouldn't be open bug reports from 2014-2017

If they can't handle their own game (which according to you they can't, as you make them sound very incompetent), they should stop updating it and go back and fix the mess that was left behind, or open source the game/add proper modding support and let people who ACTUALLY know how to fix the game do their thing.

I'd be able to believe what you said just ok if it wasn't like the 10th time Mojang pulled a Mojang and did the same thing over and over again. By this point I can't count how many hours I lost because of bugs that haven't been fixed for 5 years and won't be fixed on the next 5, including the time I'm losing typing this explaining it to a random person.
I don't think it's worth further discussing our opinions about this and I ultimately blame Microsoft for not managing stuff properly (or at all).

That wasn't sarcasm, just facts.
What's the point of keeping it up-to-date if nothing is being done about it? Sounds like just a waste of time as it is roughly about the same as ignoring it.

> We're tracking this issue
Well, if by tracking you mean doing nothing since 2017, alright. I did my part by reporting it.

Still having issues with this in 1.16.5. Did it really get fixed or Mojang just looked away and said they won't fix it?

This bug can also be seen in this video, in 2:25, when he trades emeralds for the chestplate that shows 1 emerald as cost but gets 5 emeralds deducted instead -> https://www.youtube.com/watch?v=poK7CzjWsGM

I'm hoping it gets fixed soon, it can be really misleading, completely broken display

Seems fixed (or at least partially fixed) in 1.13-pre6. I'll consider it fixed unless I get further issues in the future.

^{This attachment is a Minecraft Flat World where the bug can be easily reproduced. Simply try to cycle through the Structure Block menus and you should see it doesn't work. (Currently verifying if it has been fixed in 1.13-pre6, since it can't be reproduced like that anymore in that version)}

Still waiting for confirmation...

Already attached all info possible, will try to attach even more if requested. Bug seems to be present in all snapshots. Still awaiting for confirmation as of snapshot 18w19b. I believe this bug would definitely cause later issues if it came live to the 1.13 release.

Still in 18w08a

Still not fixed in 18w07b. Really hoping for a fix.

Also happens in 18w06a. Gets fixed upon chunk reload. Filling Ender Chests into Enchantment tables also caused the following crash:

No, not an expansion. I reproduced MC-82703, and it does only get triggered after a second fill command, unlike this one, which is unavoidable, affects structure blocks, causes FPS/other issues and doesn't get fixed after chunk reloads, as the other one seems to. Not even as similar as I though to this one, as this one is much worse.
Additionally, MC-82703 still happens in the latest snapshots, and can cause crashes, as I described into it's page. (requires updating)

It might be an expansion to MC-82703, or a similar issue. Not a duplicate, though.

Launcher log, attempt #2, here it goes.
Launch fail cause seems to be the following:
~[0210/013316:INFO:GameCallbacks.cpp(178)] launcher/launcher (main) info Process closed with exit code 1

[0210/013316:INFO:GameCallbacks.cpp(178)] launcher/launcher (main) info Exception in thread "main" joptsimple.OptionArgumentConversionException: Cannot parse argument '--height' of option width
at joptsimple.AbstractOptionSpec.convertWith(AbstractOptionSpec.java:92)
at joptsimple.ArgumentAcceptingOptionSpec.convert(ArgumentAcceptingOptionSpec.java:277)
at joptsimple.OptionSet.valuesOf(OptionSet.java:223)
at joptsimple.OptionSet.valueOf(OptionSet.java:172)
at net.minecraft.client.main.Main.main(SourceFile:95)
Caused by: joptsimple.internal.ReflectionException: java.lang.NumberFormatException: For input string: "--height"
at joptsimple.internal.Reflection.reflectionException(Reflection.java:136)
at joptsimple.internal.Reflection.invoke(Reflection.java:118)
at joptsimple.internal.MethodInvokingValueConverter.convert(MethodInvokingValueConverter.java:48)
at joptsimple.internal.Reflection.convertWith(Reflection.java:124)
at joptsimple.AbstractOptionSpec.convertWith(AbstractOptionSpec.java:90)
... 4 more
Caused by: java.lang.NumberFormatException: For input string: "--height"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:580)
at java.lang.Integer.valueOf(Integer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at joptsimple.internal.Reflection.invoke(Reflection.java:116)
... 7 more~