mchekin/rpg

This system is a multiplayer online role-playing game engine built on Laravel, featuring a domain-driven architecture for managing characters, inventory, and combat. It supports core gameplay loops including character creation and progression, real-time battle resolution, and player-to-player trading through a personal store system. The application provides a full-stack interface with Vue.js components for inventory and store management, alongside a scheduled task system for passive character regeneration.

The project underwent a major framework upgrade to Laravel 8, modernizing the build tools, configuration, and directory structure. Concurrently, significant new features were introduced, including a complete authentication system, character management, and core gameplay mechanics like battles and inventory.

22 changes

This period focused on refactoring the application's backend into a domain-driven architecture, introducing repositories, services, and factories to separate concerns. Simultaneously, the frontend was modernized with Vue.js components and a new asset pipeline, while comprehensive test coverage was added for both unit and feature scenarios.

26 changes

This period focused on refactoring the application layer to use a command-based architecture, introducing command objects, services, and mappers across the Character, Equipment, and Trade modules. It also involved defining robust domain models and repository interfaces for these modules, alongside implementing the Store system for player trading. The work was supported by adding unit tests and updating the Docker environment for consistent development and debugging.

25 changes

This period focused on implementing the player-to-vendor trading and store management features, including new API endpoints and service logic for buying, selling, and inventory control. Concurrently, the codebase underwent structural refactoring, migrating Eloquent models to a unified namespace and updating database seeders for Laravel 8 and Voyager compatibility.

5 changes

mchekin/rpg was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.