(adsbygoogle = window.adsbygoogle || []).push({}); Before I talk about it I just wanna say I know its not advanced and "anyone can do it" but this is just for people who want to save time and who are new to modding.

So this is an edit to B777x's EBOOT Which is made to load the SPRX BO2_GSC_Injector.sprx and has no recoil removed.

[url] https://mega.nz/#!rFkTALaQ!_e3tZF7jX5-2FVmbHOBEBYOes5OzglsB4bDgQ8P4L48 [/url]

Includes-
-FPS (Show Host)
-Ghost/AW Camo
-Non-host Aimbot
-Red Boxes
-VSAT
-Anti Ban
-Anti Freeze

If B777x or any admins have a problem with this thread tell me and I will gladly remove it.

Credits-B777x, Jewels and Natsu

I don't know how menu creators expect us to inject with TMAPI when all the debug eboots have that issue.

I know the glitch is quite frustrating, Sorry i couldnt do it for you

that because you are the only person who have this problem

I have it too only with disable perk/clantag check When i no clip or use a zipline or whatever my screen goes black and there are no textures on the guns and every action (circle, cross ect.) are all changed to square Still not found no fix apart from dont use the no clantag/perk check eboots ahah

Never mind man :/ Jericho engine lag a lot So i'll keep the original eboot :' Thanks anyway! Keep the good work

Okay if that suits you Thanks man!

i think that you're using JeWeLs's updated addresses (there is an extra address that mess up the buttons)

anyway heres the correct addresses: (all i did was updating them from Shark's post You must login or register to view this content., You must login or register to view this content.)

    

# Remove 0x10000 from every address for ELF usage

- Cold Blooded perk check

0x00078604 - 60 00 00 00

- Clan Tag checks

0x00361B20 - 48 00

0x00361B74 - 60 00 00 00

0x00361B84 - 48 00

0x00361BF8 - 48 00

- Class name checks

0x0036EA9C - 60 00 00 00

0x0036EAA4 - 48 00

Thanks man <3 but i still get the black screen when i no clip, Not a very big issue but im just curious why that could be

Not at all, I've seen people have this very issue with debug eboots all the time. So what you're saying is, if I use your debug eboot, the issue won't be existent?