TheRedSmarty

Still happening to me on 1.19.50. It's only happening within worlds (Global Resources or World Resource Packs), after leaving one (Global Resources), and right after applying the pack in Global Resources, and not when the game is initially loaded with packs applied after a restart.

Also occurs if the item has NBT data.

@Solo alt They both fall under the second issue I stated in my comment. If you don't specify a data value for a Splash Potion, it only looks for Splash Water Bottles (data value 0). You have to you use the correct data value for the effect.

Honestly, I think the three issues I described should be separate bug reports... plus one for the crashing... but all the created ones relating to one of the issues get marked as duplicates of this.

@Jayly Wow, I was expecting this to always be a one-off that occurs in random places that basically can't reproduced. Interesting to see that it is possible to reproduce, well at least my situation.

Too bad this is almost definitely not the same trigger as the one the original reporter saw.

This message just appeared to me while I was messing around with Sculk Sensors and Shriekers. I was near an Observer looking at a Sculk Shrieker when I saw it.

This happened on the Preview 1.19.20.20 version. I was on a Superflat near an active Nether Portal and an Armor Stand. There was a row of three Dirt blocks and a Repeating Command Block running a failed "execute unless", but otherwise there was nothing else in the Overworld.

@Missing244 That doesn't work. I tried updating the min_engine version in the preview edition to try and fix my own pack but it doesn't change anything. Content log errors still display, and the functions don't load.

Wait, I just tried again the following day, and it's fixed???

There is an alternate way to delete worlds that might act as a workaround.

Main Menu -> Settings -> Storage -> Worlds

Ok. Maybe it doesn't work to just put the event name directly?

In my project, I have:

"minecraft:sittable": {
    "sit_event": {
        "event": "on_sit",
        "target": "self"
    },
    "stand_event": {
        "event": "on_stand",
        "target": "self"
    }
}

You have the content log enabled and it isn't giving you any errors though, right? Because if this is the cause and it isn't, that could be a bug of its own.

minecraft:is_ignited doesn't set the entity on fire. It does nothing at all on its own, it's only intended to be tested for.

I'm actually using the events in my custom entities to change their hitboxes and it works just fine.

I attached an example pack to show the bug. In doing so, I also realized I wasn't 100% accurate with what was happening as I didn't properly realize what occurred on phases other than the full moon, so I adjusted the bug report accordingly.

Also, that example link leads to a non-existent page.

I encountered this issue twice in quick succession, yesterday with a Cat on a friend's world, and today with a custom mob.

I had died a respawned far from my Cats. When someone else loaded the area where my Cats were, one of my Cats turned invisible for a while before it eventually re-appeared. I'm not exactly sure why it re-appeared in this case, I just found it sitting on my Bed.

The same thing happened with a custom mob by using a ticking area. It teleported to me, but I could only detect it with commands. Re-logging fixes the issue here (didn't try re-logging with the Cat), and I can reproduce it consistently. This only happens with the follow owner teleportation, using commands to teleport doesn't trigger this.

Update: The main three issues still apply in 1.19.2 and 1.19.20.20 exactly as they were before. The crash doesn't occur on the release version but does still occur in the preview.

From my testing in 1.18.31, these are the issues with how data values interact with hasitem:

• For blocks with multiple data values, hasitem will detect the blocks while completely ignoring the data field in the command, and will detect them regardless of the block's data value. (What this specific bug report currently describes.)

• For most other items, omitting the data field from hasitem (or setting it to a negative value) will act as if it was set to 0, only detecting the 0 data value of the item instead of detecting all instances of that item type regardless of data value.

• For items with durability, hasitem will always act as if the data value of the damaged items is 0, and so will only detect them if the data field in the command is set to 0. This also applies to custom items with durability added with behavior packs.

All of this also applies in Preview 1.19.0.31, but the game will now crash if attempting to test for a negative data value on item IDs with only one data value or items with durability.

Edit: Just discovered in Preview 1.19.20.20 that the game also seems to also crash if testing for a negative data value on potions, splash potions, lingering potions, and arrows. I don't know if this used to happen.

You have to enter new chunks you haven't ever loaded, as existing chunks won't be altered.

Thank you for letting me know. I had searched for the issue prior to me making the report but I didn't find it. I guess I got unlucky.