mojira.dev

Joshua

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MC-301515 you continueusly right click or place blocks and open chests etc.. on mac Duplicate MC-300282 Items to small in shelf Duplicate MC-300278 When 2 or more copper golems are together the animation and ai breaks and the item follows a ghost animation Duplicate REALMS-13098 New lag Duplicate MCPE-222783 Water Invalid MCPE-221870 Bundle duplication glitch Unconfirmed MCPE-219382 When having more than two Hardcore worlds, it doesn't show that they're Hardcore until clicking on them individually Unconfirmed MC-296767 Lead breaks when player rides boat (or any controllable mount) attached to happy ghast Works As Intended MC-296402 potions look like water potions and arrows are just water tipped arrows Duplicate MC-296153 Cape missing Invalid MC-270420 Wither Skeletons become stuck under certain blocks Duplicate MCPE-152120 Redstone Repeaters and Observers programming errors Duplicate MC-244696 Nether Lag-Crash When Entering Awaiting Response MC-241468 Hacker was able to get into my game(orsondmc) Invalid MC-240031 I can't go on any server Duplicate MCPE-146128 Generating nether fortresses in passive causes spawning issues Incomplete MCPE-138253 delayed moves Duplicate MCPE-137501 Doors somtimes drop when you mine them in creative Duplicate MC-232815 Holding down E will cause the inventory to flicker, and ESC will always end up and stay in the pause menu Duplicate MCPE-133452 water glitch Duplicate

Comments

yea that bugs me becuase the copper golem would sort chests 1 block above them on bedrock

Please disregard previous comment. I changed Visuals back to “Fancy” and it's back to normal. Thank you for your time, and again thank you for all your awesome work.

I have an issue that I know is without question related to this problem that is not included in the list of issues. Its likely related to the central problem causing the delayed sound and the delayed chunk loading. I do believe that the Minecraft Marketplace is causing the problem as I have experienced all these issues on my Gaming Computer as well as Nintendo Switch ( computer specs are RTX 2060 GPU 9th gen i7 CPU approx 32GB ram). This error is extremely repeatable though on the Nintendo Switch and unclear on repeatability on computer. I extremely believe that the Minecraft Marketplace is the culprit [very little doubt]. error message, "slow-running script detected" followed by behavior pack and seconds average in "()". It's important to realize though that the behavior pack isn't actually the culprit and I've had this message happen anytime under any circumstance even on the menu screen before when scrolling through the marketplace on both Computer and Nintendo Switch.

I can repeat this 100% of the time by the following steps (note that you can get this message under any condition though and can be as simple as opening Minecraft)

1. Download path of the Jedi world from the Market place
2. create the world template
3. Launch the world
4. play on world for few moments and error will appear (this will not occur on computer because of the excess memory and reading speed through the drive if an SSD which the Switch does not have)

added screenshot for proof

[media]

Possible fix, test prototype DEV version under no marketplace and see if issues are repeatable (chunk loading and sound delay issues remove marketplace from pause menu and main menu). if not it might be advisable to change how the marketplace works completely and importantly optimize the system. tying the system into url's might be advisable.

[This appears to be ongoing in version 1.19.7 where the first level of the repeater still opens the piston at the same time as when no repeater is present... Not supposed to happen! (also I'm an idiot and forgot this is duplicate and also reported in 15793] I happened to just be going through the reporting's, and it looks like there is issues currently with comparators on MCPE-15793. It would be a good Idea to up the level of importance in fixing that and this error in Redstone programming at least in my opinion. The fact it is not working so far from when this was the Pocket Edition is absolutely extremely controversial. Viewing the issues in timing presently, it appears to cause pistons in some Redstone machines to create a variable if not random output doing something different every time. I often find myself if playing the Bedrock edition placing the repeater levels at level 3 to slow the flow down enough that the output of a Minecraft designed circuit (in bedrock, works fine in Java) is not randomized by the timing the other end of red stone reaches its desirable destination. If you can understand me, the issue is a race with time, where the timing outputs of the repeaters in Bedrock are so fast that they can reach their destinations in a way that the output could result in a random number instead of the desired outcome (key: the numbers are in Booleans). In other words, Since PE the Red Stone has been so buggy that you can use it as a random number generator. I went through some of the comments here, and it appears there are some bad practices in reports of dated issues like this one. The fact is that the desired outcome of the Redstone current is not what is happening in fact. Hence you have a bug, sad to say, that has existed for many years and is yet to be resolved.

This is unable to be fixed, this is caused by loading a world from a beta/preview into the full game release. 

The RAM allocation was increased as high as it is to try to get the issues to go away. Reducing the RAM down the 4gb causes general lag around the server due to low resources.

@[Mod] KillerbeeNL Thank you, I get what your saying with PID however it does not exhibit any challenge and is more of a correctional device than the heart of the machine. Thanks for recognizing the duplicate, I think the result of looking at that ticket though shows even more problems which means I do not really think the second problem needs any reporting since the methodology of how redstone was programed was likely wrong to begin with in this edition of the game. Likely a complete redo is needed in order to fix the fact that redstone dust ticks are not connected as shown in the other report which is a huge issue as the redstone dust determines timing for all contraptions.

You clearly did not read. Sorry to say such a thing but its true.

1. Open Minecraft (Bedrock game client)

2. Open Minecraft Java

3. place two pistons and a repeater to divide their red stone connections ( the steps are very simple and were shown in the video and highlighted in the description)) [do this in Java and bedrock game clients]

4. place lever and flip switch for level one repeater (both clients)
Observed result: zero time difference for the connection to the second piston in Bedrock game client while there is a time difference in the Java edition.
Expected result: Both time gaps would be identical in operation. (please note the only problem in the bedrock edition is that the time difference between the connections is incorrect)

5. Change repeater level to 2 for both editions
Observed result: Bedrock edition appears to be faster in comparison to the java edition which is running on level two
Expected result: Repeater in Bedrock edition would run on level 2
6. Change repeater level to 3 for both editions
Observed result: Bedrock edition appears to be running slower by small amount of time gap while java is running repeater level 3.
Expected result: Bedrock edition should should run on repeater level 3.

Observer Block
This issue does not have any one way to reaching the issue. As this problem is an issue in the probes which causes flying machines to work in the Java edition utilizing observer blocks but not to work in the Bedrock edition. My video of course also show this which was clearly ignored as all the facts including what I am saying in this comment have already been stated. PLEASE READ. THIS IS NOW TWICE I HAVE REPORTED THIS.

All issues are repeatable 100% of the time
Red stone is not working as intended as you can check out any other previous edition and see that red stone did work properly. It is not the result of changing the language Minecraft is programed in as many have claimed, but instead a result of rushing red stone when this was Minecraft pocket edition. I am a mechanical Engineering student so do not expect me to constantly reply. This reopening is mainly to help others who do not know any better as most of the audience for Minecraft have no idea this is fixable.

I've changed the view distance around a few times, it is currently at 10 but could have been at 9 during those logs. Simulation distance is set to 6.

Here are two of the files you requested. One from the server side and other other from my user. The server did not fully in these profiles but did shortly before I got them. Using version 1.18.1 now and still get bad lag from the nether, not from the overworld or the end.

[media][media]

 

This issue is NOT resolved. I have been unable to use players skins for anyone other than player 1 in local multiplayer (either offline or online!) in literal YEARS. When is this going to get resolved???

Just tested and can confirm they do get knockback atleast in singleplayer.

Wow it's still there?  

Sorry, it was actually my earbuds that were the problem. The were too cheap I guess.

Minecraft Addons: Customize Your Experience Then why did this state: Now available on mobile, "console" and Windows 10: Add-Ons are the first step on our journey towards bringing even greater levels of customisation to "all" editions of Minecraft? I'm just using MCPEDL.com as an example for this. I tried several other sites as well.

 Why was it edited to say squids?  Its specifically only the glow squid mob.

Another painful use case: renaming maps with an anvil - A1..E5 to keep them organized - and it turns out "C5" and "D1" are censored. Oof. RIP my anvil and my xp.

"A bug is something in the game not behaving the way it should, due to a problem in the game's code. As such, it should be reproducible and not be caused by circumstances outside of the game."

 

As I have already said, this has happened on EVERY single computer I've played Minecraft on. It is reproduceable, and is a result of something in the Minecraft code, as I have only ever had this issue with Minecraft. How is my issue invalid and not a bug?