Character with name ######

[ "'s head" <-- forgot to remove, its from pvp script ]

Confirmed on a 2013-07 client.

I have yet to check whether it is a clientside problem, but I noticed some (unrelated) issues on the 'announce' script command. I'll mark this as confirmed for the time being.

I've experienced this problem some years ago (e.g. when saying something like Y is the #2!), I think it is a client problem -- I've never really investigated it though.

Here's my findings:

(1) It currently isn't possible to combine bc_blue or bc_woe with bc_map, bc_area or bc_self. This is why, when you use a map announcement (bc_map), it'll use a yellow (bc_yellow) message instead of a blue (bc_blue) one.
(2) Due to a client limitation, it isn't possible to use the '#' character in a bc_yellow message unless it's preceded by at least one ':' character (this - according to my speculation - is probably related to the fact that official servers always show yellow (GM) announcements in the format 'GM Name: Message'.)


- Point (1) will be fixed in my next commit.
- Point (2) is a clientside issue and, as such, it can't be fixed. You can work around it by using bc_blue or bc_woe (as you were already doing), after I commit the fix for part (1). Another possible workaround is to ensure the presence of a ':' character in any part of the message, before any '#' you want to display.

This means:
- After I commit the fix, your example script will work without any problem, displaying the message in blue.
- If you want the message in yellow instead, you can use a line such as ' announce "PvP: Your name is "+ strcharinfo(0) +"!"; '. That will ensure the '#' characters will not be hidden.

Part (1) fixed in [url="https://github.com/HerculesWS/Hercules/commit/eb10f355f7e228b59011326a7f84da2e593affea"]https://github.com/HerculesWS/Hercules/commit/eb10f355f7e228b59011326a7f84da2e593affea[/url]