Originally Posted by Dave View Post
Previous part [Dave] A look inside the new GMCP for FGunZ [Part 1]

What powers do staff members have in the GMCP? And what are the restrictions?
This depends on the grade, an event team member should not have access to functions such as banning, adding warnings, etc.
All staff members have the ability to search for accounts, characters and clans.

None of the staff members can see your full IP address, see your password or change your password.

This is an example of what an admin can see. (Still looking for decent icons for the top menu.)
http://puu.sh/3zo1p.png

This is an example of the account management/overview page.
http://puu.sh/3znnb.png


Working with hash location.
As explained in my previous blog post, I use this plugin to take care of hash change events. (http://example.com/#login > http://example.com/#function1).
Say I want to manage an account, I click on the username or AID (which stands for Account ID) and then the hash in the URL will change to http://localhost/#account_84357 where 84357 is the AID.

It will then load the corresponding template and controller to show the account template and to load the account information.

Using hash locations and jQuery makes it a bit harder to add authentication since JavaScript is client sided, but I added a function at the server side which checks if you're authenticated with every request you send.

Code Snippets
jQuery example of loading the information of a single character. (http://localhost/#character_92435 where 92435 is the CID > Character ID)

[xcode=javascript]
//
else if(hash.indexOf("#character_") !== -1){
var cid = hash.split("_");
$("#characters-m").toggleClass('active');
$.get("character", {cid: cid[1]}, function(data) {
$('#main-container').html(data);
}).success(function() {
$('#body-section').fadeIn(400, function() {
initCommon();
initMenu();
});
});
}
//
[/xcode]
Due to the buggy syntax highlighter, I can only post 1 snippet.

Next blog post will contain information regarding the launcher and its CDN.
that should say "temporary mutes" and "temporary bans" not "temporarily" in the picture

all wrong.