Version 0.6 is going to have a great deal more security features than the previous version and with good reason. A few game projects that I have worked with were hacked and I had to spend a lot of time going through and trying to fix the hacking problems. I am going to provide a wide array of security tools in the updated version and a few I’m still working on, I suspect that a complete feature set won’t be available until at least version 1.0, but I suspect new exploits are going to pop up after the fact as new techniques are used (re: phpBB).
Speaking of which, I haven’t yet reached the point where I can use or find a reason to use some of the techniques in phpBB, notablely the one where they serialize the classes for storage. While it would be a good idea for caching, I haven’t added support for it and probably won’t until a later version when I fully tested caching techniques.
Back to the Point
It seems I went off on a tangent, the point is that I’m spending more time on security features and backend as well as research than I did on Mecha Asylum or 0.5 version of the game engine. Whether it will be better for it, of course, but I’ve looked at another game engine framework that is in the works and it appears they may have a better idea on how to do the security and filtering. For now, I think it should be up to the programmer to implement it themselves. The only way I could think of implementing something like that is if they extended the security filter class and it wasn’t meant to be used like that. As an aside, I should make it use final so that they don’t try to extend it.
Other Parts: Plugin
The plugin interface will be simple and shouldn’t take very long, the reason why I haven’t started it yet is because it would require testing and I’m not ready to work on the classes for testing. The Plugin feature set will most likely be extended and changed throughout the 0.6 development cycle as I think of new ways to reinvent the wheel. It would be a good start in the right direction given that I should have already had version 0.6 out the door by now.
Installer
It is part of the Core components, or at least that is where I’m placing it, it will most likely be in a place outside of the game as I extend it and add in Modding features. I probably won’t have this completely finished until after version 1.0, unless I decide that I have nothing better to fix or do than to crank this out of my ass. Even so, I don’t suspect that I’ll code more than the basic functionality until after the game engine is finalized.
I’ll most likely package it as a separate package for future updates, but for now, having it part of the core allows me to use and test it for when I do separate it in a later version and add the modding feature. I also won’t be working on it until after the game engine is almost complete in case I want to move it to the next version. It just depends on how bored I am and how good of a basic feature set I want to give it.
Most likely move the installer feature set to the Database Factory in some form or another and focus on improving it in a later version. I do want to have it automated in some form or another.
Possibly Related Posts:
- Mecha Asylum Design Document
- Data Store is Finished, but Still Imperfect
- If You Look at it This Way
- Configuration SPL Usage
- New Configuration Factory Possible Features
Comments are closed.