Without a true counter, this unit really should be just a T3 unit with vision. It's really that simple. ANY UNIT, which can't be targeted but can target, just sets the stage to be hated in RTS. GPG was wrong. Maybe this unit should have been SP only. @CumCitron, @Ske - Should UEF really have only (3) T4 units? Fine. But UEF deserves something for the subtraction. You can't even build this out of spite now (or is that the only reason remaining?). @DommyMommyDostya - Its no DPS increase as much of the wasted damage is in traversing time arising out of the 4500% targeting speed. Thats my take. @nomander, ty for break out response but your vitriol is surprising! I just wrote a provocative post because it was fun for me to write, and I wanted it to be at least entertaining. I wanted to point out the heavy hand here seen. I meant no personal slight at balance team. I'd support the game if I wasn't poor, and your & others volunteer efforts don't get thanked enough. Yes, I'm a drifter who could disappear into static. Since you replied, for what its worth: "Not an arguement" - I'll try again, there's an "a" and "b" to the argument I meant to convey: a. Slow response units are less fun to use. This was never a Megalith or FB, it was a scalpel. It rewarded micro through timing, punishing that shield breakdown/stray engie. Now it's by comparison, a limp, localized lag laser. b. Because it fires while retargetting, that grass cutting DPS is utterly wasted. So, this appears to me the biggest nerf- its less fun and less effective. Math can't see this. An AI wouldn't either. But only a human is going to be like "WTF, this thing so slow, unresponsive, and wasteful of a preciously short firing time". "Post a replay of transports [shielding]..." - I doubt you've never have seen people do this. Its very ineffective but I didn't make it up, either. Was stupid of me to distract from 1 AoE ->.5 Thats the real nerf here sir. "Yes... second sentence = nonsense" - I meant to sort of restate 1b, the shortened firing time means it fires uselessly as it moves to target. So not only does it not switch between targets quickly (a pivot movement), but it also shoots as it approaches the new target. This happens if you change targets mid firing cycle. So if perhaps, you've qued some targets and one dies (or you retarget), before the laser is finished, the rest of the charge goes into the dirt while the sat moves to the new target. (See minute 2-3 of this replay https://replay.faforever.com/27635804 )..So after wasting the shot, it arrives over the new target on cool down. Now if the DPS was 'shield poping' (you show that its not), might be good use of hover-bomb-esque hold fire micro. 4 & 5. This is still new behavior and therefore adds weight to the total scale of the nerf. But other than that fact, I'm wrong, fair enough & thank you. I read the Charge Cost & Drain rate incorrectly (I see that's the total duration of the firing cycle). Agreed, its a nerf. Just replying to the issues you had with my points. I didn't go into GitHub, or Discord and 100% only read the FAF News Change Log page, and then tried the unit. Again, this balance change was just very significant. Very unlikely to ever use this unit, (164) t3 scouts seem like a better investment.

The problem is right now the only people who know voted what are the people who can look into the log file. In that case dont log anything so noone can see, and not only a specific group of people

G2 - https://replay.faforever.com/27084307 You had 1 t3 sera shield barely covering your scathis and it seemed like it was already damaged. You got dropped 2 ahwassas dealing 8k crash + 1.1k initial bomb damage = 18.2k dmg. Then there's 9900x2=19800 remaining delayed damage on the bombs. Didn't watch czar replay. I think you're more complaining that ahwassa has too high alpha strike than anything related to suiciding them. If you ever talked about bombing and then ctrl k for the wreck to fly under a shield and kill it to let the bomb deal 9900 dmg that would be about the crash damage. For mitigating crash damage: shields absorb crash damage up to 20% of their max hp (ahwassa 8k -> 3800 when going through sera t3 shield, shield bar takes 4200 dmg), and you can spam shields around your target to reduce the chance of the remaining crash damage's splash reaching your target. The reason ahwassa can have the high alpha strike is because it's bad against shield spam since it has a long reload and you need to micro well to fire on time with that reload. It's also a bomber and the most expensive air t4 but also lowest hp. So you should spam T3 shields in a line parallel to the bombing path to stop ahwassas easily.

Yes, others will still see the pings.

@Nomander said in Global Foe Mute, and Forced Mute instead of Ban: Also personally I don't really like the idea of global mutes given out by mods, I prefer some reputation system that shamefully marks people and lets individuals decide if they want to mute them or ban them from their lobbies That's nice, but the modteam does see a lot of utility in having such a function. As do many players, based on the upvotes on the primary post in this thread and how often this feature has been requested of or suggested to us in the past. Toxicity and verbal abuse is something we deal with on a daily basis, and it's the reason for a significant chunk of the bans we hand out every week. Being able to globally mute players would allow us to be more precise with our penalties, without affecting the rest of the player base by removing otherwise active players. If players are otherwise toxic, such as by reclaiming allied units, we can still deal with them by revoking their access to the game, but it would be very valuable to us to have an additional tool in our arsenal (similar to the warning system that was recently added, and now we can finally hand out warnings without having to immediately resort to bans).

@dorset said in Setons Opti Ballancing: Wouldn't it be better for the lowest rank players to battle it out on air and have a slower building air game while the higher ranked players held the front line arc created by the other three positions? It seems like that, but in actual fact- recovering a broken front is MUCH easier than a broken air.

Thank you @Katharsas @Uveso and @Jip so far I've not had any crashes provided I have nothing else open. This probably confirms what Katharsas was saying in that maybe my computer can't handle FAF + x. It's probably time for a new computer just holding on to the nostalgia tower abit longer.

@Printer Had the same thing occur recently. Got notification NVIDA control wasn't installed independently of FAF so- game_13570399.log ice-adapter.log client.log I'll try the UI mod, and reinstalling NVIDA.

@Brutus5000 Just realized what you probably meant was to go to download the latest release .zip file from Git-hub, and extract to a local directory. 100% working thanks.

It is indeed hard to come back from losing navy on a naval map (or the naval portion of a map if you are the "navy" player). Isn't that how it should be, though?