some stuff nms and mariocraft can test

[rubiidev18alt]

1: these plug-ins for blockly in a seperate repo https://google.github.io/blockly-samples/plugins/theme-dark/test/index.html https://google.github.io/blockly-samples/plugins/continuous-toolbox/test/index.html (this one is for left side 3.0 style toolbox) https://google.github.io/blockly-samples/plugins/workspace-backpack/test/index.html https://google.github.io/blockly-samples/plugins/block-dynamic-connection/test/index.html https://google.github.io/blockly-samples/plugins/field-colour-hsv-sliders/test/index.html https://google.github.io/blockly-samples/examples/interpreter-demo/async-execution.html combine all of these demos into another repo that uses the bark blocks and stuff. 2: blockly xml to javascript (you know what to do) 3: 3 things you wanna do (using the plugin repo) 4: left vertical blockly toolbox Blockly.inject('blocklyDiv', { toolbox: { start: 'end', }, }); 5: making and editing this injection code work in a bark fork

[breakfast-for-dinner]

why do we need so many plugins and bots?

i think our top priority right now should be getting the editor to function correctly

[mariocraft987]

same

[mariocraft987]

that just seems like it would ruin bark, plus bark is fine the way it is

[dumorando]

besides why can't you test it yourself if it's your own idea