EndiKM

I wanted to simplify your work and wrote the problems with the fire in one report, but I see that you prefer to go the harder way. So the harder way will be.

I hope that the report will be taken seriously and I hope that it will not be closed immediately without reason or for a stupid reason.

Okay, I guess it doesn't matter, because I solved my problem differently. I made it so that the appropriate ticks were executed in the script adding the custom component, and the minecraft:tick component with the interval_range entered without numbers must be there for the ticks that are in the script to work. So I guess it's solved.

Besides, in version 1.21 there are no events in blocks anyway, so this report is not needed since these things are no longer there.

The problem is still there, but now I have created two different custom components that I need to have different ticks, not the same ones, and I can't do that because the minecraft:tick component doesn't tick one custom component, only all of them.

Yes, this is a problem for me and for all Minecraft Bedrock players in Poland.

I am sending an example addon with a cake with a lit candle

. The cake has a lit candle thanks to the event and the event is executed thanks to the "minecraft:queued_ticking" component, but I wanted the cake to be more similar to the one existing in Minecraft, so I wanted to make it so that when there is no other block under the cake, then the cake is destroyed . I created an event and added "minecraft:queued_ticking" to the general components of the cake and after I wanted to test it, I noticed that it didn't work, and when I removed the component responsible for particles, it started working.

(These are the general components of the whole cake.)

        "components": {
            "minecraft:loot": "loot_tables/empty.json",
            "minecraft:destructible_by_explosion": {
                "explosion_resistance": 0.5
            },
            "minecraft:destructible_by_mining": {
                "seconds_to_destroy": 0.75
            },
            "minecraft:light_dampening": 0,
            "minecraft:light_emission": 0,
            "minecraft:queued_ticking": {
                "on_tick": {
                    "event": "check_block"
                },
                "looping": true,
                "interval_range": [
                    0.1,
                    0.1
                ]
            }
        },

(These are the components of the one type of cake that has a lit candle.)

        "permutations": [
            {
                "condition": "query.block_state('cake:clslices') == 0",
                "components": {
                    "minecraft:geometry": {
                        "identifier": "geometry.cake1_candle_lit"
                    },
                    "minecraft:on_interact": {
                        "event": "cake:clslice11"
                    },
                    "minecraft:material_instances": {
                        "*": {
                            "texture": "example_cake",
                            "render_method": "alpha_test"
                        }
                    },
                    "minecraft:collision_box": {
                        "size": [
                            14,
                            8,
                            14
                        ],
                        "origin": [
                            -7,
                            0,
                            -7
                        ]
                    },
                    "minecraft:selection_box": {
                        "size": [
                            14,
                            8,
                            14
                        ],
                        "origin": [
                            -7,
                            0,
                            -7
                        ]
                    },
                    "minecraft:light_emission": 3,
                    "minecraft:light_dampening": 0,
                    "minecraft:queued_ticking": {
                        "on_tick": {
                            "event": "fire_candle"
                        },
                        "looping": true,
                        "interval_range": [
                            5,
                            100
                        ]
                    }
                }
            },

They still haven't fixed it even after seeing it. They're just lazy.

as for me, it still doesn't work, and besides, I don't know if it wouldn't be better to specify what tool should be used to destroy a given block or add this and that, i.e. tags for the block and the type of tool with which such a block should be destroyed

I wonder when this will be fixed.

on version 1.19.40 it still does not work

Once when I played MC Bedrock it was ok, I could set my chunk rendering to 51, and now it starts lagging even at 4 and it doesn't help to change gfx_vsync to 1 and gfx_max_framerate to 60. My graphics card is NVIDIA GTX 1050.

I am sending addon, in which the "block tag" does not work, additionally I created an example pickaxe to which I added the ability to destroy an example block and it works on this pickaxe, and on Minecraft pickaxes it does not work.

The block can be found in the Construction category in creative mode or can be recalled by typing "sample:sample_block" and the pickaxe "sample:sample_pickaxe".

Yes, this problem persists 

I think I found a solution, because I entered "localhost" in ip, and now I changed it to "127.0.0.1" and I can enter whenever I want. I might have thought a little 😅.

No error or any information is displayed.
I also created a server without addons, but the same situation is that on the first try you can, and on the second you can't.

At the top it says "NO LOG FILE! - [] setting up server logging ...", of course from the beginning when the server starts.

This is not a submission, just a question. Why is mojang lazy and won't add something like @initiator to the command block !!!!!!!!!!! 😡

@@unknown I found a problem with why this is happening and it was the fault of the program I made the addon in, because now I moved it to another program, or rather to its second version, and now everything is fine.

The program I used was bridge and now I used bridge v.2.

I changed  gfx_vsync: 1 to 0  it did not work, but when I changed  gfx_max_framerate: 0 to 60  it worked and it's better. On version 1.17.4006.0.