Hey guys,
So as most of you are probably aware of now, Rockstar has started banning users from GTA Online. You'll now receive a message stating that you have been banned from Grand Theft Auto Online.
![]()
Basically, this thread is just for posting any useful information you may find regarding these bans. As of right now, I'm not 100% sure how Rockstar is going about these bans, so I started looking through the EBOOT.
The only string I could find regarding a ban is "SC_ERROR_BANNED" (Social Club maybe?). There have been rumors that if you don't link your account to Social Club, you have a lower chance (if no chance) of getting banned. (Not sure if this is true or false yet). Or maybe this isn't even related to the Online banning at all :p.
This is the part of the function that may deal with the banning.
![]()
This is where it branches off to the "SC_ERROR_BANNED" part. What seems to happen is if the byte is equal to 0, it jumps all the way down to "SC_ERROR_BANNED".
![]()
Again, these may have nothing to do with the recent banning. Later I will probably check out the older EBOOTs to see if this string was around then. If you would like to check it out yourself, the function starts here: 0x93904.
Feel free to post any information you may find regarding this. :)
So as most of you are probably aware of now, Rockstar has started banning users from GTA Online. You'll now receive a message stating that you have been banned from Grand Theft Auto Online.
Basically, this thread is just for posting any useful information you may find regarding these bans. As of right now, I'm not 100% sure how Rockstar is going about these bans, so I started looking through the EBOOT.
The only string I could find regarding a ban is "SC_ERROR_BANNED" (Social Club maybe?). There have been rumors that if you don't link your account to Social Club, you have a lower chance (if no chance) of getting banned. (Not sure if this is true or false yet). Or maybe this isn't even related to the Online banning at all :p.
This is the part of the function that may deal with the banning.
This is where it branches off to the "SC_ERROR_BANNED" part. What seems to happen is if the byte is equal to 0, it jumps all the way down to "SC_ERROR_BANNED".
Again, these may have nothing to do with the recent banning. Later I will probably check out the older EBOOTs to see if this string was around then. If you would like to check it out yourself, the function starts here: 0x93904.
Feel free to post any information you may find regarding this. :)