Jump to content

Search the Community

Showing results for tags 'report'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • World of Warships - Asia Language Based Communities
    • English Speaking Community
    • 繁體中文討論區
    • 日本語コミュニティ
    • 한국어 커뮤니티
  • Mod Section
    • Player Modifications
  • Public Test Forums
    • English Speaking Community
    • 繁體中文討論區
    • 日本語コミュニティ
  • Locked Threads
    • Locked Threads

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Drag Interests

Found 14 results

  1. Gummilicious

    200%? became 100%? Wargamig solve pls

    Hi Mods, please re confirm is it 100% first win or 200% first win of the day (June 1-5 Saviour of Dunkirk) Link stating is 200% : https://worldofwarships.asia/en/news/common/june-missions-2018/ In-game: 100% Please double check what you post on website and put in-game
  2. karrablaster123

    What's your karma?

    I know it is a horrible statistic but just curious. I am at 49 atm.
  3. XV_104

    Ban this guy pls

    Without any conflict before, this guy suddenly said this. *content removed* Naming and shaming. Warning issued. Locked and archived. ~Chappo
  4. New_Horizontal

    Why people so salty to me

    After I had a several lost streak, I decided to run my Mahan in Neighbor map, T8 games and enemy had Lo yang and Sims I went C to contest cap but can't fight due to Lo yang + Sims went to C as well so I decided to retreat. But not before MK hit me and my HP reduced to one third of total HP. So, I spammed torpedoes to smoke which Sims and Lo yang sit it and I got Sims and I ran away to B, left Bismarck to die in process because my smoke still cool down. and can't cover NC as well After that I saw Sharnhorst and Nagato tried to rush B so I spammed torp again and hit Scharnhorse a couple of torps. then I have to run away due to team losing very hard but lead in cap points. Still spam torpedoes to slow them down but my remaining teammates decide to fight and got deleted one by one. yet I still spam torps and hit Scharnhorst yes I ran away from team and wait till time ran out so we win in cap point. came back to port and I found that I got reported 6 times for doing the right thing to win the game??? such a LUL I don't know what I did wrong? for not contest a cap C so I surely dead?, not smoking up team while I have to run for life?, for not firing at enemy so I can survive and let team win by cap points?, or for spamming torps and those BBabies ate every salvo? Just not understand people logic ...
  5. Hi all, I was playing a game in Konigsberg and happened to be in the perfect place to launch to salvos at a scharnhost less than 6km away. Now as there was a Belfast, by the player [redacted] whom was on the port of my ship engaging Scharnhorst as well. However, the torpedos were not supposed to hit her had she continued on her course UNLESS SHE STEERED TO PORT AS WELL. Now, because I was going to get first kill if all 4 torpedoes hit Scharnhorst, and she was in low health (for some reason she took on Scharnhorst herself, she deliberately blocked the path of two torpedoes, and I got team killer status. This is not the first time it has happened to me, stupid idiots either deliberately or too dumb, to walk into torpedoes by friendly ships. I am sick of this WOWS, can someone: 1) Tell me how to report my situation to have my teamkiller status removed 2) Report that player to an actual admin instead of the stupid useless automated complaint system. Attached screenshot of post-battle screen [Redacted] Naming and shaming. Post edited, user warned. ~Syanda
  6. So I just had good game last night getting a solo warrior. After the match I quickly went to profile to see haw many "good boy" points I get and only to be amazed my karma decreased by 4 in real-time. WG should made some filters to prevent these salty players to make baseless reports even if this is not my first time getting one.
  7. key233

    About report TKer

    sorry for didn't find where to report it... I wanna attach my rp but it's more than 1M... pls tell me what can I do
  8. Junchan

    Report team

    i can reported Plays Poorly is ok as case ??
  9. Storm_Raiser

    Too many AFKers

    I'm seeing more and more ships sitting idle during battles so I've started reporting them ... as we all know the in-game reporting tool lacks an option for AFKers so I've been reporting them as both "Bot" and "Plays poorly" but now I'm seeing so many that this is no longer possible most days. My question is: which of the report options SHOULD I be using for AFKers and is it even worth bothering to do so or is the IN-game function like in many other games where it is just a placebo that sends our complaints off into cyberspace never to be seen by an actual human being or acted upon?
  10. Issue: When running the 0.5.0.3 live server client using the Chinese locale, German ship names do not display correctly if there is an umlaut within the name. Screenshots: Occurrences: All casesTested: ReproduceableSeverity: Low. Although it looks rather ugly, it does not impact gameplay itself.Details: This is a problem with your choice of typeface. Consider changing the system fonts so that Roman letters use the same typeface as the English client, while keeping the typefaces for Chinese, Hiragana, Katakana and Thai the same.
  11. 1. Description The game client uses an excessive amount of GPU resources while displaying the home port screen, to the point where the GPU overheats and reaches extremely high temperatures. In fact, the port screen uses more GPU resources than actual in-game battles; the GPU fan speed and temperatures happen to be markedly lower whilst in-battle compared to at the port screen. Currently it is winter in Australia, however during the summertime this may potentially cause housefires if players leave the game running for long time durations, idle at the home port screen. In addition, I'd presume that players with high-end nVidia cards would have a much more severe circumstance compared to mine, and this is also likely to be the case for people who have much more poorly ventilated machines compared to mine. 2. Reproduction steps Run the game, leave the game sitting idle within the home port screen for long durations of time, record GPU temperatures. 3. Result The following temperature chart shows the changes in GPU temperature whilst in-battle, for comparison purposes. Units are in degrees Celsius. The battle begins immediately after the sharp dip from 60 degrees Celsius (at the time when the game was minimised and the Windows desktop was displayed), and reaches an average temperature of 81 degrees Celsius during the battle. The following temperature chart shows the changes in GPU temperature whilst left idle in the home port screen. Units are in degrees Celsius. The time period spent within the port screen is immediately after the second dip; for comparison purposes, the period directly preceding the dip is the in-battle temperature shown earlier. Whilst at the port screen, the temperature reached a maximum value of 86 degrees Celsius before I ALT+TAB-ed to desktop to take a screenshot of the temperature reading. Had I not done so, the temperature would have continued to rise, given that the upward parabolic curve has yet to fully plateau. 4. Expected result The port screen should not overutilise GPU resources, to the point where the GPU generates more heat at the port screen compared to actual battles. Given that players are often likely to leave the game running idle whilst at the port screen (e.g. looking for food/drinks), the GPU utilisation should be at least the same as a battle, if not less. 5. Technical details While testing the temperatures as described above, the following graphics settings were used: Dxdiag: http://pastebin.com/P2qnR9S0 Addendum: My computer has removable dust filters attached to the fans, and I clean them every two months.
  12. 1. DescriptionThe Chinese-language locale of the 0.4.0 public OBT game client displays incorrect units of time measurement at the battle results screen. 2. Reproduction steps Finish a battle, either as win/lose/draw, and click on the third details tab (on the far right side). This bug is reproducible, and occurs every single time. 3. ResultFor the time format "XX minutes YY seconds", the game incorrectly displays this as "XX 刁E▮▮ YY", instead of the correct format "XX分YY秒". Refer to the following screenshot: When paired with this separate bug, the results screen looks like this: 4. Expected result The battle results screen should display the time format as "XX分YY秒", where XX is the number of minutes, and YY is the number of seconds. 5. Technical details Client was run on Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1, English system language. Dxdiag: http://pastebin.com/P2qnR9S0
  13. 1. Description When the Chinese locale of the public OBT game client is installed, sans serif Chinese font should be used for all Chinese-language text, at all times. However, purely at random, incorrect serif Chinese fonts are displayed. Theoretically, serif fonts should never be displayed by the game client, which means that the program is having difficulty loading the correct sans serif fonts, and as a result it is resorting to a default fallback font. This is likely a memory access problem. 2. Reproduction steps None, these errors occur at random. Sometimes they happen, sometimes they don't, however the errors appear very frequently. There is no fixed series of steps which guarantee a correlation that the error will occur. 3. Result The following screenshots depict the erroneous serif fonts used to display Chinese text: In the above image, "等待玩家" (waiting for players), "一般戰鬥" (standard battle), and the text at the right hand side are written in a non-antialiased serif font. Notice the "blur" effects on the right hand side? That looks absolutely terrible with serif fonts. In this image, the description text on the left hand side explaining the benefits of premium ships is written in serif font with no anti-aliasing. In this image, the ship class names (below the numbers), description for "random battles" (at the bottom, above the button), and "您的艦艇" (your vessel) is written in serif font, with no anti-aliasing. Furthermore, within the line "在您範圍內的玩家" (players within your range), the text is correctly displayed with anti-aliased sans serif font, with the exception of "內", which is written in anti-aliased serif font. The ship type ("主力艦", battleship), the words for "tier" and "ship experience" in the upper right corner are written using serif font without anti-aliasing. Furthermore, the display of premium days remaining, server (伺服器), players (玩家), remaining time for mission updates (更新時間), buying gold, exchanging credits, and converting free XP are also in serif font without anti-aliasing. Also pay attention to the mouse hover tooltip below the "join a division" area, which also has the same font problem. 4. Expected result The following screenshots display what the UI should appear like (i.e. correct sans serif font usage): All of the following are displayed in the correct anti-aliased sans serif font: The ship type ("主力艦", battleship), the words for "tier" and "ship experience" in the upper right corner; display of premium days remaining, server (伺服器), players (玩家), remaining time for mission updates (更新時間), buying gold, exchanging credits, and converting free XP. All text is displayed in the correct anti-aliased sans serif font, and the "blurring" effect on the right hand side does not look stupid and ugly, because it correctly displays behind the text. All text is displayed in the correct anti-aliased sans serif font. The line "在您範圍內的玩家" (players within your range) has a uniform font with no odd characters which stand out. 5. Technical details These screenshots were taken using the public OBT WoWS game client, version 0.4.0, on the Asia server, using the Chinese-language locale. Client was run on Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1, English system language, Japanese locale. Dxdiag: http://pastebin.com/P2qnR9S0
  14. Shironeko085

    This User is Teamkiller

    [Removed] Naming And Shaming. Content Removed. User Warned. ~Madiba
×