mrflippy
- mrflippy
- mrflippy
- America/Denver
- Yes
- No
6 issues
Key
Summary
Status
Reporter
Assignee
Created
MCPE-46011Setting blockstates outside of expected range via scripting appears to cause memory corruption
Cannot Reproduce
MCPE-46595Add-On Documentation - "minecraft:interact" parameter "on_interact" has incorrect documentation
Incomplete
Added Affects Versions: 1.12.0.4 Beta
Added Attachments:
Changed Description:
Custom blocks do not work, and crash the game when they are referenced. I've seen crashes in the following scenarios:
- Custom block in addon. In console, type "/give @s "
- Game crashes when the space after "@s" is type
- Custom blocks are used in world generation using feature/feature rules
- Game crashes during new world generation
- When a custom block has "register_to_creative_menu" set to "true"
- Game crashes on world load
My custom block addons worked fine a couple of weeks ago, and I have not changed the code since then.
Attached is an addon containing a simple custom block to demonstrate scenario #1 from the above list. This block uses standard "stone" textures that work with vanilla blocks, so it seems unlikely that it's a texture issue.
Added Affects Versions: 1.13.0.18 Beta
Added Affects Versions: 1.14.0.2 Beta
Added Affects Versions: 1.14.0.1 Beta
Added Affects Versions: 1.14.0.1 Beta
Added Affects Versions: 1.14.0.2 Beta
I also tested in 1.12.0.4 and see the same behavior.
I attached file minecraft_addon_example_blocks_items_v1.1.0_only_packs.zip that contains block examples that worked in version 1.12.0.4. This example no longer works in v1.12.0.6.
In 1.13.0.16, the code example for "executeCommand" is still incorrect.
Edit: executeCommand still has an incorrect code example in 1.14.0.1 Beta.
I'm seeing this in 1.13.0.17 as well.
This also occurs in 1.13.0.18
This appears to be fixed in 1.13.0.18 beta
This still occurs in 1.14.0.1 Beta.