Harlowe now supports custom macros, however, these macros are stored as state variables, so there's a lot of sharp edges for users. An entry regarding this feature should probably cover:
Custom macros that are added to the story in an earlier part, like a start-up tag, won't be included in saved games that are past that part.
Changing custom macro definitions, such as to fix a bug, will not effect the copy of the macro in saved data.
Since custom macro definitions are static if players use one of the "test game starting here" features or otherwise start the game from a passage after that macro was defined, it won't be defined. This is pretty obvious, but may run counter to user expectations.
We could recommend users always define macros in headers or something to alleviate most of these issues, but that feels like overkill.
Harlowe now supports custom macros, however, these macros are stored as state variables, so there's a lot of sharp edges for users. An entry regarding this feature should probably cover:
We could recommend users always define macros in headers or something to alleviate most of these issues, but that feels like overkill.