It's been a long requested feature. If we are able to work on the Chat Coding, I'd love to see it happen.
The "HideInBattleStatus" feature was able to happen because it was some backend tweaking. This was something that came about because of Streamers being sync-dropped from others who aren't on their friendlist, so that would be another good feature to see someday <3.
The only time I've heard of something like that was something Overwatch did. You could exclude up to 3 players from future games, and would have to rotate out names with new ones if you had issues later on. Matchmakers are complex functions that draw from what is available. Making a system with a myriad of individual exclusions is very complex as a player locking out another player could delay something for many other players as they each have their own sets of interwoven exclusions.
In general, our Matchmaker pulls from what is available. If you don't queue for a few minutes after a match, there is a strong likelihood that you may not encounter the player again. Still, if you do, having them Blacklisted would auto-block them on game start so that you wouldn't see any messages from the player.
If you'd like to learn more about how our Matchmaker works, you can check out this video:
We have wanted to do an update to our chat system for some time, but other priorities continue to take precedent. At the moment, you may not be able to prevent unwanted messages, but you can make a CS Ticket to make sure they are Actioned so that other players will not have to suffer in the future.
None of your Tickets are on-hold. Everything you have submitted on the Elijah2159 account is closed out. The most recent Ticket was responded to and closed within a day.
If you have a second account you submitted the Ticket on, please let me know. You can put the Ticket# in the post as only CS or WG would be able to access the Ticket.
It stops them from continuing to message you. If the messages were bad, please make a CS Ticket so we can action it.
CS Ticket Link: https://na.wargaming.net/support/en/products/wows/help/31336/31337/31345/
If you "Blacklist" a player, they will not be able to communicate with you in game or in port. Blacklist will auto-block the player if you encounter them in future matches, as well.
I had ground the German and UK DD lines to Tier 10. A content creator known as Destroyer_Kuro had a ranked video showing the Smoke/Hydro combo on the Z-52 and I was intrigued enough to play it maybe 3+ years ago. UK DDs had Hydro as well, so I played that line up to 10 as well and then stopped.
Going back to DD was because I was challenged that French DDs (no smoke, non-amazing AA) were unplayable because of CVs, though. So yes, that reasoning for returning to DDs is correct. After that is was Japanese DDs are unplayable, and then something else was unplayable. After a while, I caught the DD bug and began to play them more regularly as I enjoyed close-range fighting (less shell float) and the decision-based play of the ship type.
Very interesting post! Thanks for sharing <3
Commanders!
Over the previous weekend, the Twitch Mission for the KotS Commander was not correctly issuing the in-game mission.
We are working on resolving this issue to make the mission available to players as soon as possible.
-
Update #1: We have a solution and are finalizing the distribution method. We'll provide an update soon!
Our EULA forbids insults and harassment. They are not allowed and are not to be tolerated.
-
Game Mechanics are not an excuse for in-game harassment or insults to other players whom are playing the game.
If you experience either in-game harassment or insults from other players, make a CS Ticket so they can be Actioned.
CS Ticket Link: https://na.wargaming.net/support/en/products/wows/help/31336/31337/31345/
Hello, Commanders!
Public Test Server Version 12.4 needs your help. Please leave feedback below!
Patch notes here: https://worldofwarships.com/en/news/public-test/public-test-124/
---
Any bugs you encounter in the PTS can be reported in the Bug Report thread!
Thank you!
Captains!
If you encounter any bugs or technical issues during the Public Test 12.4 pt 2, feel free to report it in this thread.
Please follow this template for submitting bugs:
Description: Short description of an issue with required details.
Example: Spotting-aircraft doesn't work on Iowa battleship
How to Reproduce: Exact steps need to be made to reproduce the issue
Example: Take Iowa battleship with spotting-aircraft equipped. Go in battle. Try to launch spotting-aircraft
Result: What's the result of the issue.
Example: After pressing spotting-aircraft activating button you can hear an aircraft sound but nothing happens, the aircraft stands still.
Thank you!
We don't allow it. If you encounter this behavior, please make a CS ticket and it will be actioned.
For now there's a work-around which is to hold Control to get the mouse-pointer, then ping somewhere on the minimap. This frees up the issue.
We are testing a fix already but don't have a definite ETA on delivery yet.
It'll be looked into when folks get in on Monday as it's been reported widely. In the interim, you can make a CS Ticket and describe the situation. If you selected the wrong commander on accident, CS should be able to swap them out.
devtrackers.gg
