You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No champion is summoned. Entering the same commands in chat works just fine, it is only when a Command Block is used that they do not work. Additionally, the Command Block's "previous output" box is empty.
Expected Behavior:
Triggering the Command Block would summon a champion mob. I understand the champions egg command not working since there is no target player to give the egg to, but I would expect champions summon and summonpos to work fine since there is not a target player involved. (If a player is needed anyway, perhaps a player selection field could be added to the command syntax?)
Steps to Reproduce:
Place a Command Block
Enter a champions summon or summonpos command (for example, I tried "champions summon minecraft:zombie 1" and "champions summonpos -3 73 -8 minecraft:zombie 1", with -3 73 -8 just being the coords of the Command Block)
Trigger the Command Block
Crash Log: Please use a paste site like gist. (there is no crash, hence no log)
The text was updated successfully, but these errors were encountered:
Versions (Be specific, do not write "latest"):
Observed Behavior:
No champion is summoned. Entering the same commands in chat works just fine, it is only when a Command Block is used that they do not work. Additionally, the Command Block's "previous output" box is empty.
Expected Behavior:
Triggering the Command Block would summon a champion mob. I understand the champions egg command not working since there is no target player to give the egg to, but I would expect champions summon and summonpos to work fine since there is not a target player involved. (If a player is needed anyway, perhaps a player selection field could be added to the command syntax?)
Steps to Reproduce:
Crash Log: Please use a paste site like gist. (there is no crash, hence no log)
The text was updated successfully, but these errors were encountered: