Xor Boole
- xor
- xor
- Europe/Stockholm
- Yes
- No
MC-85027The command
{id:1}
```
/summon Villager ~ ~ ~ {Offers:{Recipes:[{buy:,sell:{}}]}}
```
will crash any client that attempts to interact with the villager and place an item into the "buy" slot. This allows servers to crash clients by sending bad villager data.I assume this is due to either a mishandled null or a an issue with a draw call.
The command
/summon Villager ~ ~ ~ {Offers:{Recipes:[{buy:{id:1},sell:{}}]}}will crash any client that attempts to interact with the villager and place an item into the "buy" slot. This allows servers to crash clients by sending bad villager data.
I assume this is due to either a mishandled null or a an issue with a draw call.
The command
/summon Villager ~ ~ ~ {Offers:{Recipes:[{buy:{id:1},sell:{}}]}}will crash any client that attempts to interact with the villager and place an item into the "buy" slot. This allows servers to crash clients by sending bad villager data.
I assume this is due to either a mishandled null or a an issue with a draw call.
The relevant client crash report: https://gist.github.com/drXor/14433dbbf43705c46e36
Apparently this hasn't been mentioned in the thread, but the JVM flag `-Dorg.lwjgl.opengl.Display.enableHighDPI=true` WILL trigger correct behavior from LWJGL, including correct mouse movement, but the existing hack causes this: http://puu.sh/pk9Xo/1423a37f55.png.