almost 4 years ago - Kafka - Direct link

Hey, we noticed this and have already fixed it for the next update, version 5.1.

Unfortunately, it requires a client update so it’s not something we could fix on the fly for this week’s event.

Sorry about this, I know it’s inconvenient.

almost 4 years ago - Kafka - Direct link

Yes but changes are still waiting to be verified so I don’t want to post about too much until it’s confirmed.

almost 4 years ago - Kafka - Direct link

The Weapon filter is a programming task not a design task so there’s no overlap.

almost 4 years ago - Kafka - Direct link

It means we don’t consider a bug fixed until QA has tested the fix and has confirmed it is indeed working as intended. I try not to announce something is fixed in the next update unless I know for sure it is actually fixed.

I tested the Weapon filter myself so I could reply to this thread which is why I could post about it.