I didn't see the source code which I'm looking forward to, but choosing BEAM for a pug site sounds like bringing in cannons to kill a fly. It's designed to handle milions of connections, whilst pug has maybe tens, a hundred tops. If we're talking bringing down code complexity and keeping up maintanability, it'd be better starting with some simpler stack, slapping in metrics and benchmarks and doing optimizations once the bottlenecks are proven.

That said, I'm not quite familiar with Elixir; if this tech stack is what makes it simpler and easier for you, it looks like a good decision. We're here for creating stuff we like, not to optimize for money :)

cu@

Why do TF2 maps have so weird naming, how come there's no cp_chair or koth_egg

Btw, really nice map, looking forward to play a game on it

Lovely, thanks!

That's a hefty update, thank you!
Btw, any possibility to have the progress available via the API? I realize it's not very useful for quickstart servers, but for the other ones it might provide some value

Active support is guaranteed from my side, but we're yet to have reliable admins.

Hosting tf2pickup.org for div2+ players is not a problem. Adding captain system is also not a problem. Nor is adding elo.

Can we list a requirements for a pug site that people would actually play?

Why does the new version of the plugin request permissions to access offi-stg.lemontea.dev?

This. https://github.com/ValveSoftware/Source-1-Games/issues/4742

Hit me up if you need any help with the code; from what I've seen the backend was unable to configure the game server properly, it just hung - but I tested that 2 days ago, it might have been temporary.

It's _exactly_ the ordinary people that can do something; thinking that things will change on their own is simply wrong.

God's work steph

gg

lft

That's the changelog I waited for! B)