Blacklisting Suggestion

[Lokier]

I'm here at the behest of a GM after having to report a player from a cross-world duty finder. I'm not going to into detail about it here, as it should be resolved by the GMs.

TDRL:
- Right-click blacklist should be reinstated.
- Blacklisting cross-world players should be allowed by using their world name (as it is with whispering said players.)
- Blacklisting players should mean you do not get grouped with them for 24-hours / they can't join groups you're in. (if permanently is too severe.)
-------
Short of just reporting players who are cross-world I can't blacklist them, and even then black listing them does not stop me getting groups with them. Usually, I would see a bad player maybe once, and then never again due to the large community, but I keep seeing this one player again, and again, and again... doing the same thing.

I suggest blacklisting someone means you do not group with them again, even if it means this player can't group with you for just 24-hours. If they continue to show up, doing the same thing, you can just blacklist them again for another 24-hours, and so on and so forth.
I also wish to press the matter that blacklisting, via right-clicking, was removed (I believe) sometime last year, I would like this reinstated, so that if an AFKer is not speaking I've still some way of blacklisting them.

Right now the only way around this is the command /blist add <t> Which is all fair and good if you know this command.

(I'm not open to debating on whether duty finder "comes as is" due to the nature of the community, I just don't think bad players should be rewarded for being purposefully bad players. Especially when Mentor roulette does not allow for friend-only party dynamics.)

[AC9Breaker]

I also 2nd this suggestion. I was pretty upset to find right click black listing was removed. I would also like to add that our black list limit be increased. I've quickly reach the limit in black list all "ads" that I find bothersome on Party Finder.

I also want to say thank you for the /blist add <t> command. It had not occured to me to use this method.

[Rongway]

There are technical considerations preventing your blist from being a complete do-not-interact-at-all list.

The blist is stored in a puzzlingly obtuse way. For whatever reason, the blist is partially stored on the server and partially stored on the client. If you blist someone on one machine, you will see their name and their homeworld in your blist. If you log in to the same character on a different machine, you will see people from your homeworld as having the home world "Unknown" and people from other worlds will be homeless and named "(Unable to Retrieve)".

Forget adding blist functionality for now; first they need to pick a better way to store it properly. Then we can talk about what can and can't be done with it.

Unfortunately, this is basically the state of many of the systems in the game. Yeah they need more feature support but really a lot of the systems need their underlying storage and access designs fixed before we can even consider features.