We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
视奸发现在补刀队(Fleet-2)安全海域自律,顿时发现了不对劲。接着看了一段时间,发现在这港口和这个海域之间往返,确定了这是bug,就暂停了,并且稍微看了下log。 2025-01-03 15:22:18.905 | INFO | Click (1170, 645) @ EXP_INFO_D 2025-01-03 15:22:32.923 | INFO | Screenshot interval set to 0.2s 2025-01-03 15:22:32.925 | INFO | Combat end. 2025-01-03 15:22:32.927 | INFO | [HP] ____ ____ ____ ____ ____ ____ 2025-01-03 15:22:32.931 | INFO | [Repair icon] [False, False, False, False, True, True] 2025-01-03 15:22:32.932 | INFO | [HP] ____ ____ ____ ____ 0% 0% 2025-01-03 15:22:32.933 | WARNING | Fleet died, stop auto search 2025-01-03 15:22:33.152 | INFO | [Story_options] 1 2025-01-03 15:22:33.153 | INFO | Click ( 693, 335) @ STORY_OPTION_1_OF_1 2025-01-03 15:22:33.721 | WARNING | Fleet died confirm 2025-01-03 15:22:33.724 | INFO | [HP] ____ ____ ____ ____ ____ ____ 2025-01-03 15:22:33.727 | INFO | [Repair icon] [False, False, False, False, True, True] 2025-01-03 15:22:33.728 | INFO | [HP] ____ ____ ____ ____ 0% 0% 2025-01-03 15:22:33.730 | INFO | [HP] ____ ____ ____ ____ ____ ____ 2025-01-03 15:22:33.734 | INFO | [Repair icon] [False, False, False, False, True, True] 2025-01-03 15:22:33.736 | INFO | [HP] ____ ____ ____ ____ 0% 0% 2025-01-03 15:22:33.764 | INFO | [STRONGHOLD_PERCENTAGE 0.027s] 2025-01-03 15:22:33.765 | WARNING | Unexpected STRONGHOLD_PERCENTAGE: 2025-01-03 15:22:33.766 | INFO | Auto search stopped, because fleet died 我的塞壬海域设置Fleet-1 > Fleet-2 > Fleet-3 > Fleet-4。 alas识别认为我打了D战,同时Fleet-1沉了(但是根据游戏内截图图2 (图2图是后续截的,15:43截的图,去下个塞壬海域打了几战,但途中应该没有修船),一队是沉了2艘前排,但打完这个塞壬海域了),然后后续的log是去港口,然后切换成Fleet-2,对着已经成为安全海域的NA海域西南D反复出击,清完海域,自律停止后,缺少塞壬海域结束对应的弹窗,认为还没打完,于是又回港,又来打NA海域西南D。 图2是我当时手动终止alas之后,没对一队进行检查,直接再次开启alas,在写这篇文档的途中,想起来我没确认Fleet-1的状态,于是终止alas,点开模拟器,切换成一队看到的。但这中途似乎去打了几战另一个塞壬要塞。 我把这段log单独截出来了 大概是识别错误导致的非预期行为.txt 还有个全天log 2025-01-03_alas3.txt
遇到船沉的情况,alas能够通过去识别右下角的剩余塞壬据点数,确认当前塞壬要塞是否被打完
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
在提问之前...
描述你的问题
视奸发现在补刀队(Fleet-2)安全海域自律,顿时发现了不对劲。接着看了一段时间,发现在这港口和这个海域之间往返,确定了这是bug,就暂停了,并且稍微看了下log。
2025-01-03 15:22:18.905 | INFO | Click (1170, 645) @ EXP_INFO_D
2025-01-03 15:22:32.923 | INFO | Screenshot interval set to 0.2s
2025-01-03 15:22:32.925 | INFO | Combat end.
2025-01-03 15:22:32.927 | INFO | [HP] ____ ____ ____ ____ ____ ____
2025-01-03 15:22:32.931 | INFO | [Repair icon] [False, False, False, False, True, True]
2025-01-03 15:22:32.932 | INFO | [HP] ____ ____ ____ ____ 0% 0%
2025-01-03 15:22:32.933 | WARNING | Fleet died, stop auto search
2025-01-03 15:22:33.152 | INFO | [Story_options] 1
2025-01-03 15:22:33.153 | INFO | Click ( 693, 335) @ STORY_OPTION_1_OF_1
2025-01-03 15:22:33.721 | WARNING | Fleet died confirm
2025-01-03 15:22:33.724 | INFO | [HP] ____ ____ ____ ____ ____ ____
2025-01-03 15:22:33.727 | INFO | [Repair icon] [False, False, False, False, True, True]
2025-01-03 15:22:33.728 | INFO | [HP] ____ ____ ____ ____ 0% 0%
2025-01-03 15:22:33.730 | INFO | [HP] ____ ____ ____ ____ ____ ____
2025-01-03 15:22:33.734 | INFO | [Repair icon] [False, False, False, False, True, True]
2025-01-03 15:22:33.736 | INFO | [HP] ____ ____ ____ ____ 0% 0%
2025-01-03 15:22:33.764 | INFO | [STRONGHOLD_PERCENTAGE 0.027s]
2025-01-03 15:22:33.765 | WARNING | Unexpected STRONGHOLD_PERCENTAGE:
2025-01-03 15:22:33.766 | INFO | Auto search stopped, because fleet died
我的塞壬海域设置Fleet-1 > Fleet-2 > Fleet-3 > Fleet-4。
alas识别认为我打了D战,同时Fleet-1沉了(但是根据游戏内截图图2
(图2图是后续截的,15:43截的图,去下个塞壬海域打了几战,但途中应该没有修船),一队是沉了2艘前排,但打完这个塞壬海域了),然后后续的log是去港口,然后切换成Fleet-2,对着已经成为安全海域的NA海域西南D反复出击,清完海域,自律停止后,缺少塞壬海域结束对应的弹窗,认为还没打完,于是又回港,又来打NA海域西南D。
图2是我当时手动终止alas之后,没对一队进行检查,直接再次开启alas,在写这篇文档的途中,想起来我没确认Fleet-1的状态,于是终止alas,点开模拟器,切换成一队看到的。但这中途似乎去打了几战另一个塞壬要塞。
我把这段log单独截出来了
大概是识别错误导致的非预期行为.txt
还有个全天log
2025-01-03_alas3.txt
如何复现
预期行为
遇到船沉的情况,alas能够通过去识别右下角的剩余塞壬据点数,确认当前塞壬要塞是否被打完
相关 Logs
No response
截图
还有别的吗?
No response
The text was updated successfully, but these errors were encountered: