dcprotocol:hub_client:myinfo
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
dcprotocol:hub_client:myinfo [13/01/2013 17:09] – ppk | dcprotocol:hub_client:myinfo [13/01/2013 17:14] – ppk | ||
---|---|---|---|
Line 43: | Line 43: | ||
* 7 - Show IPv4 support when [[dcprotocol: | * 7 - Show IPv4 support when [[dcprotocol: | ||
* 8 - Show IPv6 support when [[dcprotocol: | * 8 - Show IPv6 support when [[dcprotocol: | ||
+ | |||
+ | ==== $MyINFO examples ==== | ||
+ | **$MyINFO $ALL matisskka < | ||
+ | **$MyINFO $ALL damon <++ V: | ||
+ | **$MyINFO $ALL DRUIDASLT < | ||
+ | **$MyINFO $ALL Laller26 <++ V: | ||
+ | **$MyINFO $ALL PPK _@o*<Cz V: | ||
=== Notes === | === Notes === | ||
Common mistake is that magic byte is one byte integer where value 1 is normal, 2 and 3 is away, 4 and 5 is server, 6 and 7 is server away, 8 and 9 is fireball, 10 and 11 is fireball away. Many clients in older versions support it that way, but most of them fix that when extensions using unused bits were introduced. | Common mistake is that magic byte is one byte integer where value 1 is normal, 2 and 3 is away, 4 and 5 is server, 6 and 7 is server away, 8 and 9 is fireball, 10 and 11 is fireball away. Many clients in older versions support it that way, but most of them fix that when extensions using unused bits were introduced. |
dcprotocol/hub_client/myinfo.txt · Last modified: 13/01/2013 17:14 by ppk