Skip to content

Commit c229d83

Browse files
committed
Made explicit rule regarding submission only containing relevant demos
1 parent bf2bce5 commit c229d83

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/05_proof-standards.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ or framerate issues which impact viewability, and they must not be uploaded to a
1111
suspicious websites.
1212

1313
Demos must be submitted for every segment of the run, in the correct order, with none
14-
missing. You must start recording demos before the run begins where possible, or
15-
otherwise as soon as you can - it is recommended to use `sar_record_at` to achieve this.
16-
On runs with multiple segments, demos must be recorded across loads - this is normally
17-
expected to be achieved via the `sar_autorecord` command, but categories may define
18-
different methods.
14+
missing. You must only submit the demos that are relevant to your run. You must start
15+
recording demos before the run begins where possible, or otherwise as soon as you
16+
can - it is recommended to use `sar_record_at` to achieve this. On runs with multiple
17+
segments, demos must be recorded across loads - this is normallyexpected to be
18+
achieved via the `sar_autorecord` command, but categories may define different methods.
1919

2020
The only websites allowed for uploading demos are Google Drive, and Mediafire. If
2121
you are uploading to Mediafire it is a requirement to zip the demos for your run.

0 commit comments

Comments
 (0)