One thing I always loved about Wordpress was it's use of pluggable functions, basically it has a list of functions that normal do ActionA and B. The functions were created only if that function name wasn't called before. This would open up ourselves to extending a number of core functions we have, like for instance nand's security library, instead of hardcoding the changes of how ezRPG creates and reads users and their passwords, ezRPG checks to see if a method already exists and if not falls back to using its own. That leaves it up to developers of Modules/Plugins and game owners to decide and create their higher encryption, and it wouldn't affect further releases with overwrites. The goal should be to make it so no hacking is done to the ezRPG core files, developers should only be expanding on them with additional new things.
One thing I always loved about Wordpress was it's use of pluggable functions, basically it has a list of functions that normal do ActionA and B. The functions were created only if that function name wasn't called before. This would open up ourselves to extending a number of core functions we have, like for instance nand's security library, instead of hardcoding the changes of how ezRPG creates and reads users and their passwords, ezRPG checks to see if a method already exists and if not falls back to using its own. That leaves it up to developers of Modules/Plugins and game owners to decide and create their higher encryption, and it wouldn't affect further releases with overwrites. The goal should be to make it so no hacking is done to the ezRPG core files, developers should only be expanding on them with additional new things.