mojira.dev
MCPE-101438

run_command Keyword not working in sequence/randomize nodes

I tried to use the new run_command thing with a mob. Here's the code I used at first (WorksAsIntended.png) and worked fine, both commands executed as the mob spawned. I then tried to randomize two commands (Broken.png) and none of the commands executed. I've activated the content log and no errors show up there so the feature might be broken.

The Beta Changelog for 1.16.100.56 stated that the commands would work inside randomizers  or sequences but I can't get that to work.

 

Steps to Reproduce:

  1. Download and Import the file "TestAddon.mcpack" to Minecraft

  2. Create a new world and activate the "RunCommand Test" behavior pack.

  3. Summon a Vanilla Spider and a Vanilla Cave Spider.

Expected Results:

  • When Spawned, the vanilla spider says "test1" and "place".

  • When Spawned, the vanilla cave spider either says "option1" or "option2", properly randomizing the run_command keyword.

Observed Results:

  • When Spawned, the vanilla spider does say "test1" and "place", properly running the command it was given.

  • When Spawned, the vanilla cave spider runs no commands, since the run_command keyword does not function properly when randomized.

Attachments

Comments 6

Update 1.16.100.58 Beta
The content log claims "child run_command not valid here." on the same code I was using last week. It is now impossible to use run_command on entities as of 1.16.100.58

Update 1.16.100.59 Beta
The content log still reports "child run_command not valid here." Affects 1.16.100.59

This does not occur for me in any beta since 1.16.100.57, including 1.16.100.60. I activated the TestAddon.mcpack (with all experimental toggles enabled) and cave spiders run and randomize the command correctly. Are there any additional steps to reproduce this bug?

Yes, @unknown please check that you have experimental features enabled, as this is an experimental feature

I apologize. I've now realized that they changed it to an experimental feature in 1.16.100.57. It did seem to be bugged in 1.16.100.56 but that's about it. This seems to be working perfectly with experimental features.

Sorry again for the inconvenience :c

Closing this as Cannot Reproduce.

Armand VC

(Unassigned)

Community Consensus

Windows

Windows 10

1.16.100.58 Beta, 1.16.100.57 Beta, 1.16.100.59 Beta

Retrieved