I cannot block more than 10 characters at once or else it says failure. I am so damn sick of all the plat bots. If the developers aren’t smart enough to auto block those things then at least make the block list unlimited. When a child molester goes to prison, do they let another one out to make room?
The block list can contain 50 accounts and the failure message occurs when you try to add more than that.
I just checked my Block List. It currently has around 15 accounts on it. One of those is an actual player I chose to block, the others were plat advertisers. I haven’t had to clear out my Block List for months. Maybe some servers or regions get more of these adverts but I haven’t seen one on the server cluster I play on for a couple of months now.
Also, the Block List having a maximum number of accounts you can block is not a bug, it’s a design decision you don’t like. Bug Report is the wrong place for it.
This should be general discussion rather than bug as it is working as intended and is in fact larger than 10 people.
The reason why some people may think the block list has a 10 account limit is because if you view your block list in-game, it will only display the 10 accounts you blocked the longest time ago, i.e. it’s in reverse datal order. However, if you unblock any of the accounts in that top 10, the list will re-populate with accounts you more recently blocked.
If you’re playing on PC, you can do this a lot easier with the BattleNet Launcher. From the blue swirly icon top-left, choose Settings, then Friends & Chat and click on View Block List (as shown below) and you’ll get a scrollable list showing all blocked the accounts…
However, this still doesn’t change the fact that the block list having a 50 account limit is not a bug.
1 Like
Ah nice! I was curious how you got the bigger list. Good to know!
Thank you for the info. I was looking at the list in game, and can only see 10 on any of my characters. And yes I agree I did post this in the incorrect forum, but I thought I could only block 10 when others say 50. So I thought it was bugged for me. Thanks for the explanation.