When using the experimental feature that granted access to “/execute as…” you were able to use “@initiator” in npcs. This no longer works when modifying an npcs current commands. Ex: execute as @initiator run playsound mob.villager.no @s ~ ~ ~
this command no longer works in a npc as of 1.19.5
Linked issues
is duplicated by 4
Attachments
Comments 4
After doing some tests, the @initiator selector is only affected in 1.19.50 experimental worlds with "Upcoming Creator Features" Toggle ON however works completely fine in 1.19.50 non-experimental world.
If you have a copy of the world available, you might like to upload a copy of it for investigation.
On Windows 10 you can use the Export world feature.
On Android or iOS you need to use a file explorer to navigate to Device storage > games > com.mojang > minecraftWorlds
On Xbox or Switch the only way is to upload it to a Realm, and then download the world on Windows 10 or Android/iOS. (Please do not purchase a Realms subscription just to provide a world to us - but if you have a Realm already this may be a viable option if you wish to do so.)
Here are the steps to copy a world save on PlayStation:
Make sure your BLANK USB stick has been formatted to FAT32
On your PlayStation, go to Settings > Application Saved Data Management > Saved Data in System Storage > Copy to USB Storage Device > Select Minecraft > Select Saved World to copy > Copy
This should then copy the world save to the USB, which you can share to a file sharing site such as OneDrive, and then share the link.
If the world is larger than 10MB you can upload the world to OneDrive or a similar file sharing site, and then share the link.
Seems like the `@initiator` selector when used on NPC no longer works with the pack's `min_engine_version` set to `1.19.50`. It introduced the new execute commands, but somehow had affected `@initiator` selector.