The rules Checks use
Checks group what they look for into seven rules. Each issue names its rule, for example "code 88 · substitution". This page says what each rule checks and how to fix what it finds. The messages are quoted as Courtside writes them, with made-up numbers.
Score
Every point moves one team on by one, and a set ends at a winning score.
| Message | What to do |
|---|---|
| "point to home: score 12:10 → 14:10, expected 13:10" | A point code is out of step. Usually a rally is missing or doubled: look at the rallies before it. |
| "point after the set was won at 25:22; missing set end?" | The set should have ended. Check the score, or end the set. |
| "set 2 ends at 24:22, which doesn't win it" | A set end at a score that doesn't win the set. A point is missing or the set end is early. |
| "39 s of video since the last point, usually 17 s; a missed rally?" | An info note. See How to find a missed rally. |
| "score corrected from 14:11 to 14:10" | An info note: the scout changed the score by hand. Nothing to fix if the new score is right. |
Score corrections in imported files
VolleyStation has no code for "the score was wrong". When a scout fixes the score there, the file gets rallies made only of green codes ($$&) and a point code, and together they move the score down, or on by more than one point. For example, to take back a point given to the away team by mistake:
| Code | Meaning |
|---|---|
*$$&H= | a green code against home |
a$$&H# | a green code for away |
ap14:10 | the point code, with the score back at 14:10 |
Courtside reads such a run of rallies as a score correction. It shows one info note with the old and new score, instead of a score error, and doesn't check who serves across it, since a correction can change that too.
A single rally of green codes that adds exactly one point is a point without a play, not a correction, and gets no note. Points that skip a score in ordinary rallies are still a score error.
The missed-rally note needs video times. It ignores gaps with a timeout, substitution, comment or set end in them.
Rotation
Teams rotate on a side-out, the rally winner serves next, and players are where the rotation says.
| Message | What to do |
|---|---|
| "away won a side-out but didn't rotate" | A rotation is missing. Fix rotations from here. |
| "home serves but away won the last rally" | A serve typed for the wrong team, or a point given to the wrong team. |
| "home server 7 is in zone 3, not zone 1" | The wrong player serves for this rotation. Check the serve's shirt number, or the rotation. |
| "home setter moved from zone 4 to 2; expected 3" | A setter-zone code doesn't follow the rotation. |
| "home player 8 is not on court; missing substitution?" | A touch by a player who isn't on court. |
| "home player 8 went off earlier in set 1; missing substitution?" | They were subbed off and never came back on. |
| "home player 15 hasn't been on court in set 1; wrong shirt number?" | Probably a typo in the number. |
Courtside writes its own rotations again after any edit, so most rotation faults come from rallies coded before a fix, or from rotations typed by hand. See Fixing rotations.
Back row
Back-row players don't block, and don't attack from the front zone.
| Message | What to do |
|---|---|
| "back-row player 5 (zone 1) blocked" | Check the block's shirt number, or the rotation. |
| "back-row player 5 (zone 6) attacked from zone 3" | Check the shirt number, the start zone, or the rotation. |
| "front-row player 11 (zone 4) attacked from back-row zone 9" | An info note. It's legal, but rare: usually the start zone or the rotation is wrong. Check both, and leave it if the player really did attack from behind the 3 m line. |
Substitution
Players come on and off legally, within the season's limit per set, and liberos don't attack or block.
| Message | What to do |
|---|---|
| "player 6 is not on court" | The player going off isn't on court. Check the numbers. |
| "player 7 is already on court" | The player coming on is already playing. |
| "player 12 is not on the home team sheet" | Add them to the match roster, or fix the number. |
| "player 9 has already gone off and come back on this set" | An illegal re-entry. |
| "player 6 can only be replaced by 9" / "player 11 can only come on for 4" | A player can only swap with the one they came on for. |
| "home substitution 7 in the set; the limit is 6" | Too many substitutions. The limit is in Settings → Rules. |
| "libero 1 attacked" / "libero 1 blocked" | A libero's touch that isn't allowed. A libero serving is a warning, unless the season allows it. |
| "home player 1 is a libero on the team sheet but is on court in set 1; team sheet wrong?" | A libero in the six. Check the roster's L box. |
Serve and reception
A serve is followed by the other team's reception or ends the rally, and the point goes to the team the touches say won it.
| Message | What to do |
|---|---|
| "rally has no point code" | The rally isn't closed. Add the point. |
| "second serve in one rally; missing point code before it?" | The rally before didn't end. |
| "a serve should be followed by the other team's reception" | A touch is missing or has the wrong team. |
| "reception without a serve from the other team" | A serve is missing, or the reception has the wrong team. |
"a10RH+ doesn't fit the serve *07SH+ before it; check one of the two" | A warning: the pass's rating doesn't go with its serve's. Modify one of them; with a dot code the other follows. See the table below. |
"point to home but a10AH# means away won the rally" | The point and the codes disagree. Fix one of them. |
"the rally continues after *08SH# ended it" | A code after a winning or losing touch. Check the rating. |
"a10AH/ was blocked but the other team has no block point (B#) after it" | A blocked attack and a block point go together. |
"block point *12BH# without a blocked attack (A/) from the other team before it" | The same, the other way round. |
"*09RH/ is an overpass but home won the rally; check the evaluation" | Often fine; an overpass rally can still be won. |
"*08SH+ won the point with no reception; an ace is coded S#" | A warning. The rally is a serve alone and the serving team won it, but the serve isn't rated as an ace. Rate it #, or add the reception you missed. |
| "second reception in one rally" | A warning. One serve, one reception. Usually a dig coded as a reception: change its skill to D. |
"a16RH# repeats the code before; entered twice?" | A warning: the same player, skill and rating as the touch just before. Usually a code typed twice. Remove one. |
| "player 11 set and then blocked" | A warning: one player sets and then blocks straight after, which can't happen. Check the shirt numbers. |
"*11EH+ sits between the other team's reception and attack; coded for the wrong team?" | A warning: away passes, home sets, away attacks. The set probably belongs to away: change its team. An overpass (R/ or D/) is left alone, because then the other team really does play the ball. |
Which passes fit which serves
A serve's rating says how hard it was to pass, so the pass right after it has to agree:
| Serve | Passes that fit |
|---|---|
# (ace) | = |
/ | / |
- | #, + |
+ | -, ! |
! | !, + |
Most of these are the pairings DataVolley's compound codes and VolleyStation both use. S+ with R! and S! with R+ are a second convention many DataVolley 4 scouts use, so they don't raise a warning either.
Roles
The setter on court sets the good passes and makes the setter calls. Courtside knows who the setter is from the lineup and the substitutions since. These are info notes, hints that the setter may be wrong in the lineup or that a shirt number is off.
| Message | What to do |
|---|---|
| "set on a good pass by 12, not the setter 8; is the setter right?" | A set straight after the team's own # or + pass, by someone other than the setter. Check the set's shirt number and the setter in the lineup. Leave it if someone else really did set. |
| "setter call on a set by 12, not the setter 8" | A set with a setter call (*12EH+K1) by someone other than the setter. Check the shirt number, or take the call off. |
A set after a poor pass by someone other than the setter is ordinary play and isn't flagged.
Code
The codes themselves can be read, and a reception agrees with its serve.
| Message | What to do |
|---|---|
| "unrecognised code …" | The code doesn't fit the layout. Modify it. |
| "unknown evaluation …", "unknown skill type …" | A symbol or letter that isn't one of the standard ones. |
| "start zone … is not 1–9", "end subzone … is not A–D" | See Zones and subzones. |
| "setter position 7 is not 1–6" | A setter-zone code out of range. |
| "custom text … is over 5 characters; DataVolley cuts it to …" | DataVolley keeps 5 characters of custom text. |
| "…: X5 starts in zone 4, the code in zone 2; check the combination" | An info note: the attack's start zone isn't its combination's. |
"a16RH+ is type H, the serve before it type M" | An info note: a reception has the same type as its serve. One of the two is a typing slip. With a dot code, modifying the serve's type changes the reception's too. |
| "the reception's end zone is 6, its serve's 5" | An info note: a reception shares its serve's start zone, end zone and subzone. Fix whichever is wrong. The note names the first one that differs. |