Currently, this implementation focuses on collecting achievements. #837
Currently, this implementation focuses on collecting achievements. #837kingchenc wants to merge 3 commits intoLmeSzinc:masterfrom
Conversation
…e structure is designed to be extensible, allowing for future enhancements such as collecting event rewards, daily check-ins, or other in-game rewards as needed. Key changes include: Core routine for navigating to achievement areas. Image-based detection and interaction with claim buttons. Logic to handle scrolling and processing multiple sets of rewards. Ensured screen state is up-to-date for image detection by adding self.device.screenshot() calls after screen-changing actions.
|
i update later |
|
read dev docs first https://github.com/LmeSzinc/AzurLaneAutoScript/wiki/1.-Start |
|
Okay thanks sir, I will stick to not using sleep and those two files for generating assets and GUI settings. I adding universe rewards too, but I am on holiday now - will update when I am back. |
- Reworked `SimulatedUniverseCollector`:
- Implemented iterative collection logic for Blessings, Occurrences, and Curios to handle multiple pages/refreshes by going back and re-entering sections.
- Replaced potentially buggy swipe logic with the back/re-enter strategy.
- Added helper methods for clicking coordinates and attempting claims for each index section.
- Reworked `AchievementsCollector` (logic updated in previous commits).
- Established `RewardCollector` as the main orchestrator/scheduler for running the individual collection tasks (Achievements, SU).
- I pretty much wiped all the sleep delays and added while timers instead.
- Adding to Scheduler if anyone need it. (like me for fresh account :D)
- General code cleanup and removal of comments/unused code within the reward collection modules.
|
@LmeSzinc Had a bit of time before holiday, reworked main collector, achievement collector, simulated universe collector and more... check it out. Still some left for automatic reward collecting, but not yet - if I get more time, I will add more. |
|
read this also https://github.com/LmeSzinc/AzurLaneAutoScript/wiki/4.4.-State-loop
|
Like I said on Discord, Im adding this because its such a headache to collect them manually. :D
Currently, this implementation focuses on collecting achievements. The structure is designed to be extensible, allowing for future enhancements such as collecting event rewards or other in-game rewards as needed.
-Image-based detection and interaction with claim buttons. Logic to handle scrolling and processing multiple sets of rewards. Ensured screen state is up-to-date for image detection by adding self.device.screenshot() calls after screen-changing actions.