Mulelish
- mulelish
- mulelish
- America/Havana
- Yes
- No
8 issues
Key
Summary
Status
Reporter
Assignee
Created
MCPE-19729
Added Attachments:
Changed Summary:
"minecraft:inventory_container" component does not return hotbar slots
Changed Description:
Running the following code on the client use to work as expected on all 1.12 betas (my_custom_ui would load just fine). On 1.13.0.1 beta the code runs but the ui DOES NOT load and from the player's perspective nothing happens (note the client script runs without errors on 1.13.0.1 as I attached the VS debugger and set breakpoints).
let loadEventData = this.createEventData("minecraft:load_ui"); loadEventData.data.path = "my_custom_ui.html"; loadEventData.data.options.is_showing_menu = true; loadEventData.data.options.absorbs_input = true; loadEventData.data.options.render_game_behind = true; loadEventData.data.options.always_accepts_input = true; this.broadcastEvent("minecraft:load_ui", loadEventData);Also there is a discrepancy in the documentation regarding custom ui's. In the Scripting documentation (under Breaking Changes) it says to use "engine.on("facet:updated:core.scripting", ...);" while the documentation for custom ui's says to use "engine.on("facet:updated:scripting", ...);"
Added Affects Versions: 1.15.0.53 Beta
Changed Description:
- Place a Soul Sand block (or Magma Block) 1 block in front and below a Dispenser that has a Water Bucket inside.
- Activate the Dispenser. A Bubble Column is formed as expected.
- Activate the Dispenser again, the water is removed but the Bubble Column stays! While this glitch is cool, it is not expected behavior and should be fixed.
I've attached a screen grab demonstrating this bug:
- Place a Soul Sand block (or Magma Block) 1 block in front and below a Dispenser that has a Water Bucket inside.
- Activate the Dispenser. A Bubble Column is formed as expected.
- Activate the Dispenser again, the water is removed but the Bubble Column stays! While this glitch is cool, it is not expected behavior and should be fixed.
I've attached a screen grab demonstrating this bug
Affects 1.0.2
Affects 1.0.2, their pathfinding is definitely bugged/glitchy. There can be aggro'ed by an endermite and be 2 or 3 blocks away and just stand there and not move/attack
Also confirming this is still in 1.0.3 and I hope this bug receives attention soon as this makes playing Win10 incredibly frustrating when it comes to crafting and inventory management. To top it off, triple clicking multiple stacks into a chest/inventory does not work, making this bug occur even more.
^ From the #scripting-api-feedback channel in the official minecraft discord server
I guess if this is working as intended then all that needs to change is for the documentation to be updated (as of this comment it is incorrect) but I hope another component is added like "minecraft:full_inventory_container" as it would be quite helpful to get all 36 slots in one call.
"Bug
This feature does not work as designed for the platform it was designed on...."
^ Taken from the Parity Request Guide you linked. Observers are designed to detect blockstate changes (such as a bed changing from empty to being used), there is currently a bug in the game that prevents observers from doing this. This issue is basically the same as https://bugs.mojang.com/browse/MCPE-43841, https://bugs.mojang.com/browse/MCPE-36783, and https://bugs.mojang.com/browse/MCPE-41074 and yet all of those issues are allowed to remain open. How is this one any different? @[Mojang] Mega_Spud (Jay Wells)
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
Here is some more information on this for the devs and anyone looking to use the particle command:
The documentation for particle names (found here: https://minecraft.gamepedia.com/Particles) is completely out of date. Since the particle command does not support autocomplete (tracked here: https://bugs.mojang.com/browse/MCPE-39829) the easiest way to find all the particle names is to look in the identifier field in the .json files of the default resourcepack in the particles folder.
Below is a list of particles I attempted to create using both command blocks and regular chat commands (the outcome was the same regardless). I did this on the latest beta (1.12.0.6) in a fresh creative world with zero add-ons:
Command format used: /particle prefix:particle_name ~ ~2 ~
minecraft:mobflame_emitter (works?, no errors, see also: https://bugs.mojang.com/browse/MCPE-39641, https://bugs.mojang.com/browse/MCPE-38675)
minecraft:falling_dust_gravel_particle (works, no errors)
minecraft:critical_hit_emitter (works, no errors)
minecraft:heart_particle (DOES NOT work, no errors)
minecraft:cauldron_splash_particle (DOES NOT work, no errors)
minecraft:arrow_spell_emitter (works BUT w/ errors):
[Molang][error]-Error: accessing a variable that doesn't exist: variable.color.r
[Molang][error]-Error: accessing a variable that doesn't exist: variable.color.g
[Molang][error]-Error: accessing a variable that doesn't exist: variable.color.b
[Molang][error]-Error: accessing a variable that doesn't exist: variable.color.a
minecraft:balloon_gas_particle (works BUT w/ errors):
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.x
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.y
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.z
Duplicate of https://bugs.mojang.com/browse/MCPE-41468
+1 for windows 10 on latest beta (1.12.0.6)
Whoops I didn't see https://bugs.mojang.com/browse/MCPE-40079 when I searched for it. Although I was never able to get it to work on the client in the latest beta as described in that card. Can be marked as duplicate
To add on to this bug, falling_block entities in general have gotten noticeably worse since the nether update. Either the rate at which they update has been reduced or the performance around their calculations has gone down significantly . Watching a falling_block move through the air there is an obvious stutter that did not occur before the nether update.
This issue seems so wide spread and it's an insta crash on startup. So either the devs somehow can't reproduce (which is unlikely) or vr support isn't a priority to mojang. I find it weird that they overhauled vr support with openxr but shipped it in a obviously broken state. It's like they want people to use Vivecraft (or do some random registry edits) over their implementation...
Due to the obvious lack of communication from Mojang on this card I recommend everyone share this issue with others and ask them to vote for it and to tweet this issue out to any twitter handles you see fit. It seems being loud is the only way to get a response on this as we are all clearly talking to a wall in these comments.
A user on reddit was somehow able to get the Minecraft to load into vr (via openxr) using Index. They were able to load a world just fine but were unable to get the index controllers to work (only keyboard and mouse)
https://www.reddit.com/r/ValveIndex/comments/maynh3/minecraft_vr_index_controls/
Can confirm that beta 1.16.230.50 is able to load minecraft in vr on index (steam vr beta 1.17.2, latest version of windows). Pretty sure Inventor156 is right in that there is some sort of memory leak as the game hangs consistently after being open for 2-3 minutes (regardless if you load a world or just sit on the main menu screen). Also I can confirm that index controllers do not work at all (defaults to keyboard and mouse). Opening the steam vr controller menu does nothing. Opening the legacy steam vr binding ui lets me mess around with stuff but minecraft hangs before I am able to get anything done.
I just want to say that I thought I would never see the day where this shit didn't instant crash to desktop. But now I can load the game and have it hang after 2 mins. At the current pace we should be able to play this game in vr sometime in the next 2-3 years!! How exciting! /s
Also I DO NOT recommend joining the beta and trying vr in the current state. The hang that is currently happening is really bad as it causes steam vr to get stuck and I thought I was going to have to force shutdown my computer it froze for so long.
I have the same issue, I can open/run the game using the openXR shortcut but regardless if I'm sitting at the menu screen or load into a world my game crashes after about 5 mins and my memory usage slowly climbs up the whole time. My specs:
VR Headset: Valve Index
CPU: i7-8700k
GPU: Nvidia 1080Ti
Memory: 32GB
Storage: 500GB SSD
Crashes on the latest beta of both Minecraft and SteamVR
ATTENTION ALL VALVE INDEX USERS
After waiting for 5+ years minecraft bedrock edition is actually "playable" in vr. It's in quotes because we can't use the index controllers (please vote on this issue:
MCPE-128724) but I was able to launch the game and load a world and actually move around/play for a period of time. In order to get this to work I had steamvr running, my xbox controller connected to my pc (corded and wireless both work), and then clicked the openxr shortcut. Some things to note:I don't think any of my crashes were related to memory as I had an eye on it from time to time but it's hard to say. Needless to say it was a buggy/crashy experience but I was able to make an iron pickaxe and kill a zombie. Who knows, maybe in 5 years it might actually be good.
VR Headset: Valve Index
CPU: i7-8700k
GPU: Nvidia 1080Ti
Memory: 32GB
Storage: 500GB SSD
latest beta version of both steamvr and minecraft