GrassPelt
- GrassPelt
- grasspelt
- America/Chicago
- Yes
- No
MC-121825
Don't worry, nothing important was lost. ButI thought I would just point out that after converting to a new snapshot and clicking backup and load, the original world does corrupt (as in chunks completely reset to default terrain). After trying to load the backup, the backup is corrupted in the exact same way.
I thought I would just point out that after converting to a new snapshot and clicking backup and load, the original world does corrupt (as in chunks completely reset to default terrain). After trying to load the backup, the backup is corrupted in the exact same way.
EDIT: So I did a bit more investigating and it turns out that this seems to occurs if command blocks are running when you load the world. The world seems to load fine as long as they aren't running.
I thought I would just point out that after converting to a new snapshot and clicking backup and load, the original world does corrupt (as in chunks completely reset to default terrain). After trying to load the backup, the backup is corrupted in the exact same way.
EDIT: So I did a bit more investigating and it turns out that this seems to occur
sif command blocks are running when you load the world. The world seems to load fine as long as they aren't running.
Here are the conditions I'm getting this problem to occur.
- Any structures in the structure's file: No
- Name in structure block: Gate Dn
- Redstone current applied: Yes
You can take a look at the crash report. Exception: Cannot update neighbors.
World is practically unplayable now as the world will continue to crash every time it is opened.
Using Ctrl + Middle mouse wheel on a Chain, Repeating, or Impulse command block set to conditional mode will not save the mode. When you place the same command block down, the mode resets to unconditional.
Steps to reproduce:
1. Set a command block to conditional mode.
2. Pick-block the command block. There should be a command block in your inventory with a purplish +NBT text.
3. Place the pick-blocked command block down again. It should show by the texture on the block that is in unconditional mode.
4. Open the GUI of the command block and find that it is indeed in unconditional mode.
Title says what the bug is. Paste any text or command into a command block and the "Done" button becomes unavailable. It requires typing or erasing a character to re-enable it.
To reproduce:
1. Find a command. Copy it.
2. Open the command block GUI. Note that the "Done" button should be enabled.
3. Paste the copied text into the command line. The "Done" button should disable.To Re-enable:
Type or erase a character. The Done button will re-enable.I will also mention that when the command line is empty, and you type one character, the button is also disabled. typing a second re-enables it, but strangely erasing the second character and leaving only one leaves the button enabled.
It's a minor thing that kinda bothers me.
I would like to say that in 1.13.1 I am unable to summon any falling_block entity with a BlockState other than the "minecraft:sand" tag.
The only way I've been able to get a different type of falling block is to save the world and edit the tag in an NBT Editor.
Here are commands I've tried, I get "minecraft:sand" every time.
Command BlockState /summon minecraft:falling_block ~5 ~5 ~ {BlockState: {Name:"minecraft:stone"} ,Time:1}
minecraft:sand /summon minecraft:falling_block ~5 ~5 ~ {BlockState: {Name:"minecraft:grass_block"} ,Time:1}
minecraft:sand /summon minecraft:falling_block ~5 ~5 ~ {BlockState: {Name:"minecraft:glass"} ,Time:1}
minecraft:sand /summon minecraft:falling_block ~5 ~5 ~ {BlockState: {Name:"minecraft:gravel"} ,Time:1}
minecraft:sand
Unless I'm doing my commands wrong, I would say this bug should be reopened. By description, I also don't think it should be related to the duplicated issue.
Don't think this is a bug, but rather the intended effect. use a water breathing potion to see underwater clearly.
I can't seem to recreate this scenario consistently. It always corrupts when going backward in versions, but it seems to be random when going forward. Whatever happened seems to have been fixed in the latest snapshot (17w49b), as I haven't had this problem with the latest one. You can mark this one as closed if you want.
Do you still want the zip file?
This bug is occurring again in snapshots 17w46a and on.
This also seems to occur when you delete a map. I had two copies of the same map, One with an ID of 0, and another with an ID of 4. Upon attempt to delete the map with ID 0, the map is deleted followed by an immediate game crash. Attempts to reopen the world result in immediate crash.
Please note that this Map with ID of 0 was not in any item frames.
I added my crash report to the attachments section as well.
Can Confirm. Doors do not load, but they do save.
Getting a few of these upon entering the water with fish in them. As of 1.13pre-7.