MinusGix
MinusGix
There is a pattern where utility macros are defined for common things that are performed in a certain area of the game, but aren't intended to ever be used elsewhere....
Currently we simply write out the macro definitions to the config file in whatever order it decides, but it would be nice for readability to have the option (perhaps on...
Handling this *properly* might be impossible without tackling the problem of having several different Twee projects in one workspace, but it should be possible to improve the experience.
When opening a normal Twine project without definitions (such as extracting their own with TweeGo so they can use the files), they may see *many* warnings about unknown macros. We...
It would be nice to use some existing simple text similarity algorithm to make so if the user types an incorrect passage, we can provide an option to correct it...
It would be nice to let users who want extra validity checking to specify valid variables *and* their types. This issue is more of me spilling out ideas, since this...
It would be useful to check if all paths in a passage left to another passage. This would help avoid issues of soft-locks. The issue with this is that it...
Currently, macros don't provide autocomplete for passage names (like link syntax does). It would be beneficial to users if we could provide that. The sc2 arguments parsing already allows incomplete...
SugarCube-2 Templates aren't that common, but they are common enough for some verification of valid templates to be useful. I think this could/should work like macros. Unrecognized templates have a...
It would be useful to let the user specify the names of their setup variables to allow checking them for validity. It isn't uncommon for the access to be written...