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

Suggestion: A Simple Mode, with current interface behind an "Expert" button #8

Open
SubordinalBlue opened this issue Jan 24, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@SubordinalBlue
Copy link

SubordinalBlue commented Jan 24, 2025

Crash Assistant is great! I think it's fantastic for me; but I already understand the basics of what's going on when dealing with an MC crash.

It, I think, presents way too many choices for non-technical players... people who don't already know the difference between latest, debug, and crash logs, or what KubeJS is and its various logs—and each of those have three actions to choose from.

"Regular" computer users expect, and have kinda been trained, to look for the one button they need, like 'OK', 'Submit', or 'Cancel'. This plethora of choices and possibly new terms presented by Crash-Assistant would, I expect, just encourage people to 'take an easy way out', like just posting a screen shot of the Crash-Assistant window. In fact, that's already happened on AOE discord, now that we've included Crash-Assistant in Craftoria.

So... perhaps a default 'simple' mode, that has at most two, maybe three, buttons would be great:

  • The current "Request Help in..." button,
  • The "Upload all and copy message..." button, (maybe)
  • A (slightly) less prominent button leading to a second screen with all the choices on it—perhaps call it "More Options", "Details", or "Expert".

p.s. Thank again for making this. Happy to discuss this further in the #dev-general channel on AOE-cord if you prefer that over this GH issue thread.

@KostromDan KostromDan added the enhancement New feature or request label Jan 24, 2025
@KostromDan
Copy link
Owner

KostromDan commented Jan 24, 2025

Posting screenshots of the GUI was a massive issue (about 75% of reports) when the first studio, LunaPixel, added it. After seeing this, I implemented three solutions:

  • Upload all... and $CONFIG.text.support_name$ of commentLabel are now hyperlinks. Pressing them will result blinking for 3 seconds of according button background with light red.
  • Then upload finished: Copied! button background will blink with light green for 3 seconds to request user attention.
  • Added under comment label optional bold red text Please read the text above carefully. Screenshot of this GUI, tells us nothing!. You can disable this with new config option.

These changes have almost completely resolved the issue. According to the ATM10 Discord (about 700 reports related to my mod), less than 0.05% of users still submit screenshots. Fewer than 5% don't understand the process and ask, "I crashed, what do I do?"

Embeddedt has already suggested in the ATM Discord to hide logs and add a single button to reveal them. However, I didn't find this necessary, as Crash Assistant is also intended for experienced users. I don't want to force them to make an extra click. Additionally, they might not switch to expert mode, assuming it could hide the current "Easy mode" buttons.

As I see in your config:

	#With this you can change formulation of first sentence of comment under title.
	#CANT_RESOLVE - "If you can't resolve the problem by reading logs, join the $CONFIG.text.support_name$."
	#PLS_REPORT - "If you want to report the problem or need help, join the $CONFIG.text.support_name$."
	#For modpacks, the second option is recommended; the first is intended for individual mod downloads.
	comment_start_formulation = "CANT_RESOLVE"

You should change it to PLS_REPORT.
User reads first lines, reading logs...??? ohhh, I don't want, lets just post screenshot.

If you think it's requred, I can add option to hide mod list diff, and logs. And add button to switch to expert mode. But currently I don't see point in this.

@SubordinalBlue
Copy link
Author

SubordinalBlue commented Jan 26, 2025

Hey, sorry I hadn't gotten back to you yet.

Thank you for taking time to make a detailed reply.

I'm just gonna copy my response on discord, after Phantom reminded me to get back to this issue thread:

his suggestion of using PLS_REPORT instead of CANT_RESOLVE seems good.

ngl, happy to see Embeddedt had a similar thought before me.

otoh, Kostrom seems to be right... after that first one, we have indeed have 0(?) screen-shots-of-crash-assistant itself.

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

No branches or pull requests

2 participants