Note: The ban is not necessarily related to dawn, the user who got banned has also used some other "suspicious" tools. But since mihoyo might already knew the existence of wine users, there is still a chance he got banned because of dawn.
The user has started using dawn since mid August. He got banned (paused) on 09/23, the ban continues to 10/23. He also plays another account with dawn but the account status is somehow still fine.
According to him, he has also used following somewhat "suspicious" tools which could also be accountable to the ban:
The exact reason for the ban is still unknown. He has asked for customer support and the only answer is he has used some third-party software hence violates the ToS.
**Note**: The ban is not necessarily related to dawn, the user who got banned has also used some other "suspicious" tools. But since mihoyo might already knew the existence of wine users, there is still a chance he got banned because of dawn.
The user has started using dawn since mid August. He got banned (paused) on 09/23, the ban continues to 10/23. He also plays another account with dawn but the account status is somehow still fine.
According to him, he has also used following somewhat "suspicious" tools which could also be accountable to the ban:
- https://github.com/xunkong/KeqingNiuza , gacha expoter, windsong lyre auto-playing
- https://github.com/DGP-Studio/Snap.Genshin , gacha expoter, launcher, account switcher, FPS unlocker. He has not used the most suspicious "FPS unlocker" feature.
- https://github.com/Sporif/dxvk-async , could trigger anti-cheats according the README
The exact reason for the ban is still unknown. He has asked for customer support and the only answer is he has used some third-party software hence violates the ToS.
Going only on the information available, it's likely that the tool was KeqingNiuza, specifically the lyre autoplay feature relying on hooks into user32.dll. As far as we (AAGL Discord) know, we've had numerous users flip on DXVK Async on deck with no issues, and Snap.Genshin seems to be another launcher like AAGL and Paimon Launcher.
Though, it might also be Snap.Genshin, if HYV started detecting proxies in the middle somehow.
That being said, most of our users are outside CN; we may simply not have received a report yet.
(This is only my opinion, and isn't implied to be fact)
Going only on the information available, it's likely that the tool was KeqingNiuza, specifically the lyre autoplay feature relying on hooks into user32.dll. As far as we (AAGL Discord) know, we've had numerous users flip on DXVK Async on deck with no issues, and Snap.Genshin seems to be another launcher like AAGL and Paimon Launcher.
Though, it might also be Snap.Genshin, if HYV started detecting proxies in the middle somehow.
That being said, most of our users are outside CN; we may simply not have received a report yet.
(This is only my opinion, and isn't implied to be fact)
I think the main issue here is creating a "play-time" modification to obtain some advantage, which is detectable as a non-regular behavior by the servers. As long we don't make any non-regular behavior, we're safe, unless Hoyoverse decides to make a witch hunt and ban all together, or use an anti-cheat that needs a constant communication with the servers telling status and many other things that can detect the binary tampering even if you don't cheat at all.
I think the main issue here is creating a "play-time" modification to obtain some advantage, which is detectable as a non-regular behavior by the servers. As long we don't make any non-regular behavior, we're safe, unless Hoyoverse decides to make a witch hunt and ban all together, or use an anti-cheat that needs a constant communication with the servers telling status and many other things that can detect the binary tampering even if you don't cheat at all.
The hypothesis of user32 hooks is reasonable because it can be used to modify inputs and window behavior.
The lyre playing tool does borderline justify the temporary ban. It is an excessive duration if only these three tools were used, but is likely due to limited functionality of a plain hook detector (which has a good reason to exist).
The hypothesis of [user32](https://source.winehq.org/WineAPI/user32.html) hooks is reasonable because it can be used to modify inputs and window behavior.
The lyre playing tool does borderline justify the temporary ban. It is an excessive duration if only these three tools were used, but is likely due to limited functionality of a plain hook detector (which has a good reason to exist).
Note: The ban is not necessarily related to dawn, the user who got banned has also used some other "suspicious" tools. But since mihoyo might already knew the existence of wine users, there is still a chance he got banned because of dawn.
The user has started using dawn since mid August. He got banned (paused) on 09/23, the ban continues to 10/23. He also plays another account with dawn but the account status is somehow still fine.
According to him, he has also used following somewhat "suspicious" tools which could also be accountable to the ban:
https://github.com/xunkong/KeqingNiuza , gacha expoter, windsong lyre auto-playing
https://github.com/DGP-Studio/Snap.Genshin , gacha expoter, launcher, account switcher, FPS unlocker. He has not used the most suspicious "FPS unlocker" feature.
https://github.com/Sporif/dxvk-async , could trigger anti-cheats according the README
The exact reason for the ban is still unknown. He has asked for customer support and the only answer is he has used some third-party software hence violates the ToS.
Going only on the information available, it's likely that the tool was KeqingNiuza, specifically the lyre autoplay feature relying on hooks into user32.dll. As far as we (AAGL Discord) know, we've had numerous users flip on DXVK Async on deck with no issues, and Snap.Genshin seems to be another launcher like AAGL and Paimon Launcher.
Though, it might also be Snap.Genshin, if HYV started detecting proxies in the middle somehow.
That being said, most of our users are outside CN; we may simply not have received a report yet.
(This is only my opinion, and isn't implied to be fact)
I think the main issue here is creating a "play-time" modification to obtain some advantage, which is detectable as a non-regular behavior by the servers. As long we don't make any non-regular behavior, we're safe, unless Hoyoverse decides to make a witch hunt and ban all together, or use an anti-cheat that needs a constant communication with the servers telling status and many other things that can detect the binary tampering even if you don't cheat at all.
Don't cheat in the form of playing lyre songs. Simple as that.
The hypothesis of user32 hooks is reasonable because it can be used to modify inputs and window behavior.
The lyre playing tool does borderline justify the temporary ban. It is an excessive duration if only these three tools were used, but is likely due to limited functionality of a plain hook detector (which has a good reason to exist).
It's also very interesting that the ban isn't permanent.
Case acknowledged. No actions needed.