You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I get a lot of reports of issues that are mentioned in the readme, but because a lot of people get to the list through the gallery, they don't know to check there first. I doubt I'm alone in this. Opening the readme after the install is complete is also a bit late in the process I think, and the lack of user prompt likely means many people close it right after (I know I would).
I also wonder how many people try to install a list, fail due to some predictable error, and instead of looking for a solution they just say wj is broken or unstable or blame the list author.
Describe the solution you'd like
If say, you pressed download on a list and that list had a toggle that was on for "require prep steps" in the backend, it should prompt the user "this list requires steps to be completed before the download starts, would you like to open the readme?" with yes opening the readme and no cancelling the download.
I guess I could however move some steps for after the download, but having a readme open before the install starts means that at every step you can write a contingency message. I.e "if your download fails because of these English string files, you downloaded the wrong language of the game", instead of showing the readme after its done like I think it's done now, which means people will either fail to install or come and report it to you since they don't know any better
Describe alternatives you've considered
Adding a tidbit in the list description that people should open the readme first, but that's likely to be missed, plus it doesn't solve the readme opening late in the process without user prompt.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I get a lot of reports of issues that are mentioned in the readme, but because a lot of people get to the list through the gallery, they don't know to check there first. I doubt I'm alone in this. Opening the readme after the install is complete is also a bit late in the process I think, and the lack of user prompt likely means many people close it right after (I know I would).
I also wonder how many people try to install a list, fail due to some predictable error, and instead of looking for a solution they just say wj is broken or unstable or blame the list author.
Describe the solution you'd like
If say, you pressed download on a list and that list had a toggle that was on for "require prep steps" in the backend, it should prompt the user "this list requires steps to be completed before the download starts, would you like to open the readme?" with yes opening the readme and no cancelling the download.
I guess I could however move some steps for after the download, but having a readme open before the install starts means that at every step you can write a contingency message. I.e "if your download fails because of these English string files, you downloaded the wrong language of the game", instead of showing the readme after its done like I think it's done now, which means people will either fail to install or come and report it to you since they don't know any better
Describe alternatives you've considered
Adding a tidbit in the list description that people should open the readme first, but that's likely to be missed, plus it doesn't solve the readme opening late in the process without user prompt.
The text was updated successfully, but these errors were encountered: