You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current /submit command takes in 3 parameters: the game being played, the red score, and the blue score. The submit command is potentially prone to typos, or outright cheating (in the event of a 1v1, it is extremely easy for one malicious player to fake the fact that a match ever happened and submit a fake score).
With recent std i/o features added the the game server, score info and game state info can be read in from the console.
Proposal
Automatically detect when the match is completed by scanning the game state periodically (use cron job?)
Automatically submit the red and blue score properly for the game associated with the server
Require that at least 51% of the expected players are on the game server for the score to be submitted (preventing fraud)
Things to consider
May need to differentiate between "restart all" matches and "tournament" matches (started via ready up). Should the /submit command be maintained but with fewer args, or should the command be removed altogether in favor of full automation?
How to deal with penalties that are added after the match ends?
The text was updated successfully, but these errors were encountered:
Context
The current
/submit
command takes in 3 parameters: the game being played, the red score, and the blue score. The submit command is potentially prone to typos, or outright cheating (in the event of a 1v1, it is extremely easy for one malicious player to fake the fact that a match ever happened and submit a fake score).With recent std i/o features added the the game server, score info and game state info can be read in from the console.
Proposal
Things to consider
May need to differentiate between "restart all" matches and "tournament" matches (started via ready up). Should the
/submit
command be maintained but with fewer args, or should the command be removed altogether in favor of full automation?How to deal with penalties that are added after the match ends?
The text was updated successfully, but these errors were encountered: