Custom blocks show red and throw (IR: Unknown stacked block) — guidance on which files are required for native-level blocks

[saing048246638]

Hello, I am currently trying to add a custom category called MoonCar to TurboWarp. The category button and blocks appear correctly in the GUI, but all custom blocks render as solid red. When I run the project, I consistently get the following error:

(Sprite1: Error: IR: Unknown stacked block: mooncar_connect)

At the moment, the only files I know how to modify are make-toolbox-xml.js and the category color configuration (blockColors). With just these two changes, the custom button and category appear correctly, but it seems that the opcode is not properly registered on the VM/runtime side.

I would like to kindly ask:

• Which VM/runtime files are required to properly register a custom opcode so that the red blocks and the IR: Unknown stacked block error can be resolved?

• If I want this custom category to behave like native Scratch/TurboWarp blocks (rather than plugin-style blocks), which files are generally required to be modified in total (such as extensions, runtime, GUI, colors, etc.)?

If there is a minimal working example or a list of essential file paths that I can follow, I would be very grateful.
Thank you very much for your time and help.

[LegoBrainBiker]

the code for built in extensions is in scratch-vm develop/src/blocks
you will also need to add it to defaultBlockPackages in src/engine/runtime.js
there's probobly more you'll have to do after that, I'm not an expert on the vm, but that should be a good start.
you could also try making a custom extension that is automaticly registered.

[CST1229]

the code for built in extensions is in scratch-vm develop/src/blocks you will also need to add it to defaultBlockPackages in src/engine/runtime.js there's probobly more you'll have to do after that, I'm not an expert on the vm, but that should be a good start. you could also try making a custom extension that is automaticly registered.

the blocks being red imply that they're not defined in scratch-blocks (or they didn't link the modified scratch-blocks correctly, or the definitions in scratch-blocks have an error)