Revising requirements on posting attachments...

[nilly]

@nilly
1. What good does it do to make the hexer have 20+ post? I don't understand the logic behind that seeing as it's fairly easy to get 20 post.
2. Yes hexers really should give credit.
Suggestion for a third req:
If someone else has already hexed a client someone shouldn't be able to post a client with the exact same features.

Clients that are the same, and known that they are the same, don't get approved. It's difficult to tell most times because the op usually doesn't give a good description of what's in the client.

Also the 20+ post count at the very least is helpful for mpgh staff. We don't have to edit the thread to get links to link and all that.

I honestly don't know how the 20+ post count rule will work out. I'm hoping that it cuts down on the spamming of hexed clients as recently a lot of them have been posted by people with a post count below 20 (at the time they were posted, that is).

[ILikeToDLThings]

Clients that are the same, and known that they are the same, don't get approved. It's difficult to tell most times because the op usually doesn't give a good description of what's in the client.

Also the 20+ post count at the very least is helpful for mpgh staff. We don't have to edit the thread to get links to link and all that.

I honestly don't know how the 20+ post count rule will work out. I'm hoping that it cuts down on the spamming of hexed clients as recently a lot of them have been posted by people with a post count below 20 (at the time they were posted, that is).

Maybe we could add a standard client posting format?
EX:
Client name:
Version it was hexed from (If Hexed):
Original author (If Hexed):
Link to original thread (If Hexed):
Included hacks:
Screenshots:
Virus Scans:
Additional Info:

[nilly]

Maybe we could add a standard client posting format?
EX:
Client name:
Version it was hexed from (If Hexed):
Original author (If Hexed):
Link to original thread (If Hexed):
Included hacks:
Screenshots:
Virus Scans:
Additional Info:

This seems like a good idea.

[ILikeToDLThings]

This seems like a good idea.

It would be easier on you and any future minions. You could just see if 1 client was exactly the same as another and get Flengo to delete the later one. Also, you could simply refuse to approve something that wasn't in the proper format.

[IziLife]

They should tell wich version was hexed too ..
Like : 15.0 to 16.2

[ILikeToDLThings]

They should tell wich version was hexed too ..
Like : 15.0 to 16.2

Client name:
Version it was hexed from (If Hexed):
Original author (If Hexed):
Link to original thread (If Hexed):
Included hacks:
Screenshots:
Virus Scans:
Additional Info:

/post2short

[IAmDM]

There needs to be some way to prevent people with less then x amount of posts to download the client too. It's too simple to make a profile then download whatever client you want, there has to be some boundaries there too, shouldn't there?

[nilly]

There needs to be some way to prevent people with less then x amount of posts to download the client too. It's too simple to make a profile then download whatever client you want, there has to be some boundaries there too, shouldn't there?

This won't ever happen and nor do I think it should. I big draw to making an account on this site is the ability to download files (it is the reason I made an account initially). Take that away and people will only go to other sites to download.

[JustAnoobROTMG]

Lol. Post count needed to download a hack? Nonsense.
What about a forced "answer to thread" to download? << no, no and no, it will increase the amount of useless posts
The problem is not downloading, its users posting the same crap when the game is updated

Also, i think the posting format is a good idea.
Like i have said before : "16.2 hexed from mpghuser1234 15.0" when this 15.0 was already hexed....derp.
Such a title may lead people to think the 15.0 was a genuine one when it was hexed.

The "hexed from" must be the GENUINE number of the build, not the "last hexed build"