Nice contribution however, it shouldn't be done as a string packet effect, it needs to be a statusflag, that way all surrounding clients and yourself will see it anyhow, without any need to send repeat string packets.
e.g. TQ's statuseffect.ini
Code:
34 gamemain NULL
35 gameassistant NULL
36 gamemonth NULL
37 gameweek NULL
38 gamefighter NULL
39 gamewarrior NULL
40 gamebow NULL
41 gamewater NULL
42 gamefire NULL
43 gamegulp NULL
Statusflag is a BitField, I can't be bothered explaining what that means so you can Google it to find out how it works and how to set the bitflag correctly.