How communityradargg/mod_forge_legacy works
Project type and purpose
• This is a Minecraft Forge mod (CommunityRadar) for version 1.8.9.
• Its purpose is to let players create and manage “radar lists” of trusted or scammer players in-game via chat commands and to display relevant information on the client side.
File structure
• build.gradle, gradlew, settings.gradle: standard Gradle-based Java project.
• src/main/java/io/github/communityradargg/forgemod: contains the mod entrypoint (CommunityRadarMod.java), command handlers, event listeners, and the radar list management subsystem.
• src/main/java/.../radarlistmanager: in-memory model (RadarList, RadarListEntry), manager class, and Gson adapters for JSON serialization.
• src/main/resources/assets/communityradar & mcmod.info: mod metadata and assets.
README for additional insights
• Lists the slash commands (/radar [help], /radar list add …, /radar check <player>, etc.) and their behaviors.
a. Main components
• Forge Mod Loader (FML) and Minecraft Client
• CommunityRadarMod (entrypoint)
• Command Module (RadarCommand)
• Event Module (KeyInputListener, ClientChatReceivedListener, ClientConnectionDisconnectListener, PlayerNameFormatListener)
• RadarListManager (manages RadarList objects in memory)
• Persistence Layer (Gson + adapters: GsonLocalDateTimeAdapter, GsonRadarListPlayerMapAdapter) writing JSON to disk
• Utility Module (Messages, RadarMessage, Utils)
• Resources (assets/communityradar, mcmod.info)
b. Relationships and interactions
1. On client startup, FML loads CommunityRadarMod → registers commands and event listeners on the Forge Event Bus.
2. User types a /radar command → Forge routes to RadarCommand → Command Module invokes RadarListManager to create/read/update/delete lists.
3. Event listeners intercept chat messages, key presses, connection/disconnect events → update internal state or push messages via Utility Module.
4. RadarListManager holds lists in memory; when modified (add/remove list or entry), it uses Gson + adapters to serialize to disk (src/main/resources or game config directory).
5. At client disconnect or on demand, Persistence Layer reloads JSON into RadarListManager.
c. Architectural patterns / design principles
• Event-driven architecture via Forge Event Bus
• Command pattern for /radar subcommands
• Separation of concerns: commands, events, persistence, utilities
• Use of adapter pattern for custom JSON (Gson adapters)
d. Key technologies
• Java 8
• Minecraft Forge API
• Gradle build system
• Gson for JSON serialization