Board size can change during battle now so it is great if we can know it by using opencv.

TODO

• Detect board when it is complete blacked out
  • Go to every orb and hold until it is read
• Detect whether orbs are interactable
  • Detect battle (battle xx / xx) and wait for 1.5s
  • Detect empty tiles and wait for 1.5s or 3 cycles
  • When more than half the board is not readable (try again)
• Support more orbs
• Support different game ratio (need more testing)
  • Currently, only 2:1 is supported
  • There are 16:9 and also 3:2 available
  • The new iPad UI is also different
  • Template should be the same but not sure if it matters
• Mac OS uses retina and the point location can be a bit different
• Enter dungeons automatically
  • Pick the right dungeon
  • Choose my own leader
  • Enter the dungeon
• Battle counter
  • Count battle from 0
  • Detect boss battle
  • Detect OK button (clear or game over)
• Stop when out of stamina
• Quit dungeon and avoid using magic stones
  • Still need to make sure touches are working
• Fix touch issues with pyautogui
  • Sometimes, it doesn't click or mouse down
• Use skill 1 to 6 (for 周回)
• Detect board location
  • This is important when porting to Android
  • Can use the heart icon to determine the location
• Faster screenshot
• ~~~無限回廊三回まわる~~~
  • Pick the dungeon
  • Choose my own leader
  • Enter the dungeon
  • Count battle from 0 to 50
  • Clear the dungeon
  • Quit the dungeon
  • Do this 3 times
• Normal dungeons
  • The program is running for a few hours and has cleared many normal dungeons one by one
• Battle detector not working all the time
  • This should be the first thing to check
  • Continue can be very dangerous sometimes
• Detect board size based on a single orb size
  • Board size can change during a battle, rare but possible

This is very important moving forward because pointing out the board manually can be annoying.

The current implementation while being functional isn't great in the long run. I should have different strategies for different game mode. Thus, a refactor is needed to fix some problems.

• Singleton class for configuration
• Config should be easy to change
• Introduce different strategies
• Move some python scripts to a folder
  • config and main should be outside
• Board detection should be automatic unless it failed many times
• more coming soon

Currently, python is using the binary via command line and pazusoba writes the final route to the disk. This works very well but it isn't ideal because file I/O takes time. If python calls pazusoba via cdll, the data can be sent to python directly and python can simply read it and ask pazusoba to free the list. pazusoba will be compiled to a shared library as pazusoba.so. However, this is not possible unless pazusoba supports it.

WIP

• Make pazusoba.so with cmake
• Add a python wrapper
• Pass data to the shared library
• Receive the route from the library
• Update cmake so that the output is libpazusoba.so on all platforms

All good for now. However, not yet finalised but it is working.

The route might still be wrong or maybe I am just imagining things. This can be the automation issue. Note that the route can be checked every time. It is highly possible that skyfall broke it.

Original - Final - Route
LBRLGDDRGDLDLHGDBGHGBHRDGHBBRR
BRDRGDLLLLGDHGGDGDHHHRDBGBBBRR
LLULLDRDDRURRULUULDLLURRDRRDRD