Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't display truncated text at all if requested text is too long #115

Open
spellboundtriangle opened this issue Aug 13, 2023 · 0 comments

Comments

@spellboundtriangle
Copy link
Contributor

spellboundtriangle commented Aug 13, 2023

Issue Description
When using the faq command, TWLHelper automatically truncates text that will cause a "wall of text" to appear in a Discord channel. I think this causes a bigger problem, though:

95% of the time, the entire message of whatever it's retrieving (FAQ entries, etc) is necessary for the full context, so the user will have to go to the page anyways. This makes it an even bigger waste of space than without truncation, because it's not even worth reading the embedded text if you're going to have to head to the full page anyways.
The "Which is the best exploit?" FAQ from the DSi Guide is a great example of this. It's a large embed as it is, but it only gets into the Memory Pit "pros" before it gets cut off.

Also, if someone chooses not to head to the linked page for the full text and only read the truncated text for whatever reason, they may miss out on important context or additional solutions/information.

So, I propose one of these:

  1. If the text entry is too long, don't embed any of its contents at all, just give a button/link to the FAQ/page/whatever
  2. Don't truncate text at all, text walls galore

I think the former would be the way to go, but either of them would be better than how it is now, in my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant