Yes, but I’m saying the algorithm for layoffs factors in “performance”, which can be factored from past bonus allocations.
The algorithm isn’t going to lay off 150’s, but might preferentially select 100’s.
I don’t have inside info, I’m just making assumptions that the data has to come from somewhere.
The REPO devs are quoted as saying:
But the article writer turns this into:
If that was what they meant, that’s what they would have said, since what they said doesn’t imply that at all. Depending on the API, the mods could be doing any number of things with even a single player that would send network traffic through the roof.
Telling modders this is just about lobby size might diminish the impact of what the devs are requesting. An inexperienced modder who isn’t changing lobby size might not realize they’re inadvertently being a bad citizen with other stuff they’re doing.
As someone else mentioned, they should look into protecting themselves within their API though. Rate limits, etc. Since this whole thing took off on them unexpectedly, they probably weren’t prepared, so in the meantime they’re requesting the mods be more careful. Ultimately, this won’t work though.
Tbh, if it was just a lobby size thing, I would think that would be super easy to defend against server-side…