How ohbob/ultima-online---stealth-scripts works
Project’s Main Domains and Components
• Automation/Stealth Engine: This is the core functionality that interacts with the game (presumably Ultima Online). Look for files like “stealthScript.py”, “stealth_gate.py”, “slave.py”, “Discordance/discordance.py”, “Mining_demise_0_4.py”, and similar modules. These scripts likely provide discrete automation routines (e.g., taming, mining, and general stealth operations).
• Hotkeys and Input Handlers: There are multiple “hotkeys” scripts and a full directory called hotkeysV4 including auto-function modules. These handle user interactions, mapping specific key combinations to automation functions.
• Messenger/Integration Modules: Components under “messengers” (Discord.py and Telegram.py) indicate that the system has integrations for notifications or remote command triggering via external services.
• UI and GUI: Several directories and files support a graphical interface, such as the “gui” folder, “sampire” (which has damage counter, functions, UI and configuration), and “Tamer_helper_v1” (which includes UI and configuration files). These provide the interactive layer for the user.
• Web Interface: There is an entire “dev/stealth-web” directory which includes a SvelteKit client with both client and server build directories, configuration files, and a Python backend component in “py_stealth”. This part likely supplies a web dashboard or API for controlling or monitoring automation.
• Helper Utilities and Miscellaneous Scripts: Other standalone scripts (e.g., “create_food.py”, “obkast-middle-earth.py”, “trial.py”) and supporting modules in “helpers” provide extra utilities that round out the functionality.
Relationships and Interactions
• At the very core, the Automation/Stealth Engine performs game-specific operations. It is triggered via multiple input channels: direct script execution, hotkey events, GUI commands, or even remote commands from messaging integrations.
• Hotkeys and UI components act as front-end controllers and trigger the automation routines.
• Helper utilities can be seen as support libraries that each of the main modules can call upon for configuration and additional functionality (for example, UI configuration scripts and common functions).
Architectural Patterns and Design Principles
• Separate the concerns: input (hotkeys/GUI), core automation/business logic (stealth scripts), integration (messengers), and external interfaces (web backend and front-end).
Final Elements
• Detail—while the architecture is a collection of many specialized scripts, try to capture the essence of each category rather than listing every individual file.
• The core “stealth/automation” layer sits at the center.
• Input methods (hotkeys, GUI, web inputs, messaging) attach as interfaces to the core.
• The web interface is split into the modern client (SvelteKit) and a Python backend that also integrates with the automation routines.
• Shared helper utilities and configuration modules support each component.