The Blacklist Functionality Needs To Be Reworked

RSS News

Syndicated News Service
Hi I've never made a post like this but this is important to me and I don't really see it talked about at all and I'd like to talk about it.

The Blacklist function is, effectively, useless, in a lot of aspects of the game, and I think it needs to be addressed and reworked by the development team.

If another player is harassing you or otherwise being disruptive in places like /say, /shout or /yell, and you can see their messages, blacklisting them is easy, and effective. You click their name in the chat log and add to blacklist. This is working fine.

However, if a player is disruptive in a duty, your options start to become limited.

While in an instanced duty, if a member of your party or alliance is being disruptive, you cannot add them to blacklist UNTIL you exit the duty. When you exit the duty, you then must access your contacts menu, and add to blacklist there.

This means that for the duration of the duty, you must endure the disruptive behavior. You could attempt to vote-kick, but you can only do this if the offending player is on YOUR party. You cannot vote-kick another member in a different alliance.

Additionally, and this is where the Blacklist function loses all effectiveness, is in larger instanced duties such as Diadem, Eureka, and the Bozja Citadel.

While participating in these larger zoned instances, you cannot add another player to your blacklist during the duty, same as above.

Additionally, UNLESS the offending player is added to your alliance or party, the player will NOT appear under your contacts menu.

This means that, when a player experiences harassment from another via /shout, /yell, or /say in an instanced duty, they cannot then exit the duty, and add that player to their blacklist via the Contacts menu, because the player will not be listed.

If you wanted to blacklist the offending player in this instance, the only way to do so are by these steps:

If the player is not on your server, you must world visit to the world they are currently on. Then, you must locate the player in-game, and travel to their current location, and wait until that player says something in a chat log, like /shout or /yell, THEN you may click the players name from the chat log, and add to blacklist.

You cannot add to blacklist from the Search menu.

You cannot add to blacklist from the Friends List menu.

You cannot add to blacklist from the Linkshell menu.

You cannot add to blacklist from the Free Company menu.

You cannot add to blacklist even by STANDING NEXT TO the offending player, and right clicking them.

The ONLY way to blacklist is by clicking their name in a chat log, while NOT in an instanced duty, and adding to blacklist.

Additionally, with the changes to how server names are included in the commands now, you cannot use the slash command /blacklist add Name, because the command will return with an error that the name is not a valid PC name.

I really feel like this needs to be reworked and addressed. Harassment and disruptive behaviors may not happen all of the time, but when they do, it should not be an absolute chore to blacklist the player and move on with my life.

submitted by /u/Cy-Guy
[link] [comments]

Continue reading...
 
Back
Top