How angels-d/troveauto works
a. Core Automation Script:
• Central Auto-Hotkey file (TroveAuto.ahk) as the primary process that initiates the automated tasks.
b. Library Modules:
c. Supporting Tools:
• In another section, list the tools directory which houses several utilities:
• Batch installer scripts (ModInstaller.bat)
• Additional AutoHotkey scripts (StrCrypto.ahk)
• Cheat Engine tables/scripts (Trove Src.CT, Trove TP.CT)
• Demo C++ code (demo.cpp)
• These tools assist or extend the core automation process.
d. Auxiliary Data Resources:
• A block for the “钓鱼资料” folder which holds reference materials (Excel and PDF files) for fishing information. Although not directly part of the runtime automation, they provide support as documentation/training material for understanding and fine-tuning the auto-fishing functionality.
Architectural Patterns & Principles
• Clearly differentiate between the automation logic and the helper libraries. Think of the design in layers:
• Presentation/Action layer: The primary script handling user automation.
• Service/Module layer: Libraries that abstract lower-level memory access and game interactions.
• Utility/External Integration layer: Tools and cheat engine scripts that interface with in-game processes.
Incorporate Specific Project Technologies and Practices
• That the core script is developed in AutoHotkey and that the libraries are in C++ header files, suggesting mixed-language integration.
• Cheat engine components (CT files) as crucial for mapping out memory offsets and game state detection.
• That the project uses external resources (videos, forum posts, and documented offsets) to inform its runtime behavior.