DAE think that hexes should not be approved?

[ILikeToDLThings]

Seriously, it takes no effort to hex something and generally its not the original client maker who posts it. Some ****** who knows how to open Yogda and change a string gets thanks while the original client maker gets nothing.

[gioseba]

some people don't have/want swf editors on their computer

[ytherno]

all people who release hexed clients only want thanks oki bb

[silentWizz02]

You have a serious problem in there.

[Yotsuba]

Well they did waste their hexing it and putting it up.And if it were so easy why don't you try/do it?. Also the point you bring up is that the owner gets nothing, I do agree with. I posted up a client once but I gave credit to the rightful owner who helped me make it.

[ILikeToDLThings]

Well they did waste their hexing it and putting it up.And if it were so easy why don't you try/do it?. Also the point you bring up is that the owner gets nothing, I do agree with. I posted up a client once but I gave credit to the rightful owner who helped me make it.

If the build is a hexable one, I have it hexed within 5 minutes. Its not hard

[artufe]

Heres how it should go -
IF the build does not add / change any client side stuff ( ie new dungeons , arena , etc ) you CAN hex someones cleint and post it , but you must contact him personally thru pms to ask for approval , cause it might be that the original owner is also updating the client, or does not the client to be updated, or does`nt want some random getting all the thanks just cause he has the knowledge of how to look up a tutorial on how to hex a client.
IF the build adds new content ,clients from previous builds should not be hexed/posted cause it just causes confusion amongst the "leechers" cause most ( NOT ALL ) of them cant tell the difference between hexed , and nonhexed. Thus resulting in some obvious signs of hacking in realm , ie saying that they cant see the new dungeon , or why do they crash near the new arena place / dont see it at all. I have had countless ppl tp to me when I call out a lucky god/ epic dungeon , and shouting out that they cant see it.


I went on quite the rant there .

[Discombobulator]

I believe all credit for the original client should be stated in the OP. People who are giving thanks need to realize what a hexed client actually is beforehand.

[ILikeToDLThings]

Heres how it should go -
IF the build does not add / change any client side stuff ( ie new dungeons , arena , etc ) you CAN hex someones cleint and post it , but you must contact him personally thru pms to ask for approval , cause it might be that the original owner is also updating the client, or does not the client to be updated, or does`nt want some random getting all the thanks just cause he has the knowledge of how to look up a tutorial on how to hex a client.
IF the build adds new content ,clients from previous builds should not be hexed/posted cause it just causes confusion amongst the "leechers" cause most ( NOT ALL ) of them cant tell the difference between hexed , and nonhexed. Thus resulting in some obvious signs of hacking in realm , ie saying that they cant see the new dungeon , or why do they crash near the new arena place / dont see it at all. I have had countless ppl tp to me when I call out a lucky god/ epic dungeon , and shouting out that they cant see it.


I went on quite the rant there .

I don't think even permission would be enough. I think the original maker should be the only one allowed to post a hex, also following your rules

[nilly]

I agree that something needs to be done. I think all posts of hexed client should provide the source of the client (like the thread in which it was originally posted at). Then the other idea I had was actually requiring people to have 20 posts before posting a hexed client (because it takes me longer to fixed the links and check the client than it does for the author to hex and post it). Unhexed clients could still be posted by people with less than 20 posts. Also I should probably make a sticky on the difference between hexed and non hexed client, although, I don't think that will make much of a difference because the people that don't know the difference are the people that don't know how to/to lazy to read anyways.

[ILikeToDLThings]

I agree that something needs to be done. I think all posts of hexed client should provide the source of the client (like the thread in which it was originally posted at). Then the other idea I had was actually requiring people to have 20 posts before posting a hexed client (because it takes me longer to fixed the links and check the client than it does for the author to hex and post it). Unhexed clients could still be posted by people with less than 20 posts. Also I should probably make a sticky on the difference between hexed and non hexed client, although, I don't think that will make much of a difference because the people that don't know the difference are the people that don't know how to/to lazy to read anyways.

Sounds good. Also, can we get a rule about "mod selector" clients. Last build there was like 5-10 clients that could be made with nothing more than mod selector

[nilly]

Sounds good. Also, can we get a rule about "mod selector" clients. Last build there was like 5-10 clients that could be made with nothing more than mod selector

That won't happen till the mod selector is cross platform compatible. As it is now it only runs in windows.

[Stellar Spark]

If people want to hex an outdated client, then they can just hex it themselves, keep it, and (laugh at everyone who are waiting for a release) be done with it.

[liaojh1998]

That won't happen till the mod selector is cross platform compatible. As it is now it only runs in windows.

This is why your in-game mod selector comes in, and btw, that in-game mod selector is not made by me its by nilly, for those of you that don't know

[nilly]

This is why your in-game mod selector comes in, and btw, that in-game mod selector is not made by me its by nilly, for those of you that don't know

Sure, it was my client that you used, but you added all the hacks to it.