I was wondering if anyone would be interested (Who are using the official files, now that they've been leaked.) in using the backend engine I developed...
However of course with all donation based things removed from it strictly to be used as a registration/administration(gm) panel... this system has been designed to be very extensive and I would supply updates to such.
A bit of futures from the engine,
- -Ban Players
It will allow people under the access level you require to be able to ban players by account, or player name.
- -Unban Players
The same as banning but instead un-banning the specified player.
Note: This will also have it's own individual access level setting which can be changed.
- -List bans.
This will list all of the bans into a large page,
all bans which have been preformed by this system will include reasons for bans.
Which will make staff management more simple/easy when trying to figure out why a player was banned or etc.
It will also specify who banned the showing player.
- -View Players
--Show players full stats(HP,MP, etc)
--Show players inventory (Including stats on weapons, Awakenings and etc.)
--Remove an item from the player that you select from their inventory.
- -Level Access Control
Basically the entire system is based on an internal database which requires you to enter a username/password for the logging in user when they do this it's not based on in-game log-in currently.
Later on I might make it to where you can configure it to read from either,
However because of this you're able to control an individual 'access level',
Per each administrator/gm meaning you can restrict certain GMs from certain areas/functions.
Allowing you to keep those who you have very little trust for away from potentially dangerous functions.
- -Fully Logged
Any action that happens within this system is automatically logged not only to flat file but on it's console.
All logs are stored with an exact date and time of when each event occurred which IP preformed it... As well as which GM preformed it.
- -Integration/Flexibility
Because the way this engine works you're not limited to the PHP panel that will be included.
If you understand the protocol you'll be able to develop you're own GM Panel via an application even if you wish, it could be in a various amount of languages or even an in-game d3d hook/chat hook which implements new GM /commands.
- -Security
Because the way the engine works it will require a unique key which you can either specify or have it randomly generate for you.
This key will stop other users from being able to use the protocol to just execute commands via throwing them at your server.
Not to mention they'd also have to be authenticated as a GM/Administrator in order to execute anything anyways but it's an extra precaution/security measure to insure that nothing can go wrong.
Since the engine is responsible for handling all the database transactions by making any external applications or panels which you'd like to give to your GM's that interact with it.
You're not putting your entire database at risk by making it's remote access ports available in your firewall or providing it's credentials to potentially untrusted users.
Or even if they're untrusted dim witted users who could possibly be key-logged and cause your server to be compromised.
Security was a large aspect that was far from overlooked in the development of this engine.
- -Speed
The speed behind this engine is far greater then the time it takes to connect via ODBC libaries+PHP or even AODBC.
I've tried both first hand and where PHP will take a matter of even two seconds to five, this engine has out preformed PHP by far by only taking a matter of 0.1 mili-seconds to one-two seconds even on the highest/largest of transactions.
There's other futures but I don't feel like spoiling them unless people are really interested(That and I can't remember them all I've been up all night).
Why?
It gives me a reason/motivation to continue further development on the engine and also gives me a chance to get further input/request for futures on it.
Additions?
I'm planning on making a lot of different 'hook' based additions to it which will allow it to directly interact with the world server.
Meaning it will be able to do things such as send notices to the in-game world via a panel communicating with the engine.
A possible anti-hack idea was put into play but hasn't had any progress made on it.
Source Code?
The PHP side will be freely open source but the binary side however for security reasons will have to remain closed source as well as because I won't be removing a lot of donation based functions because they're also used in some administration scenarios.
Let me know what you think, give me input.
And if you guys would like me to release it I'll do so with an installer/full guide of how it works and etc.
There's also a bit of information from when I originally designed it here.
Screen Shot
The following is screen shot of the engine in action.
API Call Example(PHP)
PHP Code:
<?php
class Backend {
var $global_key = "No_key";
function engine_exec($exec_data){
$fp = fsockopen($this->consrv, $this->conport, $errno, $errstr, 30);
$out = $global_key.$exec_data['id']."||".$exec_data['data']."||".chr(10).chr(13).chr(12);
fwrite($fp,$out);$data=fgets($fp);fclose($fp);
return $data;
}
function get_characters($username){
$username = htmlentities($username);
$username = $this->odbc_esc($username);
$cmd = array("id"=>"A5","data"=>"$username");
$data = $this->engine_exec($cmd);
return $data;
} //GET CHARACTERS BY THE ACCOUNT NAME
}
?>
Originally Posted by Luxury
Re: Backend Engine/Administration System?
