/who all [some words NEVER work, why?]

[HeallunRumblebelly]

/who chest does not return chest. pls rename.

[radditsu]

Yeah you gotta /who all 60 monk that dude. So painful.

[Sarajo]

I met Portasaurus one day in the sewers, where she introduced me to several rat meat recipes. Since then I've always tried to get in touch for all rat-related news & gossip, but was sad that /who all port never returned a result. I thought she'd quit.
There's another few (druids, naturally) whose names start with "Port", but you're right - /who all port gets me nothing.
I wonder if we have to use underscores or wildcards or something.

[Byrjun]

Originally Posted by Byrjun [You must be logged in to view images. Log in or Register.]

I assume it has something to do with hitting search results in the database (outside of players).

For example, a Bazu was a type of mob in GoD so there's a lot of items that start with "Bazu x."

Seems like if you search for names that are items/NPCs/places in the game, they won't return with the player name.

[Clark]

Really sucks for pvp; not really a big deal on pve.

[Rogean]

This happens because the client is trying to figure out exactly what you're searching for by comparing it to race or guild names, and then sending those ID's to the server instead of the string.

/who all eath.. there are a lot of race names with earth in the name. (This includes NPC Races).

Not a whole lot we can do about this, other than making the server reject all those player names to begin with... which would block a lot of random things.

[odiecat99]

/who all "unreliable comes up...
quotes help mang

[Peekae]

I remember this being a problem way back when with the guild "Poison"

[Buefurd]

It was definitely like this on live back in '99 as well.

[Lune]

/who is the gayest of them all

On prexus that came up with a bard named Offkey