Budget: 27000 UAH Deadline: 10 days
Well, it's more like this - a full-fledged anti-cheat for CS2 shouldn't be made as a small plugin. For the first stage, I would budget 45,000 UAH and 10 days - analyzing the current Tenit, architecture, a prototype for detecting suspicious actions, an evidence log, a basic admin panel for moderation, and a plan for the full version.
I looked at the site tenitcs2.net - I see a live platform with servers, a lobby, Steam login, premium features, and a public part on Nuxt. So, the anti-cheat needs to be integrated into the existing system, not made as a separate game on the side =/
I would simplify it - start with server telemetry, behavioral rules, evidence preservation, and a verification queue for admins. A client agent or even more so a driver level is a separate, more expensive, and legally sensitive layer, and I wouldn't start with that without design.
> Is only a server-side anti-cheat needed or also a client program for the player?
> What should happen when triggered - auto-kick, ban, manual check, demo recording, or just a risk marker?
Similar approach cases:
> https://business.ingello.com/platforma - a complex platform with roles, data, and internal logic
> https://business.ingello.com/vorfahr - automation and smart rules around operational processes
> https://systems-fl.ingello.com/ua - our page on system development
I will provide an exact estimate for the full version after receiving answers and access to the current server part or API description. But the initial stage above seems to be the most reasonable entry point - without magic, dust in the eyes, and belief in a magic button.