Eh, there are a few things that can be taken from this that could help MPGH.
Having multiple versions of the same hack with some features disabled depending on their status on MPGH, with special BB tags that allow you to section off the different versions.
E.G.
Code:
Hack for everybody
[PostCount=10]
Users with posts above 10
[/PostCount]
[RegistrationDate=June 2009]
Hack for users that registered before June 2009
[/RegistrationDate]
[RegisteredFor=3 months]
Users who have been registered on the site for at least 3 months
[/RegisteredFor]
[ActivityRatio=.50]
Users who have at least 1 post per two days since registration
[/Ratio]
Either that, or having a MPGH API that coders could use to create a login GUI for their hack where you have to supply your MPGH credentials and then from there they can make up their own system of checks and permissions.
/Start of possibly just shooting my mouth off
I personally am working on an APB: Reloaded triggerbot (Link in sig) and I require a 20 post limit. This keeps my bot from being leeched outside of MPGH and generates traffic to MPGH from users who have the bot that tell their friends to come sign up.'
As some proof of my Tbot generating traffic, which I personally have no way of verifying that this is actually what is going on, I have 75 referrals since I posted the triggerbot with it's post count limit and my AFKBot code as a general proof of knowing how to make working code that isn't detected (Even if it was in AutoIt)
Of course, the post limit also encourages users to just spam, which is where a simple post timer can come in. If a user posts 20 times in all of 10 minutes, theres probably something wrong. :/
/End of possibly just shooting my mouth off