It appears he has a pretty robust logging system. Having a chat with PixelTweak, it even red flags you. If your having that error every time you try to attack, you've probably been red flagged.
If anyone has more information on it, please share!
Printable View
It appears he has a pretty robust logging system. Having a chat with PixelTweak, it even red flags you. If your having that error every time you try to attack, you've probably been red flagged.
If anyone has more information on it, please share!
Errorin logging information.Quote:
Originally Posted by MattSmith
General logout error.Code:error: function(){
console.log('Something went wrong! ):');
$("#quick_success").css({backgroundColor: "#710000"}).html('An error has occured, refreshing in 5 seconds!').fadeIn(300);
setTimeout(function(){
redirect('battle');
}, 5000);
Code:} else if(json.error === 1){
$("#quick_success").css({backgroundColor: "#710000"}).html('You\'ve been logged out, refreshing in 5 seconds!').fadeIn(300);
setTimeout(function(){
redirect('home');
}, 5000);
Hereis the one he added to stop us from preventing monster attacks.
These are all just for ./battle./ though.Code:if(json.error === 4){ // Battle is over!
battle_data['monsters'][monster_key]['attack_interval'] = setTimeout(function(){
battle_data['monsters'][monster_key]['attack']();
}, 3000);
you can just ask him to remove it. Hes too nice.
Console.log isn't him logging to the server. That's client side logging to your local console in the browser. json.error is getting the 'error' id in the request that returned json.. None of this is truly useful at all.. Sorry.