Closed Jaffe2718 closed 12 months ago
Doesn't seem to be working well using 1.1.2 release.
So far, this is just an experimental feature. I'm not familiar with macro syntax yet, and it may take a long time to perfect this feature.
It seems that version 1.2.0-rc5 has a bug in the plugin's ability to create projects that prevents the creation of packet projects. Try this one 1.2.0-rc6
It's now working almost as expected, I'm still getting an error though:
It's now working almost as expected, I'm still getting an error though:
Working as expected !
Maybe for a more complex feature that can be made far in the future, you could add navigation from the macro to the commands calling the current function with the arguments as a JSON object.
For example, my screen is on the function1.mcfunction
, in the function2.mcfunction
I have this code:
function datapack:function1 {my_macro: "test"}
When CTRL clicking (or CTRL B) to $(my_macro)
, the function2.mcfunction
file on the first line would be listed as the usage of the macro.
There are some details of the syntax that I need to test, for example:
say hello \
world
say try to send \\
I need to adjust these details to match the actual results of the program.
$
(as the first non-space character) marks a macro line.$(variable)
.