released several updates with some improvements, check the discord for more information

https://clips.twitch.tv/CovertFilthyScorpionTinyFace-e8U2TybcZ6puE4KZ

yooo these devs are on fire lately

Can we not use that language on the forums please, thanks.

enjoy you filthy spy mains

Holy cow, that's amazing. Kinda kills my idea, but I may have some more up my sleeve.

This basically means that serveme is a mirror of nfo or tragic, and that's great.

I created a whole new beta api that runs serverlessly, which is fancy talk for "it's going to be super fast".Well, it's only as fast as the connection from whatever datacenter it chose to the server, but we can ignore that.

you can find the new link here to the website and use the url https://beta-api.rcon.tf if used as an api.

to use the api, just send a POST request with a body containing "ip", "command", "password" and optionally "port". You'll get an error if it doesn't have the information it needs.

since I open source everything now, you can view the source here for api and the frontend here

- Fixed Engineer losing metal when hitting damaged buildings while they are being re-deployed after pick-up
is the real big one here

WAIT
- Fixed Wrap Assassin projectiles colliding with other projectiles and func_lod entities

WHAT

While yes, people do throw games to get lower elo and thus easier games, if done right, the "formula" for elo should bounce it back.

I'm unfamiliar with how pugchamp did their elo system nor do I know much about if this is a real impact for pugchamp, but that's where I'd start: learning what pugchamp did and hear feedback from pugchampers about their games.

The easiest solution would be to build an elo system.

Let's take an example:

A random user logs into tf2pickup.eu, and this magic service will look at all (configurable?) leagues and see what their average skill level is. This skill level would just be some number, maybe 1 for open and 10 for invite. Calculate the average skill by weighting the most played division by that factor. We would end up with this base line rating to what a skill level would be, and it's factored based on the overall scores of both time played and highest division played in.

You could then go into more detail on games played, where their internal score (essentially elo now) is based on number of games won (or won in a row). You can then deduct a maximum percentage based on the current score for each loss.

Basically, just write an elo system. That's all.

wtf is this shit

Payload V5 is released!

Almost 3 months in the making, and well over a year in planning, I am finally releasing the next version of Payload! This was an incredible amount of effort to put forward, so if you would like to support what I do, please visit our patreon

Here's the outline of what was done:
1) A total, ground-up rewrite of the entire bot
2) Re-write all translation keys
3) Completely redesigned the API
4) Argument parsing is much nicer overall
5) Slash and button support!!!

Though with these new changes, comes some ones that are going to affect you:
1) Webhook routes are all changed (/api/webhook/v1 => /api/v1/webhook)
2) All command restrictions have been reset, and are now guild-wide
3) Language and Settings commands are not present

What's next?

I'm planning a whole new dashboard experience. I want to rewrite the dashboard to better reflect the capabilities and the features of Payload and hopefully allow for newer people to better use Payload. I want to bring a better experience configuring and integrating with Payload, and I think the best way is to provide a richer experience on the dashboard.

With that wraps the announcement, and have a great holiday week all!

New payload update requires having the latest version installed, you can view that here

It has been patched in this commit

hold your breath