StarCraft Patch 1.15

[rabbit]

It could be 0x01 | 0x04 | 0x08 | 0x20 you know.

[Mystical]

Oh wow they disabled chat in brood war usa channels?

[Hdx]

ohy, mental fart
~Hdx

[Barabajagal]

Use force join to join the Warez channel. That channel's silent.

[brew]

warez has flags 0x13.
blizzard tech support has 0x11. (@ uswest it has 0x03)
just for comparison, open tech support has 0x01.
need I say more? Jeez. 0x10 is OBVIOUSLY the silent flag. Whoever made the original channel flags specifications obviously screwed up

[brew]

It could be 0x01 | 0x04 | 0x08 | 0x20 you know.

I know, my point is that 0x01 | 0x04 | 0x08 | 0x20 = 0x33, but if the new flag(s) were 0x08 and 0x02 it would just 0x35, wouldn't it? :p So it must have had flags | 0x10 (which is silent.)

[Spht]

Use force join to join the Warez channel. That channel's silent.

And force talk to speak there.  And force speed to get out of there if someone catches you.  And force grip so no one knows you were ever there

[rabbit]

And Jedi Mind Trick to make Blizzard give you an @Blizzard account.   ...............Wait....

[Sorc.Polgara]

ROFL.  The last two posts just made my day.  Thanks.

[Spht]

warez has flags 0x13.
blizzard tech support has 0x11. (@ uswest it has 0x03)
just for comparison, open tech support has 0x01.
need I say more? Jeez. 0x10 is OBVIOUSLY the silent flag. Whoever made the original channel flags specifications obviously screwed up

I'm 100% sure 0x10 does not flag a channel as silent.

[brew]

warez has flags 0x13.
blizzard tech support has 0x11. (@ uswest it has 0x03)
just for comparison, open tech support has 0x01.
need I say more? Jeez. 0x10 is OBVIOUSLY the silent flag. Whoever made the original channel flags specifications obviously screwed up

I'm 100% sure 0x10 does not flag a channel as silent.

How are you sure though? and how else could you explain the flag update to public channels on asia?
EDIT** jeez, i just proved myself wrong. 0x03 | x = 0x11, x must obviously be 0x08. This also explains the Void's flags of 0x09 But... if 0x10 is indeed the system channel flag then how does the 0x43 work out?

[Spht]

warez has flags 0x13.
blizzard tech support has 0x11. (@ uswest it has 0x03)
just for comparison, open tech support has 0x01.
need I say more? Jeez. 0x10 is OBVIOUSLY the silent flag. Whoever made the original channel flags specifications obviously screwed up

I'm 100% sure 0x10 does not flag a channel as silent.

How are you sure though? and how else could you explain the flag update to public channels on asia?

I had it as an edit, but I'll put it in a new reply:

I just joined the two channels you mentioned in your previous post, and on Asia:

[12:38:13] Joining moderated silent product-specific channel Brood War USA-1.

Which is a combination of 0x1 (public) 0x2 (moderated) 0x8 (silent) 0x20 (product-specific) = 0x2b (and confirmed this is the value sent to me via packet log)

The Brood War channels on USEast are still normal: 0x1 (public) 0x20 (product-specific) = 0x21 (confirmed via packet log)

And for the record, warez is 0x1 (public) 0x4 (restricted) 0x8 (silent) = 0xd (confirmed via packet log)

0x10 (system) did not show up in any of these channels.  So what's the confusion?

[Spht]

So what's the confusion?

I see now.  In your post, you said the asia channel had flags 0x44 and east had 0x33.  44 = 0x2b, 33 = 0x21.  See what you did wrong?

[brew]

Omg, thanks spht! It turns out it was a problem with my code. (i didn't hex() the flags on accident) And it didnt help that I was trying to figure out the flags in decimal.. jeez

So what about that packet??? anyone know anything about it??

[Barabajagal]

About 4E? Maybe if you gave some info about how you found it?