johnathan
Member
Lately we've noticed many people being banned from playing COD Ghosts from Infinity Ward's suspicion that those people have been modding the game or was involved/participated in activity associated with modding, cheating or boosting. Players are also getting banned who are joining xp lobbies. These lobbies may change your stats severely and will make your player stand out above everyone else. You may not be the one modding, but benefiting from a mod is just as guilty in the eyes of Infinity Ward.
Most of these bans occured almost directly after update 1.07. It seems in earlier versions, 1.06, 1.05, etc., Infinity Ward was tracking/taking note of how we are modding the game and update 1.07 would provide them a way to target players that are modding (Changing Squad Points, Time played, etc.) and/or have unusual stats on the leaderboard and ban them. If you have been banned you may first see the error stating "The account [Player's Name] has been permanently banned...." and even after that you may see a different one stating "This console system has been banned from accessing Call of Duty Ghosts..." which probably means they've blocked our MAC address or less likely our ip which I doubt.
Do you think we could find out what Infinity Ward has included in update 1.07 that is banning people quicker than ever? If it is something in the update files that is communicating with their server by sending a flag and alerting them that there is unsual activity on our account, we need to find and eliminate this functionality. Some of our accounts maybe be banned but we need to find a solution so our future accounts remain anonymous. The two files PARAM.SFO and EBOOT.BIN seem to be untouched after comparing updates 1.05, 1.06 and 1.07 but default.self and default_mp.self have changed significantly. Maybe the solution is in these files? If not it has to be something in this game folder that we can change so that we can prevent this because this wasn't happening before, or do you think their mod tracking system is hosted on their servers?
Infinity Ward is playing smart, why cant we? If we can figure out how to create CFW we can figure this out.
Most of these bans occured almost directly after update 1.07. It seems in earlier versions, 1.06, 1.05, etc., Infinity Ward was tracking/taking note of how we are modding the game and update 1.07 would provide them a way to target players that are modding (Changing Squad Points, Time played, etc.) and/or have unusual stats on the leaderboard and ban them. If you have been banned you may first see the error stating "The account [Player's Name] has been permanently banned...." and even after that you may see a different one stating "This console system has been banned from accessing Call of Duty Ghosts..." which probably means they've blocked our MAC address or less likely our ip which I doubt.
Do you think we could find out what Infinity Ward has included in update 1.07 that is banning people quicker than ever? If it is something in the update files that is communicating with their server by sending a flag and alerting them that there is unsual activity on our account, we need to find and eliminate this functionality. Some of our accounts maybe be banned but we need to find a solution so our future accounts remain anonymous. The two files PARAM.SFO and EBOOT.BIN seem to be untouched after comparing updates 1.05, 1.06 and 1.07 but default.self and default_mp.self have changed significantly. Maybe the solution is in these files? If not it has to be something in this game folder that we can change so that we can prevent this because this wasn't happening before, or do you think their mod tracking system is hosted on their servers?
Infinity Ward is playing smart, why cant we? If we can figure out how to create CFW we can figure this out.
Last edited:
it
Carry on pissing them off 
