Better customtext management #5360
Unanswered
Andre601
asked this question in
Ideas and Feature Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Right now any
/customtext
value is stored inside a singlecustom.txt
file.This feels extremely weird as you have to deal with a somewhat unusual system for creating different chapters (Using
#text
for chapters) and also suffering the problem that text is auto-paginated if it goes beyond 9 lines.My suggestion is to update the system to use a dedicated
customtext
folder, where each chapter would be its own file to manage.In addition could the files allow the usage of settings through a YAML-frontmatter like formatting to change stuff like the split/pagination behaviour.
As an example, if I want to make a
/customtext voting
command that prints a text without any pagination, I would make acustomtext/voting.txt
file with the following content:This would print all lines without any pagination when using
/customtext voting
Additionally, to make the creation of new TXT entries easier could perhaps a
--create
option be considered?It would essentially create a bare-bones example using the provided name as file name. I.e.
/customtext newtext --create
would create a file callednewtext.txt
Alternatively could it be its own dedicated command (or you would use a specific subcommand, but that may break existing setups)
Beta Was this translation helpful? Give feedback.
All reactions