Seriously it's been a year and we still can't do that? It's the most annoying thing in the game!
Printable View
Seriously it's been a year and we still can't do that? It's the most annoying thing in the game!
Devil's Advocate: Not being able to talk to those outside of the dungeon keeps you focused on the task at hand. It keeps players focused and moving forward through the dungeon rather than trying to chat/fight/run at the same time. In addition, the sound notifications some players may have could confuse them thinking the sound was a trigger caused by a boss attack or something in game.
My solution: Make it optional to not be bothered while you're in a duty. Those who start falling behind from not paying attention can be vote kicked. Problem with this, like anything, it can be abused. It's reliant on player maturity and discretion to use the tool responsibly.
People can already talk outside of dungeons via Linkshells, so what you're saying doesn't really apply. I don't see people "falling behind" from being too busy chatting in their Linkshells.
And your solution is also pointless, as there is already the "Busy" mode, which makes people unable to whisper you. That's really all that would be "required" here.
As such, I completely agree that it's about time they give us the ability to whisper normally during duty.
Now that you mention it.. you can also talk in FC chat as well. (I've been on a break for a few months and just came back this week so my mind isn't full wrapped around the game again just yet.) This makes me think that the way /tell communications function with instanced servers (Dungeons/Primals/Raid/Etc.) could be the issue. They perhaps didn't build the required bridge code for personal messages to be sent to the characters current state (server wise). So while they're not in a home world zone the /tells can't even reach the players. Free Company and Linkshell's still work because of how they're designed to spread to all characters in the FC or LS.
Just my $.02~
I've already seen some pretty vile stuff in Alliance chats, not sure I'd want somebody within the dungeon party/raid alliance being able to privately harass somebody, regardless of whether or not it gets reported.
This is for players on the same servers to keep communicating after one of them enters a duty, not for random people from duty finder to keep harassing you after the run is over. If they're from your server they could already do that after the run anyway.
If people harass others, they should be reported and dealt with and / or blacklisted. Plenty of people being jerks is not a good reason for our tools of communication to remain crippled.
Take a moment to think about how many players from different servers connect to one instance, now think about multiples instances that contain those players from different servers, now think about a front line alliance of 3 alliances connected to one instances and all those instances of frontlines/duty finder going on at the exact same time. Now if everyone was able to send tells back to their home servers. Do the math. That would over stress the instance servers ten fold. Servers would go down
I doubt /tells are that much harder on the systems than the FC and linkshell chat that can already go on. I suspect that it's due to a different problem:
/tell "John Doe" Hi
would be confusing if there's both a John Doe there in the dungeon party with you and also a different John Doe back on your home server. No matter which one they implemented, there would be people trying to use it to talk to the other John Doe.
Then there's those of us who are too focused / busy to even chat with the party unless it's something urgent, much less deal with LS FC or /tell chatter...
Two words: Gil Sellers. Do you really want to be spammed with those kind of tells while in a dungeon?
I remember someone said a dungeon can have 2 chracters with same name while they come from 2 different servers,
therefore I think current /tell does not support dungeon because "player name" is not an unique identity in the dungeon.
But that could cause a lot of confusion if you try using the /tell to talk to a party member in the dungeon with you. (And I'm sure plenty of people would try to use it that way.) If someone on your native server happens to have the same name, they'd get the message you'd intended to go to someone else. It would just be too error-prone to be a good idea.
The off chance that somebody would try to whisper somebody from an entirely different server in the same duty as themselves, who just so happens to have the same name as some other person on the server is enough for you to suggest that it's a good thing that we're unable to whisper during duty...?
It's wholly unique to SE games then, because other games have managed to figure it out. I cannot think of one other game that blocks you from communications just because you jumped in a dungeon, and two of those I know for certain have had cross-server for years. They invented it.
It's funny how this a complete non-issue for basically every other MMO with cross-server grouping.
Moreover, you can still chat with your own linkshells and free companies, so you're still connected to a server in charge of handling communication. I don't know if this is the same server responsible for handling chat messages in between players, probably not, but I seriously doubt it's such an insurmountable technical challenge to have these messages be properly passed off to the right server. As I said, basically every other MMO does this without issue.