You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea of macros supporting advanced logic has been discussed before. I'm in favour of an approach that doesn't tie this too closely to the keybind/macro system and is instead more general.
My proposal is a Functions system.
Functions are written to the Impact/functions/ directory
The filename acts as a name/id for reference within the client.
The file may contain a list of lines to be sent to chat
There may be a parser to handle logical syntax, or if possible logical commands may be added to the command system instead.
Adding commands instead of function syntax has the advantage of being usable even when typing directly into chat. Think .# to comment, .if to branch .test for boolean statements, etc... Inspired by shells such as sh, bash, zsh, powerline, etc.
"anonymous" functions may be possible too by having a command that parses and then runs a function.
Functions could read arguments either as an argc/argv list or as $1,$2,etc globals.
This idea would replace advanced macros, since a macro could simply run a function.
The text was updated successfully, but these errors were encountered:
The idea of macros supporting advanced logic has been discussed before. I'm in favour of an approach that doesn't tie this too closely to the keybind/macro system and is instead more general.
My proposal is a Functions system.
Impact/functions/
directory.#
to comment,.if
to branch.test
for boolean statements, etc... Inspired by shells such as sh, bash, zsh, powerline, etc.argc
/argv
list or as$1
,$2
,etc globals.This idea would replace advanced macros, since a macro could simply run a function.
The text was updated successfully, but these errors were encountered: