This is not a priority for me, but since it's been asked, this ticket is to document the work that would be required for initiative.sh to run effectively at the command line.
The first several months of development took place as a CLI app before I ported it to WebAssembly, so the core crate (encompassing the bulk of the logic: command parsing, character generators, etc.) ran and continues to run well at the command line. However, the cli crate is no longer at parity with the web crate, missing the following features:
Note that there are two command-line interfaces, rich (the default) and light (used when the input is not a tty, eg. if you run echo npc | cargo run). There is not currently a switch or configuration option to force a particular interface.
This is not a priority for me, but since it's been asked, this ticket is to document the work that would be required for initiative.sh to run effectively at the command line.
The first several months of development took place as a CLI app before I ported it to WebAssembly, so the
corecrate (encompassing the bulk of the logic: command parsing, character generators, etc.) ran and continues to run well at the command line. However, theclicrate is no longer at parity with thewebcrate, missing the following features:Note that there are two command-line interfaces,
rich(the default) andlight(used when the input is not a tty, eg. if you runecho npc | cargo run). There is not currently a switch or configuration option to force a particular interface.