How errornointernet/errornowatcher works
Main Components
a) Core Components:
• Minecraft Bot Core (main.rs)
• Bot Command Handler (bot.rs)
• Matrix Integration (matrix.rs)
• Logging System (logging.rs)
b) External Components:
• Minecraft Server
• Matrix Server (optional, based on configuration)
• Alert System (HTTP endpoints for notifications)
Component Relationships
Top Layer: External Services
• Minecraft Server
• Matrix Server
• Alert HTTP Endpoints (e.g., ntfy.sh)
Middle Layer: ErrorNoWatcher Core
• Main Bot Controller
• Command Handler
• Matrix Integration
• Logging System
Bottom Layer: Configuration & Storage
• TOML Configuration
Key Features to Highlight
• Player Detection System
• Pathfinding System
• Command Processing
• Alert System
• Script Execution
• Entity Management
Data Flow Indicators
• Bidirectional communication with Minecraft server
• Command flow from Matrix server
• Alert notifications to HTTP endpoints
• Configuration data flow to components
Specific Implementation Details
• The bot's connection to the Minecraft server using Azalea
• Command input sources (both Minecraft chat and Matrix)
• Alert system workflow (player detection → notification)
• Configuration influence on all components
Additional Elements
• Player detection radius
• Pathfinding capabilities
• Block interaction points
• Script execution flow