Client Hash Bug?

[PewN]

i don't know if this is a bug or not

i set a different Hash on different group id

but my account lvl 99 (admin) can connect even im using the hash for [ group_id 0 ] is this a bug or not?

[Emistry]

the client cant connect if the client using the harsh that is specify for higher level.

but higher level account can connect using the other client using lower level of harsh...

[PewN]

the client cant connect if the client using the harsh that is specify for higher level.

but higher level account can connect using the other client using lower level of harsh...

awtz -.-

i think it's more nice if they didn't set like that. i mean if 2 client hash set the group_id with higher lvl can only connect on the set hash

any possible solution on this?

client_hash: 0, hash | all group_id on 0 upto 89. can use this but if group_id 90+ can't connect they must use the hash of id 90

client_hash: 90, hash |

Edit: i think it's useless on 2 client hash

// A player can login with a client hash at or below the account group_id.
// Format: group_id, hash

bumpo!

bump

Edited December 2, 2012 by TrojanWorm

[SilverMayCry]

Just give the client with the Hash of group id 0 to your players

Then keep the Client with the hash of group 90 to your self or give it to your staff?

Anyway, use the Diff WDGForceClientHashPacket.dll so client's can connect and there is no other way to connect when using different hash

use this to get the hash nkwz rA Toolkit search for it here..

Correct me if i misunderstood what you're saying.

[solid2005]

how to use this? i need to load .dll .

i can't see it on wee.

[a1252962]

I don't think this is a bug..

regular users have to use the regular client (hash group 0)

gms & admin have to be able to use both clients.. to have those special features, and to test what the regular clients use

[PewN]

Just give the client with the Hash of group id 0 to your players

Then keep the Client with the hash of group 90 to your self or give it to your staff?

Anyway, use the Diff WDGForceClientHashPacket.dll so client's can connect and there is no other way to connect when using different hash

use this to get the hash nkwz rA Toolkit search for it here..

Correct me if i misunderstood what you're saying.

lol my problem is

i set a 2 hash then i use the client for hash group_id 0 i login my lvl 99 admin then i easily connect. my lvl 99 admin must use the lvl 90 hash but seems it's not working properly

Edited December 7, 2012 by TrojanWorm

[PewN]

any solution? bump!