Zailer43
- Zailer43
- zailer43
- America/Montevideo
- Yes
- No
MC-167419
Normal
crash-2020-05-11_21.39.29-client.txt
How to reproduce it:
If you already checked in "Do not show this screen again" you need to go to /.minecraft/options.txt and change skipMultiplayerWarning to false- Go to the main Minecraft screen
- Click on multiplayer, the following image should appear
- Click the checkbox (to make it true)
- Resize minecraft window (f11 for example)
- The checkbox has been reset to false
How to reproduce it:
If you already checked in "Do not show this screen again" you need to go to /.minecraft/options.txt and change skipMultiplayerWarning to false- Go to the main Minecraft screen
- Click on multiplayer, the following image should appear
- Click the checkbox (to make it true)
- Resize minecraft window (f11 for example)
- The checkbox has been reset to false
In the BlockStateTag tag all the values that must be Boolean are strings, which does not make sense since it only has 2 possibilities, true or false
For example
/ give @p stone_slab {BlockStateTag:{waterlogged:"true"}}should be
/ give @p stone_slab {BlockStateTag:{waterlogged:true}}or
/ give @p stone_slab {BlockStateTag:{waterlogged:1b}}
Values that use the BlockStateTag tag and should be Boolean are:
open, occupied, powered, lit, has_bottle_0, has_bottle_1, has_bottle_2, drag, signal_fire, waterlogged, down, east, north, south, up, west, conditional, inverted, triggered, eye, in_wall, snowy, enabled, hanging, persistent, has_book, extended, short, locked, bottom, unstable, attached, disarmed
In the BlockStateTag tag all the values that must be Boolean are strings, which does not make sense since it only has 2 possibilities, true or false
For example
/give @p stone_slab{BlockStateTag:{waterlogged:"true"}}should be
/give @p stone_slab{BlockStateTag:{waterlogged:true}}or
/give @p stone_slab{BlockStateTag:{waterlogged:1b}}
Values that use the BlockStateTag tag and should be Boolean are:
open, occupied, powered, lit, has_bottle_0, has_bottle_1, has_bottle_2, drag, signal_fire, waterlogged, down, east, north, south, up, west, conditional, inverted, triggered, eye, in_wall, snowy, enabled, hanging, persistent, has_book, extended, short, locked, bottom, unstable, attached, disarmed
the game does not crash completely but the screen stops rendering and stays in the last frame so there is no crash log, besides I switched to linux and here I have not been able to reproduce the bug, sorry for responding late but I have not received notification.
- Reproduction steps:
Rename 2 items, to one of them put "deadmau5" and to the other whatever you want.- put an item frame
- place one of the renamed item in the item frame
- remove that item from the item frame
- place the other renamed item in the item frame
- result: you can see that the nametag height is different when the item is named "deadmau5".
Reproduction steps:
- Rename 2 items, to one of them put "deadmau5" and to the other whatever you want.
- put an item frame
- place one of the renamed item in the item frame
- remove that item from the item frame
- place the other renamed item in the item frame
- result: you can see that the nametag height is different when the item is named "deadmau5".
The height of the nametag of anitem frame with an itemnamed "deadmau5" is different from the height of any other nameThe height of the nametag of an entity named "deadmau5" is different from the height of any other name
Reproduction steps:
- Rename 2 items, to one of them put "deadmau5" and to the other whatever you want.
- put an item frame
- place one of the renamed item in the item frame
- remove that item from the item frame
- place the other renamed item in the item frame
- result: you can see that the nametag height is different when the item is named "deadmau5".
Reproduction steps:
- ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}
',CustomNameVisible:1b,NoAI:1b}}```
Reproduction steps:
- ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"
deadmau5"}',CustomNameVisible:1b,NoAI:1b}}```
Reproduction steps 2.0:
- use ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"}
',CustomNameVisible:1b,NoAI:1b}}```
- and ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}
',CustomNameVisible:1b,NoAI:1b}}```
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps
2.0:
- use ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"}
',CustomNameVisible:1b,NoAI:1b}}```
- and ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}
',CustomNameVisible:1b,NoAI:1b}}```
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"}
',CustomNameVisible:1b,NoAI:1b}}```
- and ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}
',CustomNameVisible:1b,NoAI:1b}}```
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"}
',CustomNameVisible:1b,NoAI:1b}}```
- and ```/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}
',CustomNameVisible:1b,NoAI:1b}}```
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"} ',CustomNameVisible:1b,NoAI:1b}}
- and
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"} ',CustomNameVisible:1b,NoAI:1b}}
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"} ',CustomNameVisible:1b,NoAI:1b}}
- and
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"} ',CustomNameVisible:1b,NoAI:1b}}
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"} ',CustomNameVisible:1b,NoAI:1b}}
- and
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"} ',CustomNameVisible:1b,NoAI:1b}}
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
Reproduction steps:
- use
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"test"} ',CustomNameVisible:1b,NoAI:1b}}
- and
/give @p minecraft:creeper_spawn_egg{EntityTag:{CustomName:' {"text":"deadmau5"}',CustomNameVisible:1b,NoAI:1b}}
- place both spawn eggs
- result: you can see that the nametag height is different when the entity is named "deadmau5".
I got the error in 1.15
crash report:
crash-2019-12-13_20.44.25-client.txt
It happens to me in survival and creative and that's when I don't look at blocks
crash-2020-01-24_12.40.23-client.txt
I did not realize that it does not leave more than 10 mb
Minecraft 1.15.2 - Singleplayer 2020-01-24 11-37-48 (online-video-cutter.com).mp4
I've already checked it and it's not a driver's problem as indicated in that problem, plus the one quoted from the driver is not compatible with my PC
Yes, but in the case of simply putting the integer it accepts it as if I put it as a string
In the following case it gives me an item that when I put it there are 3 candles but they are off
/give @s candle{BlockStateTag:{candles:3,lit:true}}I can't reproduce this with /summon either but with an item with EntityTag yes
Can confirm in 1.17
Confirmed for 1.17
Can confirm in 1.17.1
Can confirm in 1.17.1
ready, I already uploaded the launcher_log.txt, although with sublime text I replaced all the times that my username appears in the paths of the pc
If you look at the logs a few seconds before it said "crash" this had occurred
Can confirm in 1.19.3
> Can you show a profile the data that supports this assessment? Thanks.
I have made a small benchmark with 100 million iterations and 5 cycles of iterations, the result I got was:
code: