How arjun99ab/ovo works
Main Components
a. Modloader Core: The heart of the system responsible for orchestrating mod management. This includes modules like the modloader scripts found under src/modloaders and the various version-specific directories (e.g., 1.4.x, dimensions_v101, etc.).
b. User Interface (GUI): The front-end components (HTML, CSS, and JavaScript under directories such as src/img, assets, and various index.html files) that display menus, mod lists, and settings dialogs.
c. Mod Management & Customization: Components that handle the enabling/disabling of mods, configuration of custom mod settings, and integration of community-made mods. This is reflected in the “mods” directories (e.g., src/mods/general, src/mods/modloader) and the configuration files (such as storage.json and mod configuration files).
d. Skin and Community Level Support: There are directories for skins (src/skins), community levels (src/communitylevels) and other customization assets that allow users to extend or modify the game experience.
e. Cross-Version & Data Persistence Layer: The project supports 9+ versions with shared storage and compatibility. This layer deals with saving settings, caching data across sessions, and ensuring that different versions of the modloader and the game runtime co-exist.
Relationships and Interactions
• The User Interface interacts directly with the Modloader Core by sending commands (enable/disable mods, update settings) and receiving status updates.
• The Modloader Core acts as a mediator – it loads mod scripts from both the “mods” and “modloaders” directories, coordinates community levels, and applies skins.
• The persistent data/configuration component ensures settings and mod choices persist in local storage or configuration files across sessions.
• The system supports multiple game runtime versions. These are maintained in separate version-specific directories (like 1.4.x, dimensions_qa_*, etc.) and the mod loader switches or adapts its behavior accordingly.
• External integrations (like GameAnalytics, Crazygames SDK, etc.) are included in several directories and should be represented as external services interacting with the modloader.
Architectural Patterns and Important Design Principles
• Modularity: The project is broken up into many independent modules (for mods, skins, community-levels, version-specific configuration) that the core loader integrates.
• Separation of Concerns: A clear separation is maintained between the user interface components and the logic for loading and managing mods.
• Extensibility/Plugin System: The design supports adding custom mods and skins with minimal changes to the core structure.
• Cross-Version Compatibility: The system design allows a single modloader to work with multiple, sometimes significantly different versions of underlying game code.
Relevant Technologies
• JavaScript is used heavily for dynamic mod loading and interactivity.
• HTML/CSS (with usage of files such as animate.css and fonts.css) for the GUI.
• Various support libraries like Tween.js for animations, Howler.js for audio, and GameAnalytics.js for analytics.
• Offline and caching solutions (e.g., offlineClient.js, sw.js) to support cross-session data persistence.