Marco Bergsma

I recorded a video of it happening. I start out at the local world, show that the resource pack is loaded and then proceed to put a snowball item on the ground and /execute a command on it.

I will then proceed on the realm and repeat these steps and show it's not named "Wand" but "Snowball" thus ignoring the custom naming. 

Unfortunately an issue when dealing with executing commands on dropped (named) items. 

https://youtu.be/yowHqit_0yQ

(I posted in a private YT video as it was too large to fit directly)

I have added the pack. You can reproduce by enabling it on an offline world, then take a snowball (which is renamed as "Wand") and observe you can both throw it and drop it on the ground while executing a command on the entity by using [name=Wand].

When you enable the same pack on a realm, it will not work as the renamed item will still be called a "Snowball"....this appears to work with all named/renamed entities/items. They DO show up in the inventory with the names used in the .lang file, just the entities themselves are not named.

I can chime in and confirm this happens on a new vanilla world. I opened a blank, flat world to test a pack and it had the speed-glitch even before I added any packs, after I added the pack and when I removed the pack. It never went away. The same happens on my realm with random people.

Unfortunately just started happening to me on my Realm....I have a lot of paintings....repaired them all....moved away for a bit and came back 2 minutes later to see some of them already gone missing....I did built a command contraption to detect if they would "fall off the wall" as you would call it but this doesn't happen.

They simply disappear 😞

The problem still persists in 1.19.50 - /gamerule disablecommandblockoutput, /gamerule sendcommandfeedback are just completely stuck in whatever mode they are in. For me personally, on my realm, it doesn't even help of putting a repeating commandblock with the "/gamerule sendcommandfeedback false" command in it. It simply autoenables every single tick.

Not the end of the world, but the immersion is a bit lost when one uses some command tricks to make stuff happen.

can confirm it doesn't work on XBOX one and controller....cannot possible get to the y-coordinate...not even when using keyboard and arrow keys

can kind of confirm this happens to me as well for the past 24 hours....tried a gazillion times and also tried resetting the slot

May I deduct, just to be safe, that if I keep the version below that of 1.19.10 in my behavior packs, the old syntax will still work after the new execute command goes live?

I upgraded from a GTX 1080 to an RTX 3070 on my desktop.....I never had the performance issues with my 1080 and now with the way more powerful 3070....presto, I get the fps drops.

And yes, I used DDU to uninstall my old drivers and reinstalled clean recent ones. Interesting to say the least.

There might indeed be something wrong with RTX 3000 series card....I didn't even enable the RTX itself....

I went back to the non-renderdragon version in the end. There were still areas on my map that would just be unplayable....again: powerful hardware (RTX).

On my less powerfull, non RTX desktop I have no problems, which leads me to believe it might have something to do with my RTX card?

I might try playing it (with low render distance) on my internal GFX card to see if I get the same drops.

This is still an issue in 1.19.2 - my (and my friends') realm still needs command blocks to fix all the gamerules continiously

So, an interesting observation....I still can't get rid of certain structures below y=0 that have existed prior to 1.18.xx

I made them all emerald (as per my previous report) so once the issue is resolved, I can remove them. However, I tried to hollow them out to see what would happen and what do you know?:

If I do this, it stays like this. I just can't get rid of the outer layer....perhaps someone with a bit of knowledge can explain what's going on here.....

In short: certain (pre-existing) areas below y=0 cannot be removed....by hand or by /fill air....you can CHANGE the blocks though and it will stay and you can hollow them out and they stay....other than that; they cannot be removed.....they will be back once you reopen your map/realm

So I tried again with similar results. I did get the component group (burns in daylight) to work when sitting, but the "on standing" event never triggers.

So in my case, my intention was to not make the entity rideable when sitting, and then rideable again when standing. With the code above it simply becomes unrideable after sitting once.

Looking into the content logs, there were some remarks about the sittable part not being parsed correctly, but when putting it through the various JSON parsers and validators, the code appears to be 100% correct. And it should, because I simply copy/pasted it from another section which is 100% correct.

I will attempt a whole new, blank entity with only a sittable component and see how that works. Will revert back again.

Thanks for your insight @TheRedSmarty (I'm still fresh as a pickle with all this, just 2 weeks of "experience")

This is just initial testing, but the new 1.19.2 appears to have better performance on my windows 10 RTX laptop. It used to drop to a crawl in certain areas, which now doesn't appear to be the case anymore (even though still dropping slightly, but way less noticable).

So am interested in hearing everyone's opinions on this.

I'm afraid so, BeeTeeKay64.

And while the main part of the bug (a lot of stuff below y=0 gone missing) is fixed, there is still part 2 of this bug that's apparently not addressed; in some cases, older structures below y=0 can't even be filled with air now. See also my screenshot below...I have some old parts that I wanted to simply remove (by hand or /fill with air) but they kept coming back. These particular areas kept coming back, no matter what I tried. So in the end I settled for filling them with emerald so i know these parts could be removed later. After 1.19.2 just hit, I tried removing them and presto; they kept coming back still.

(These emerald structures below y=0 keep coming back unless overwriting with something other than air)

you are correct, when writing this down I used the wrong component, I actually used the minecraft:burns_in_daylight one.

I need to get back to it then, I perhaps made a mistake, but when looking it up I found an old ticket and natually assume it was still not solved (MCPE-109399).

Will revert once I try again from scratch.

I can confirm this is (still) a bug.

I created a custom entity with some functionality, and one of the things I added was the ability to sit. It does sit, but I cannot get it to change/execute behavior when it's sitting. It appears the minecraft:sittable code doesn't work for custom entities:

"minecraft:sittable":

{ "sit_event": "minecraft:taking_a_seat", "stand_event": "minecraft:time_to_go" }

Steps to reproduce, add the following:

Component group to enable sitting:

 
        "buckbeak:tame": {
          "allow_sitting": true,
          "minecraft:sittable":

{             "sit_event": "buckbeak_sitting",             "stand_event": "buckbeak_standing"           }

,
          "minecraft:behavior.stay_while_sitting":

{             "priority": 0           }

}
 
Then the sittable event:
 
      "events": {
        "buckbeak_sitting": {
          "add":

{             "component_groups": [               "buckbeak_sitting"             ]           }

        }
and then the component group (in this case, I want to set it on fire when sitting so I can easily see the code is working:
 
      "component_groups": {
        "buckbeak_sitting": {
          "minecraft:is_ignited": {}
        }
 
 
Nothing ever happens. Other parts, like the "on_leash" event and subsequent component group do trigger.
 

This is on the Windows 10 (bedrock) version

 EDIT: apologies for the crappy code, the editor doesn't outline that well

Probably a duplicate of MCPE-156679 MCPE-156679 

so....I reverted back to 1.18.31 to at least be able to keep working on my build. I literally just experienced certain deleted structures at y=-60 to reappear at will.....I delete them (/fill air or by hand) and they just keep getting back.....and this is in 1.18.31, which is very strange.

The structures present in these "perpetual areas" keep coming back, funnily enough, if you /fill them with another block type, the area stays filled with the block used. But the second you /fill with air, it reverts to its previous state...