[MCPE-158735] "trigger" block event response

"trigger" block event response doesn't throw error when it's value is array

Working

"event": {
    "example": {
        "trigger": "anyOtherEvent"
    }
}

Not Work But No Content Logs

"event": {
    "example": {
        "trigger": [
            "anyOtherEvent"
        ]
    }
}

Steps to Reproduce:
1. Download addon provided below and import to minecraft
2. Active addon to the world ( Turn on Holiday Creator Features is needed)
3. Get block by enter following command

/give @s issuetest:testblock

4. Place that's block to anywhere

5. Interact with that's block

Observed Results:
The event named "e2" has triggered but not trigger "trigger" event response

Expected Results:
The event triggered will thrown error to content logs

Attachments

Test Issue.mcaddon

Comments 4

EveryCabbage884 2022-07-11T10:05:37Z

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Could you please attach an example add-on to this ticket?

Additionally, to make your bug report as effective as possible, please add a video and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.
Observed Results:
(Briefly describe what happens)
Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

v-baslod 2023-04-26T13:06:57Z

Could you please elaborate on the expected results? Should interacting with the block (jumping on it or right-clicking it) not produce any messages and only produce content log errors?

This ticket will automatically reopen when you reply.

NguyenDuck 2023-04-26T14:17:01Z

The game will thrown content log before enter to the world, unknown syntax, invalid syntax, ect at event definition because "trigger_event" accept string only, not array

v-baslod 2023-09-29T16:57:46Z

Is this still an issue in the latest version? If yes, could you please add it to the affected versions (or mention it if you are not the reporter)?

This ticket will automatically reopen when you reply.