So, if a command that isn't registered by NXL it will instead skip over it and not throw an error. So it would be hard debugging things if you don't know the syntax for this language. And modules that aren't supported by functions commands will still be executed
Right now at v1.8 to v1.9 function commands are executed automatically instead of having to be called. This is a current bug as of v1.8 to v1.9
Any unsupported modules inside of a chain block, (i.e. @function and @if commands will still be executed) will still be ran if they have started with @, if a unsupported module that starts with : is ran inside a chain block it might throw an error, or the code will skip over it. (I haven't tested that)
If an command is started with : it will not be ran outside of a module. And will be skipped, as the :packaged block will treat it as an unknown command.
If any unsupported modules inside a chain block have a @ call command written in front of it is gonna be treated as a :packaged command. If that command is ran inside the module it won't actually be executed by the chain block module. Chain-block Module Commands are started with a : which tells the chain block to run it instead of the :packaged block running it
:package-main root/me
:package-com x-auto
:packaged [
@var [x]: (integer)11
@var [usernames]: (string)Someone
@var [negativity]: (negatives)-10
@var [decimal]: (double)0.1
@var [percentage]: (percentage)11%
@output x
@output usernames
@output negativity
@output decimal
@output percentage
@function [hello]:
@if [x > 10]:
:output true
@else
:output false
@end
@end
];
So, if a command that isn't registered by NXL it will instead skip over it and not throw an error. So it would be hard debugging things if you don't know the syntax for this language. And modules that aren't supported by functions commands will still be executed
Right now at v1.8 to v1.9 function commands are executed automatically instead of having to be called. This is a current bug as of v1.8 to v1.9
Any unsupported modules inside of a chain block, (i.e.
@functionand@ifcommands will still be executed) will still be ran if they have started with@, if a unsupported module that starts with:is ran inside a chain block it might throw an error, or the code will skip over it. (I haven't tested that)If an command is started with
:it will not be ran outside of a module. And will be skipped, as the:packagedblock will treat it as an unknown command.If any unsupported modules inside a chain block have a
@call command written in front of it is gonna be treated as a:packagedcommand. If that command is ran inside the module it won't actually be executed by the chain block module. Chain-block Module Commands are started with a:which tells the chain block to run it instead of the:packagedblock running it