It's something I may do in the future, but at that point, we're getting into actual programming that requires some real life programming skill to understand, and I'm not sure if that is going to be everyone's cup of tea.
Because you can't stop at just storing output in variables. Because then the only thing you can do with it is log it. And that's the same as the command just outputting the output to the log, which it does now.
We'd need conditionals like if/elseif/else to check the output of the command. And that also means adding a function for 'does this output contain a specific string' so you could do like:
#if
@var contains true
goto blocka
#else
goto blockb
#endif
#blocka
the log was true!
#endblocka
#blockb
the log was false!
#endblockb
And that isn't even very useful, so you'd need the ability for blocks to be more like labels for specific parts of your code you want to run, meaning blocks would have to be able to contain other tags like:
#blocka
#log
the command succeeds!
#endlog
#login
do login stuff
#endlogin
#send-mail
do mails stuff
#endsend-mail
#endblocka
And all that gets difficult to implement (for me) and more and more difficult to understand as a decker.
Just not sure if there will be a big appetite for that. We want people to feel like cool ass deckers, but not actually need to be one IRL.
Time will tell, I'm not against it, but just not sure it is worth it at this point.
(Edited by Slither at 9:18 pm on 9/2/2025)
