This feature covers the implementation and testing of warning flags on Match and Game. These flags function similarly to that of the AutomatedChecks, except there is no automated rejection of this data. The data will end up being PreVerified should there only be flags and no other means of auto rejection.
The goal of this feature is to implement the following warning flags:
Match
Title regex matching: {T_ABR}: ({TEAM_A}) vs ({TEAM_B}) where {T_ABR} is the tournament's abbreviation. vs check should be loose and cover VSvs., and everything in between (codified as UnexpectedTitleFormat).
Match game count is exactly 3 or 4 (codified as LowGameCount).
Game
If a tournament does not have a stored mappool and the beatmap is used exactly once in the entire tournament (codified as BeatmapUsedOnce)
If a tournament does have a stored mappool, and the beatmap is not in the mappool, and the game is not one of the first two games in the match (codified as BeatmapNotInMappool)
Depends on #438
Overview
This feature covers the implementation and testing of warning flags on
MatchandGame. These flags function similarly to that of the AutomatedChecks, except there is no automated rejection of this data. The data will end up beingPreVerifiedshould there only be flags and no other means of auto rejection.The goal of this feature is to implement the following warning flags:
Match{T_ABR}: ({TEAM_A}) vs ({TEAM_B})where{T_ABR}is the tournament's abbreviation.vscheck should be loose and coverVSvs., and everything in between (codified asUnexpectedTitleFormat).LowGameCount).GameBeatmapUsedOnce)BeatmapNotInMappool)Tasks