How paulmndn/vrmlbot works
VRMLbot is a Discord bot that turns VR Master League data into command responses, with server defaults and administrator messaging as supporting workflows. Discord users invoke the bot; its handlers use the VRML client to search or fetch game, player, and team data and present results. The client models seasons, bios, news, matches, and sets, backed by an HTTP layer. Guild settings and a scheduled player cache support server behavior. The graph follows documented capabilities and indexed imports; unsampled bot handlers and several VRML modules limit more specific call-flow claims.
Main entry points: game.py Games · player.py Players · team.py Teams · http.py HTTP API client
Components 21
Discord Bot
- Command handlers
bot.py
Bot Operations
- Bot configuration
lib/config.py - Admin actions
lib/admin_actions.py - Guild settings
lib/guild.py - Player cache
lib/player_cache.py - Scheduled tasks
lib/tasks.py
VRML Client
- VRML client API
vrml/__init__.py - HTTP API client
vrml/http.py - VRML utilities
vrml/utils.py
VRML Data Models
- Games
vrml/game.py - Players
vrml/player.py - Teams
vrml/team.py - Matches
vrml/match.py - Seasons
vrml/season.py - Player bios
vrml/bio.py - VRML users
vrml/user.py - Game news
vrml/newspost.py - Match sets
vrml/set.py
Other components
- Discord user
- Discord guilds
- VRML API
Connections 35
- Discord user → Command handlers: invokes commands
README.md - Command handlers → VRML client API: uses client
bot.py - Command handlers → Guild settings: uses settings
- Command handlers → Admin actions: offers admin commands
README.md - Admin actions → Guild settings: messages guilds
lib/admin_actions.py - Admin actions → Scheduled tasks: starts tasks
lib/admin_actions.py - Scheduled tasks → VRML client API: fetches player data
lib/tasks.py - Scheduled tasks → Player cache: updates cache
- Discord guilds → Guild settings: has settings
lib/guild.py - Guild settings → Discord guilds: sends messages
lib/guild.py - VRML client API → HTTP API client: requests data
vrml/__init__.py - HTTP API client → VRML API: sends requests
vrml/http.py - VRML client API → Games: constructs games
vrml/__init__.py - Games → HTTP API client: fetches game data
vrml/game.py - Games → Seasons: builds season
vrml/game.py - Games → Game news: builds news posts
vrml/game.py - Games → Teams: searches teams
vrml/game.py - VRML client API → Players: constructs players
vrml/__init__.py - Players → HTTP API client: fetches details
vrml/player.py - Players → VRML users: builds user
vrml/player.py - Players → Player bios: builds bios
vrml/player.py - Players → Games: builds game reference
vrml/player.py - Teams → HTTP API client: fetches team
vrml/team.py - Teams → Seasons: builds seasons
vrml/team.py - Teams → Players: builds roster
vrml/team.py - Teams → Matches: builds matches
vrml/team.py - Matches → HTTP API client: fetches sets
vrml/match.py - Matches → Teams: builds partial teams
vrml/match.py - Matches → Match sets: builds sets
vrml/match.py - Game news → VRML users: builds author
vrml/newspost.py - Game news → Games: links game
vrml/newspost.py - Games → VRML utilities: uses game helpers
vrml/game.py - Teams → VRML utilities: uses display helpers
vrml/team.py - Players → VRML utilities: uses display helpers
vrml/player.py - Player bios → Seasons: uses season data
vrml/bio.py