Icons

Guyz i wanted to Add Soul Shackle Timer and The Azure Shield icon too so what i Think is that the Soul Shackle Timer icon is a subtype of Update packet 10017 So if that True Any1 have the Valid Icon Number Cuz i tested from 55 - 130 and nothing Appeared yet :(

It's probably a character status flag. I know the Azure Shield is.

Quote:

Originally Posted by Fаng It's probably a character status flag. I know the Azure Shield is.

Hmm i know that its Status Flag icon but i tested from 55 - 130 But nothing was Found ...So Could u tell me Azure Shield One ?

Quote:

Originally Posted by shadowman123 Hmm i know that its Status Flag icon but i tested from 55 - 130 But nothing was Found ...So Could u tell me Azure Shield One ?

Are you using hexes?
Example of status types:
0x1
0x2
0x3....

...0x8
0x9
0xA
0xB...

... 0xF
0x10
x11...

Also... didn't I already release most of the status types?

Shackled = 1UL << 47

Quote:

Originally Posted by Fаng Are you using hexes? Example of status types: 0x1 0x2 0x3.... ...0x8 0x9 0xA 0xB... ... 0xF 0x10 x11...

They're bitflags for individual status types; a bitwise OR is used on a client's status to add a status to it and a bitwise AND is used to clear specific statuses from the client's status.

0x01
0x02
0x04
0x08
0x10
0x20
0x40
...

TQ does what Jacob put above - shifting 1 up until the size of the update value (32 bits for early clients, 64 bits for later clients). (1U << x, where x is an integer from 0-63)

Quote:

Originally Posted by Lateralus They're bitflags for individual status types; a bitwise OR is used on a client's status to add a status to it and a bitwise AND is used to clear specific statuses from the client's status. 0x01 0x02 0x04 0x08 0x10 0x20 0x40 ... TQ does what Jacob put above - shifting 1 up until the size of the update value (32 bits for early clients, 64 bits for later clients). (1U << x, where x is an integer from 0-63)

I already use that method. Thanks for catching my mistake. I'm shocked that I wrote that instead of your example. My project probably isn't going to benefit from my current state either... I guess I should just go to bed instead of trying to stay up with you guys from the UK. Have a good day.

Quote:

Originally Posted by Fаng I already use that method. Thanks for catching my mistake. I'm shocked that I wrote that instead of your example. My project probably isn't going to benefit from my current state either... I guess I should just go to bed instead of trying to stay up with you guys from the UK. Have a good day.

He is not from UK, neither am I. :confused:

Yeah, I'm from the USA. My sleeping schedule is just majorly screwed up right now, as usual.

I think you two are getting confused between the Status Packet's Type Enum (which is just random values) and the Entity Status Type Bitwise Field.

In this case as its a timer its a specific value for the Status Packet's Type field, not the Entities Bitwise Field. So Fangs correct in this instance.

Unless TQ really are that retarded and have mixed the two systems so as the Entities Status lasts for a limited amount of time =/

Update packet (1017/10017) -> Update subtype (status flags) -> Flag bitwise type -> value.

I was talking about the flag bitwise type, after they established to use the status flag update type. Or did you mean shadowman123 and Fang?

Nono i meant you and him, i guess TQ really are that retarded after all....hard to believe really.

Quote:

Originally Posted by Korvacs Nono i meant you and him, i guess TQ really are that retarded after all....hard to believe really.

It's TQ. :rolleyes:.

Quote:

Originally Posted by I don't have a username It's TQ. :rolleyes:.

Even so, some of their programming is really nice...

Quote:

Originally Posted by Korvacs Even so, some of their programming is really nice...

Remember the finding a valid spot to drop an item calculation in the EO? ;)

But some is good... some is just awful. Our source is much better than theirs (at least the EO one)!