-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Press "c" no response #3075
Comments
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 |
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? |
2023-11-19 09:01:25|ArchiSteamFarm-20892|INFO|ASF|InitCore() ArchiSteamFarm V5.4.13.4 (win-x64/1e343ea7-d4bb-4cb6-9437-57e0a54836e0 | .NET 7.0.13; win10-x64; Microsoft Windows 10.0.19042) |
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:
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! |
this happens from the version V5.4.13.4 |
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. |
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 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. |
https://github.com/JustArchiNET/ArchiSteamFarm/actions/runs/6917590724 |
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! |
Checklist
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
Global ASF.json config file
No response
BotName.json config of all affected bot instances
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: