How zhulibo/biochemicalarena works
Main Project Identification
• Type/Purpose: A networked, multiplayer FPS game focused on mutation gameplay.
Key Components
• Game Systems:
• Characters: Include characters (both human and mutant). This module also incorporates animations (HumanAnimInstance, MutantAnimInstance) and character components (combat, recoil, crosshair, etc.).
• Equipments: Group all equipment-related code such as weapons, melee items, projectiles, pickups, and equipment data. Differentiate between the “data” and “runtime” implementations.
• Player Controllers/Player States: Illustrate the control flow from input to game responses. Different controllers cater to different game modes (login, melee, mutation, team-based).
• System/Subsystems: This includes asset management, configuration storage, EOS (likely for online services), multi-culture, and player subsystems. Represent these as system services that support the main logic.
• UI (User Interface): Cover all UI-related modules (HUD, menus, notifications, shop, settings, server list, text chat). Show that UI components interact both with game state information and provide player input.
• Editor Integration: Since there is an “Editor” directory, note that some components extend the Unreal Editor for custom tooling (for instance, “Editor/Private” and “Editor/Public”) to support design-time functionality.
Relationships and Interactions
• That the Player Controllers receive input and then influence both the Game State and Character modules.
• Abilities module to Characters since abilities (animations, cues) affect character behavior.
• How the Equipments module integrates with both Characters and Game Modes.
• Link UI components to various subsystems (game state, controllers) to reflect real-time updates.
• Dependency from all these modules back to the core System/Subsystems (asset management, storage, online services) that provide essential runtime support.
• Architectural Patterns:
• Separation of concerns (e.g., gameplay logic vs. UI, and game state vs. visual representation).
• Interaction via the Unreal Engine’s component-based design, especially in the Characters and Abilities modules.
a. A container labeled “Unreal Engine Framework.”
– Core Game Systems: Abilities, Characters, Equipments.
– Game Modes and Logic: Game Modes/Game States, Player Controllers/States.
– Supporting Systems: System/Subsystems (Asset, Storage, EOS, etc.).
– Frontend/UI: HUD, Menus, Notifications, etc.
– Editor Tools (optional, but note the custom editor extension).
d. Adding notes on external services if applicable (like online services via EOS).
e. Use annotations to mention key design patterns, such as “Component-Based Architecture” (present in Unreal) or separation between game logic and UI.