Ok lets all cast our minds back to CO Partner.......
What did we do there? We had a Server emulator so we didn't connect to 9net9 servers and we cracked the CO Partner log in.
So here is what i was thinking.....
1. Instead of cracking each new SV as it is released pick one to keep running.
2. Bypass the server checks.
3. Find away to update the memory addresses in SV to relate to the new updates of CO2.
This way once we can tell SV the new memory addresses to look at we can keep it running without having to find all the new nasty 9net9 "hack protection" on each new release and it will also make the turn around of the bot alot faster after updates.
Just an idea, maybe I have over simplified.
Honiahaka~






