No error message on sent /tell

I've noticed in this game that you could send a tell to dfdfs dsfsd and it will go though with out an error message saying this person may be offline or is changing areas.

Another example.
I've tried contacting a few friends and never get that error message nor do I get a respond from them.

There could just be afk, but all the time?

It would be easy for me to know if the tell is getting though or is not because persion is of line or the name misspell.

Platform: Windows Vista 64bit
ISP: Virgin Media
Type of Internet Connection: Cable
Internet Connection Speed: 50 MB/s
Date & Time: All the time and every day
Frequency: All the time and every day
Character Name: Alexis Jade
Race: Lalafell
World: Selbina ( I can't believe its not Selbina Butter)
Class/Skill Rank: All
Physical Level: All
Area and Coordinates: All
Party or Solo: All
NPC Name: N/A
Monster Name: N/A
In-Game Time: N/A
Steps:
1. Send /tell to friends
2. try again
3. and again
4. no respond from any of them
5. send a random tell to a name that would get rejected ie fjdf dfds
<*Add more steps if necessary.>

Don't think this is a bug. More like a missing feature.

Quote:

---

Originally Posted by Coldfire

Don't think this is a bug. More like a missing feature.

---

As described, it is a bug, or filters set preventing the messages from showing. Normal behavior (I just tested) is that if a recipient does not exist, you see:

>> blahblah blahblah: Wut
Tell recipient could not be located. Your message was not received.
>> wutwutwut wutwut: wut
Tell recipient could not be located. Your message was not received.

I guess it's the filter settings then. 'Cause I also don't get that error message and I played around with those settings :/

I have been playing around with my 4 chat windows recently and there are some system messages that will only appear in the first chat window (the default window). Even if the chat filters in the other 3 are set to show everything, certain system messages still do not appear. This may be your problem.

Yes it was one of the filters that was hiding the error message