How haixingtaohai/yys-auto works
YYS-AUTO is a Windows desktop automation tool for the Onmyoji mobile game. A user selects an emulator, configures a scene and challenge limit, then starts a device tab: its runner captures and recognizes the game screen, dispatches scene logic, and sends actions back through ADB. The graph also preserves documented configuration, settings, notifications, audio, and auxiliary automation. Relationships are grounded in README statements and shown source/index references; unsampled scene internals are represented by their documented subsystem paths.
Main entry points: scene_runner.py Scene runner · device_tab.py Device controls · app.py Window and tabs · image_recognizer.py Screen recognizer
Components 23
Desktop interface
- Application startup
main.py - Window and tabs
ui/app.py - Device controls
ui/device_tab.py - Settings controls
ui/settings_tab.py
Automation runtime
- Scene runner
ui/scene_runner.py - Screen recognizer
image_recognizer.py - Recognition acceleration
image_accelerator.py - ADB device management
adb.py - Screen templates
png
Gameplay scenes
- Scene dispatch registry
scenes/registry.py - Scene context and results
scenes/scene_api.py - Scene interaction helpers
scenes/scene_common.py - Farming scenes
scenes - Co-op scenes
scenes - Tower and PvP scenes
scenes - Auxiliary automation
scenes
Persistence and feedback
- Scene presets
presets.py - Persistent configuration
ui/config_store.py - Resource paths
paths.py - System notifications
notification.py - Completion audio
wav.py
Other components
- Operator
- Android emulator
Connections 34
- Operator → Window and tabs: operates
- Application startup → Window and tabs: starts
main.py - Application startup → System notifications: registers
main.py - Window and tabs → Device controls: creates tabs
ui/app.py - Window and tabs → Settings controls: hosts settings
ui/app.py - Window and tabs → Persistent configuration: persists settings
ui/app.py - Device controls → ADB device management: lists devices
ui/device_tab.py - Device controls → Scene runner: starts loop
ui/device_tab.py - Device controls → Screen recognizer: configures
ui/device_tab.py - Device controls → Scene presets: selects preset
ui/app.py - Scene runner → Screen recognizer: captures and matches
- Screen recognizer → ADB device management: runs commands
image_recognizer.py - Screen recognizer → Screen templates: matches templates
- Screen recognizer → Recognition acceleration: uses acceleration
image_recognizer.py - Scene runner → Scene dispatch registry: dispatches scene
ui/scene_runner.py - Scene runner → Scene context and results: builds context
ui/scene_runner.py - Scene dispatch registry → Farming scenes: resolves scenes
scenes/registry.py - Scene dispatch registry → Co-op scenes: resolves scenes
scenes/registry.py - Scene dispatch registry → Tower and PvP scenes: resolves scenes
scenes/registry.py - Farming scenes → Scene context and results: uses contract
scenes/dfw.py - Co-op scenes → Scene context and results: uses contract
scenes/sj.py - Tower and PvP scenes → Scene context and results: uses contract
scenes/dg.py - Farming scenes → Scene interaction helpers: uses helpers
scenes/dfw.py - Co-op scenes → Scene interaction helpers: uses helpers
scenes/sj.py - Tower and PvP scenes → Scene interaction helpers: uses helpers
scenes/dg.py - Scene runner → Auxiliary automation: invokes handlers
ui/scene_runner.py - Settings controls → Auxiliary automation: configures pauses
ui/settings_tab.py - Settings controls → ADB device management: restarts server
ui/settings_tab.py - Scene runner → Completion audio: plays on stop
ui/scene_runner.py - Scene runner → System notifications: notifies completion
- ADB device management → Android emulator: controls device
- Screen recognizer → Android emulator: captures and taps
- Window and tabs → Resource paths: loads resources
ui/app.py - Device controls → Persistent configuration: saves tab state