How jonagamerpro1234/advancedchat works
Project type and purpose
• This is an open-source Minecraft chat customization plugin named “AdvancedChat.”
• It provides a core API plus two platform adapters (Bukkit/Spigot and BungeeCord) to hook into server events, file-based configuration, command processing, chat formatting, permission & hook integrations, and metrics.
File structure
• Top-level modules:
– AdvancedChat 1.6.x Bug Fix (core code + tests + resources + pom.xml)
– Bukkit (Spigot/Bukkit adapter with storage implementations)
– Bungee (BungeeCord adapter)
• Core subpackages:
– commands/ (command definitions, subcommands, handler)
– listeners/ (event loader, chat & inventory listeners)
– files/ (config, logs, player data, file utils)
– manager/ (ConfigManager, PlayerManager, HookManager, ColorManager)
– chat/MessageBuilder (format engine)
– hooks/ (interfaces and implementations for Vault, LuckPerms, PlaceholderAPI, DiscordSRV)
– utils/ (logging, update checker, general utilities)
• Resources: YAML files (config, chat.yml, gui definitions), plugin.yml
• Build: Maven (pom.xml), GitHub workflows, Dependabot
• Tests: simple unit test in core module (Main.java)
README
• Confirms that AdvancedChat is a plugin that customizes chat on a server.
• Mentions supported MC versions, installation steps, API usage via JitPack.
Main components to capture
– Spigot/Bukkit Server
– BungeeCord Proxy
– Core Module
– Bukkit Adapter Module
– Bungee Adapter Module
c. Core Module subcomponents
– EventLoader → registers ChatListener, CommandListener, InventoryListener
– CommandHandler → AdvancedChatCmd, ClearChatCmd, MuteCmd, UnMuteCmd, subcommands
– ChatEngine/MessageBuilder → applies formatting patterns (solid, gradient, rainbow) via IridiumColorAPI
– FileManager & ConfigFile, ChatLogFile, ColorFile, PlayerFile, CommandLogFile
– Managers: ConfigManager, PlayerManager, HookManager, ColorManager
– Hook interfaces & implementers: Vault, LuckPerms, PlaceholderAPI, DiscordSRV
– UpdateChecker & Metrics (bStats)
– Utils: Logger, Utils, InventoryView, TSkullUtils
d. Storage implementations (in Bukkit module)
– YamlStorage, JsonStorage, MySqlStorage (implements IStorage)
e. External services
– Vault (economy/groups), LuckPerms (permissions), PlaceholderAPI (placeholders), DiscordSRV (Discord integration), bStats (metrics)
Relationships & data flows
• Server emits an event → EventLoader → appropriate Listener
• Listener → delegates to CommandHandler or ChatEngine
• CommandHandler → invokes business logic, updates PlayerManager or files → returns feedback via MessageBuilder → server
• ChatEngine → loads settings from ConfigManager/FileManager → MessageBuilder → returns formatted chat message → server
• HookManager → checks for and invokes third-party hooks at runtime
• Storage layer (Yaml/JSON/MySQL) is chosen by server admin in config → storage module in Bukkit adapter
Architectural patterns & design principles
• Modular plugin design: core + platform adapters
• Event-driven (listeners register with server API)
• Strategy pattern: multiple storage strategies via IStorage
• Hook abstraction: pluggable external integrations via Hook interface
• Separation of concerns: commands, chat formatting, file I/O, hooks, storage