If we really wanted to, we could add an option e.g. for game host to not save a replay. We'd have to do some coding (switch to new replay server, add rabbitmq to it, add some simple "don't record this replay" logic between lobby server and replay server), but if there is a lot of interest in it, why not.
Metadata is another thing entirely of course.

It is possible

People who want to discuss politics can discuss it there, people who don't can now just mute this channel.
This solution is okay, imo.

A point-based veto system resolves any issues that come with multiple matchmakers. I worked it out back when a few devs were interested in developing a veto system.

Matchmaker games are rated immediately, custom games have that delay until the game is ranked

Sure. The problem is just that every month they change the maps and I forget to make sure they're downloaded. But it's not a major issue.

genuinely curious on the ilshie -> incubus logic

The current featured mods are already mostly abandoned, no need to bring in more.
Also the underlying mechanics to distribute them is horrible, that I wouldn't accept any new.

Go for regular mods. They will break as well as featured mods do. All needs to stay compatible with FAF feature mod anyway.

@cyborg16 said in Forbid to kill underwater without weapons used that purpose:

But static T2 tactical missile launcher can't do any damage at any depth.

Odd. Why not allow TML to snipe T2 mexes or a parked ACU underwater? Is there a reason the missile detonates on contact with the water's surface?

Yes, the missile detonates on the surface. This isn't a problem for other missiles (nuke subs can fire non-nuclear tac missiles with 3 splash radius, UEF cruisers have tac missiles with 3 splash radius). Those missiles can kill fully-built HARMS if you just ground fire.

Whether or not to boost the splash radius of the TML is a balance decision. There are probably good reasons not to (it's already pretty strong, with extra splash it would be harder for ACU to dodge and maybe you could kill more buildings in 1 shot).

On some maps, there are mexes close together, separated by only 1 spot for a mass storage. If the TML had a bigger splash radius, it would probably be easier to kill 2 with one shot. I don't even know whether that's hard to do now, but it would be easier if the splash was bigger. It would also make TMLs a lot better at firing into armies. If you kill a percy 1/3 of the time, it's viable to use TMLs to shoot at armies, but if you kill a percy 2/3 of the time because of bigger splash, it would become very viable to use TMLs against armies. I don't know if we want to open that whole can of worms just to try to balance an unlikely situation (trying to use static TML to kill HARMS just doesn't seem like it would happen that often)

Still this should be added automatically to the FAF client in some way.
Or can you make it as a pop-up window that would be present during the loby waiting time. Maybe that would be easier to implement? Same pop-up as you get when the lobby is full, just always on or let's say 10sec after loby is full and when the host makes a switch then that it would pop-up again with refreshed stats??
And the Supreme Score Board mod should be added to the client automatically too - way better then the original!!

@emperor_penguin said in Make high tech engis more efficient than low tech engis:

T1 engineer spam often results in pathfinding problems and more lag. If we encourage concentrating bp in t2/t3 engineers instead of t1 engineers, that would often be a boon to pathfinding and lag reduction.

this is why they are already more efficient. Some setoners also switched to spamming t2 engies for assisting the naval factories. Just for the extra bp density and survivability.

A moderator kicking someone from a live game is a very rare occurrence. On top of that not all the circumstances for that are the same, often it is a dead player spectating that gets connection issues.

The payback for implementing some weirdly specific rule set for when a game should be unrated if a moderator kicks someone from a live game, just doesn't exist.

Just use Google forms ez

@ftxcommando said in Mass/energy storage full/depleted ETA timers:

I’m not really saying we’re at that point now, but I think it becomes something to begin thinking about if we need to consider having things like new player presets.

Beat you to it, I am trying to set that up in this forum post.

I agree with you that we should not overload our users. That is why it is such a struggle to add features to the lobby: it is already full in my opinion.

He's not wrong, any change to the speed of any unit in the game in any way is a balance change regardless of if you think that's the case.

Once the new CPU benchmark test is done, what about having a (fairly forgiving) minimum score/time that is required running the benchmark to join the 2v2+ matchmakers, to reduce one cause of slowdown? E.g. you'd require a better CPU for 4v4 than 2v2, and wouldnt have any restriction on 1v1.

That said I'd see it as a much more minori ssue - the issue I come across by far the most is also just having the game start in the first place - the majority of the time it times out after a couple of minutes on the Setting up automatch screen (with the reason being due to lack of response from other players)

Although it sounds like the core issue (stopping people who cant connect from joining) is being worked on, additional things that might help improve the experience would giving more information both on the progress with connecting to other players (if this is possible), and the reason for the failed connection beyond the current message (e.g. say we could connect to 6 out of 8 players, and were unable to connect to [name] and [name]'. If you're unable to connect to any other players then it would add to the end a message asking them to not try joining future matchmakers until they've resolved the issue/to seek help on the forum or something. I.e. it's quite possible that people are queuing, not able to connect to anyone, and then just keep retrying without realising they're the cause of the problem.

A thread with a good result! How rare!