ezRPG - free PHP MVC rpg engine

Hello everybody!

I just want some reviews on ezRPG! 1.0 and 1.2 are both stable (1.0 is no longer being developed) and 2.0 is in public BETA.

2.0 is loosely based off of the Swiftlet MVC framework, and uses PHP namespaces. It features a custom, easy to use Role Based Access Control (RBAC) system. You can check if somebody has required permissions to perform a specific task, or just to view a specific route. The AdminCP for 2.0 is very basic so far, with the only current feature of it listing players and managing routes.

More information about ezRPG v2.0:

Architecture
ezRPG is built primarily upon the MVC design pattern. We chose this architectural pattern because it allows the abstraction between Modules and Template files, among other reasons. The core components of ezRPG is entity objects that are either an expendable object, or in some circumstances, a singleton.

Going along with the MVC design, here are how we separated the concerns of library components:

Models
A base Model class exists which we layer upon Pdo. The reason we choose Pdo is due to it's astounding support of database engines and it's generic API. We went further to include some CRUD utility methods to speed up development and help newcomers extend the engine without having to know any SQL.
We also implement a flexible second layer of caching upon common queries, which will give significant improvement in performance.

Views
We have a View class that allows developers to separate their application logic from their presentation. This comes with a few utility methods as well, in what we call "Helpers". Helpers allow developers to add functionality to the views without having to modify any library components or introduce complex mechanics into the view templates themselves.
Our plan is to implement the Composite VIew pattern, which will abstract views into a layout and templates, and remove any dependency issues between the two. Ideally the template wouldn't have to be aware of the layout or any other underlying logic. . Since views are essentially templates, we group templates into "Themes" in which Themes define their own layout and client-related dependencies.

Furthermore, Views do rely on PHP for implementing iteration and logic, but it should be noted that while PHP can and should be used in template files, the bulk of the logic should rely in the calling Module.

Controllers
Scrap that, we use Modules. Modules are much like what veterans of the MVC pattern would call Controllers, but are much more flexible. Modules can be a single component, or define a base for other components.

Plugins
Another extension of modules that we provide are called "Plugins". Plugins allow developers to define a place in execution where "something" needs to happen. Plugins can be created to fire at these bookmarks, and have the ability to extend the functionality of the runtime operation.

Library

The ezRPG library is designed to be a set of loosely coupled components that work together to create a base engine.

Caching

Primarily the cache is represented as a plain-old array which makes it magnificently easy to use. It also interfaces with APC by default, which also makes it easy to maintain and support. The implementation of the cache is also abstracted to allow most types of caching interfaces such as Memcache and Reddis.

Access Control

ezRPG contains a Role Based Access Control system, more technically level 1a flat (NIST). The RBAC itself isn't limited to only dealing with a flat hieracrchy, we chose this to simplify the security of the engine for developers. The AC can be extended to accept inheritance all the way up to a level 3 standard(NIST).
Click to expand...

Log in or Sign up

ezRPG - free PHP MVC rpg engine

Jake B. Active Member

Log in or Sign up

ezRPG - free PHP MVC rpg engine

Jake B. Active Member

Useful Searches