Jump to content

_rayhan_

Member
  • Content Сount

    5
  • Joined

  • Last visited

  • Battles

    5100
  • Clan

    [BNS]

Reputation Activity

  1. Cool
    _rayhan_ got a reaction from _TAMAL_ in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Well, that is exactly my point. I am having fun with our current game play. So, why the heck they are ruining it with these changes that they are calling BALANCING.
  2. Cool
    _rayhan_ reacted to Moggytwo in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    This is not a storm in a teacup.  This is reverting what is one of the best changes they have ever made to the game. 
    It's not that we don't know how to play around the old mechanics - we had to put up with it for ages.  It's that the new mechanics introduced in 0.7.9 enabled much more dynamic play and a clear knowledge of what would happen every time you broke LOS.
    With the reversion, you now have to go back to guessing when your bloom time is up.  You want to get out and retreat right now, but is your bloom time still up?  Pop out only to find it had a couple of seconds left and you get blapped for half your health and that can be the difference between winning and losing the game.
    Have a look at the polls on the EU and NA forums - they both have 1200-1300 votes with a 94% (!) response of keep the current mechanics.  Has there ever been this much consensus on an issue?
    I honestly am not sure how a team decided that reverting this change was a good idea.  What are they trying to achieve exactly?  Did anyone ever once actually complain about this change?
  3. Cool
    _rayhan_ reacted to Max_Battle in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Yeah what about UK DD?
    Short smoke to break LoS is what they do.
  4. Cool
    _rayhan_ reacted to Grygus_Triss in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    So... what about smoke, does it work the same way. That is, if you smoke up, break line of sight, then glide out of smoke, will you still be at Max detection range? It is often a tactic of DDs to use smoke to break los, then run, rather than staying in smoke, especially RN DDs.
    Other than that. Don’t like this change. How dare they insult us by calling a a “bug fix”.
  5. Cool
    _rayhan_ reacted to 9mm1n in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Someone mad a presentation of Before (""bugged"") and After ("fixed") version of the bloom time debuff mechanics. The "bugged" version is when the video starts and you can see the new mechanism starting 0:25 of the video
    Hope this helps.
     
  6. Cool
    _rayhan_ reacted to _TAMAL_ in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    I seem to have misunderstood what you said before. I completely agree. We were in a good state with the game. Right now the game needs more new Maps and missing ship trees along with balancing of the existing ones. Not the BS that is being planned for release...
    Hell, they are not even releasing Alaska
  7. Cool
    _rayhan_ reacted to PGM991 in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    I see... normally when I'm firing main gun, detection range will expand, but shrink back immediately if there's no enemy spot me.
    after this fix, my detection range will remain expand for 20 sec even there's no one spotting me huh.. 
    it seem trivial but it may cause huge impact in some way...
  8. Cool
    _rayhan_ reacted to _TAMAL_ in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    And unironically, the game was perfectly fine at that state, with some minor imbalances here and there... very few people built for countering carriers and most ships were build around surface combat(the way this game should be played in the first place). Carriers matches were rare(and those matches were typically one sided with one or both team basically waiting for the match to end asap). Clan Battles didn't have CV in them and large portion of the playerbase was happy. The game was perfectly fine.
  9. Cool
    _rayhan_ got a reaction from _TAMAL_ in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Well, that is exactly my point. I am having fun with our current game play. So, why the heck they are ruining it with these changes that they are calling BALANCING.
  10. Cool
    _rayhan_ reacted to Thyaliad in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Urgh.
    This has been a feature that almost all players knew about since god knows when.
    This means either WG is trying to lie to the players by passing off balance changes as a bug fix, or they don't even play their own game. Not sure which is worse. And people wonder why I have little faith in WG.
    And this a very big change. For example, you can't fire in smoke and stop firing just before the smoke runs out to leave undetected. You now have to give yourself a 20s window.
  11. Cool
    _rayhan_ reacted to 9mm1n in It's not a feature, it's a bug. [concealment change 0.8.0] [Poll added]   
    Yes, you read the title right. No, I didn't get the software developers meme wrong. Yes, doomsday is upon us.
     
    In the impending patch wargaming is going to fix a "current feature" as a "bug"; or rather, fixes a "bug" to a feature. I'm not sure
    "How?" you may ask. Well, here's what Saint Petersburg is gracing us with upon the update, closing into us in 16 hours or so
      Source: 0.8.0 Patch note: https://worldofwarships.asia/en/news/game-updates/update-080-takeoff/  scroll down to second bullet point of section "Other Changes and Improvements
     
    In other words, breaking LoS in this patch after firing your guns WILLNOT reset your detection range from full debuff (as in your maximum firing range) to your base detection. No matter what happens, any ship will have the full 20 second concealment penalty for firing your guns, even if you break visual contact by, for example, sailing behind an island, popping a smoke or killing the enemyships with in your concealment range. 
     
    As demonstrated in this video, the "bugged" mechanics (0:00) and "fixed" mechanics (starting 0:25) has dramatically different behavior to the player's detection area once  visual contact is broken.
     
    This is going to massively, and negatively, impact every single ship that has a maingun, especially for lightcruisers and destroyers, whose survivability relies on expert mastery of landscape and LoS control, just as the community grow familiar to using fire-concealment with landscape as a combo since a few patches ago.
     
    Obviously, I'm not too impressed by this "news". What are your thoughts on the subject matter? please vote and share your opinion 
    Update
    Sub_Octavian, our old freind & WG spokesperson, has just posted a official explanation to the current situation. Because it's quite a lengthy post I think it's better to simply link it here.
    Thread in question: 
    tl:dr
    the "bug" was fixed out of necessity from the perspective of software engineering;
    WG staunchly believed that falt-out 20 second debuff is more intuitive for players
    WG is considering implementation of the "bugged" as an actual feature in 0.8.2 or 0.8.3
     
     
    Edit: Poll added as EU & NA server counterparts
    Edit: WG offical statements on the subject matter
    Please read the patch notes and watch the video above for intuitive understanding of the current fiasco
     
     
×