Press "c" no response

Question

Press "c" no response

anonyein opened this issue 8 months ago · comments

anonyein commented 8 months ago

Checklist

I read and understood ASF's Contributing guidelines
I also read Setting-up and FAQ, I don't need help, this is a bug report
I don't own more than 10 accounts in total
I'm not using custom plugins
This is not a question
This is not a technical issue
This is not ASF-ui problem

ASF version

Latest stable release

ASF variant

win-x64

Bug description

Press "c" no response, cannot make any commands

Expected behavior

Press "c" get tips

Actual behavior

Press "c" no response, cannot make any commands

Steps to reproduce

No response

Possible reason/solution

have no idea

Can you help us with this bug report?

No, I don't have time, skills or willings for any of that

Full log.txt recorded during reproducing the problem

no log

Global ASF.json config file

No response

BotName.json config of all affected bot instances

No response

Additional info

No response

Łukasz Domeradzki · Answer 1 · Sun Nov 19 2023 03:24:41 GMT+0800 (China Standard Time)

Full log.txt recorded during reproducing the problem

no log

That wasn't optional when creating issue. Provide full log as recorded by ASF while reproducing your issue if you expect from ASF development team to look into this issue.

Same for global ASF.json config file.

anonyein · Answer 2 · Sun Nov 19 2023 08:58:58 GMT+0800 (China Standard Time)

Full log.txt recorded during reproducing the problem

no log

That wasn't optional when creating issue. Provide full log as recorded by ASF while reproducing your issue if you expect from ASF development team to look into this issue.

Same for global ASF.json config file.

all are default, and no console without error log when initializing the program from the beginning

Łukasz Domeradzki · Answer 3 · Sun Nov 19 2023 09:00:05 GMT+0800 (China Standard Time)

I didn't ask if there is console error, I asked for full log.txt recorded during reproducing the issue, as stated during issue creation. Are you able to provide all necessary information or would you rather solve the issue yourself?

anonyein · Answer 4 · Sun Nov 19 2023 09:02:35 GMT+0800 (China Standard Time)

I didn't ask if there is console error, I asked for full log.txt recorded during reproducing the issue, as stated during issue creation. Are you able to provide all necessary information or would you rather solve the issue yourself?

Łukasz Domeradzki · Answer 5 · Sun Nov 19 2023 09:06:16 GMT+0800 (China Standard Time)

Great, now we can move on.

Log states that interactive console is active and enabled, there are also no errors related to that, which means it should work fine. I've just verified with the version you're using that it works fine on my linux as well as windows machine.

Due to that, this is not a bug, but a technical issue related to your machine or the environment you're using ASF in:

Before you open an issue please review the contributing guidelines for this repository.
(...)
I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.

Reason for closing: technical difficulties using the program are not related to ASF development. Use appropriate support channel instead.

Please check out our wiki if you need further help.

Have a nice day!
~Archi

anonyein · Answer 6 · Sun Nov 19 2023 09:08:13 GMT+0800 (China Standard Time)

Great, now we can move on.

Log states that interactive console is active and enabled, there are also no errors related to that, which means it should work fine. I've just verified with the version you're using that it works fine on my linux as well as windows machine.

Due to that, this is not a bug, but a technical issue related to your machine or the environment you're using ASF in:

Before you open an issue please review the contributing guidelines for this repository.
(...)
I understand that if my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue that is not related to ASF development in any way, then it will be closed and left unanswered.

Reason for closing: technical difficulties using the program are not related to ASF development. Use appropriate support channel instead.

Please check out our wiki if you need further help.

Have a nice day! ~Archi

this happens from the version V5.4.13.4
and I cannot check the old version

Łukasz Domeradzki · Answer 7 · Sun Nov 19 2023 09:10:25 GMT+0800 (China Standard Time)

Alright, that's important information you've omitted then, because that sounds like a regression rather than an error.

Did it work for you before?

anonyein · Answer 8 · Sun Nov 19 2023 09:14:18 GMT+0800 (China Standard Time)

Alright, that's important information you've omitted then, because that sounds like a regression rather than an error.

Did it work for you before?

for at least one year. I check on other PC, it works well.

Łukasz Domeradzki · Answer 9 · Sun Nov 19 2023 09:29:00 GMT+0800 (China Standard Time)

Alright, I think I know what happened now.

As part of resolving #3051 ASF started ignoring invalid input, but invalid input is also (apparently) defined as out of ASCII characters, which means that Chinese users, among other not utilizing latin alphabet, can unintentionally trigger the workaround due to sending to ASF terminal something it doesn't recognize.

For now I've coded another solution that instead triggers the workaround only when user sends 100 or more of such characters in a row, which should resolve accidental problems while still resolving the original issue. I'll need to take a look if there is a better way to resolve it, but this will do for now.

Thanks for report, this should be resolved in V5.5.0.1.

anonyein · Answer 10 · Sun Nov 19 2023 09:33:22 GMT+0800 (China Standard Time)

Alright, I think I know what happened now.

As part of resolving #3051 ASF started ignoring invalid input, but invalid input is also (apparently) defined as out of ASCII characters, which means that Chinese users, among other not utilizing latin alphabet, can unintentionally trigger the workaround due to sending to ASF terminal something it doesn't recognize.

For now I've coded another solution that instead triggers the workaround only when user sends 100 or more of such characters in a row, which should resolve accidental problems while still resolving the original issue. I'll need to take a look if there is a better way to resolve it, but this will do for now.

Thanks for report, this should be resolved in V5.5.0.1.

Thanks. It (V5.4.13.4) work well on first start in the new directory that has never used before, and on the second trial fail.

anonyein · Answer 11 · Sun Nov 19 2023 09:51:53 GMT+0800 (China Standard Time)

https://github.com/JustArchiNET/ArchiSteamFarm/actions/runs/6917590724
I use this action, and it works well. Thank you for your assistance!

Łukasz Domeradzki · Answer 12 · Sun Nov 19 2023 09:58:51 GMT+0800 (China Standard Time)

V5.5.0.1 is now officially released in case you want to use it, it should no longer have this issue 🙂

anonyein · Answer 13 · Sun Nov 19 2023 10:01:21 GMT+0800 (China Standard Time)

V5.5.0.1 is now officially released in case you want to use it, it should no longer have this issue 🙂

I get it, thank you!