> For the complete documentation index, see [llms.txt](https://size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://size.club/docs/playing-a-trial/a-trial-minute-by-minute.md). # A Trial, minute by minute Play-by-play of a standard Trial. Read it once before your first run so the eliminations never surprise you. ## Before 0:00 * You acknowledge the briefing rules. * Your Key is consumed when the Trial starts. From here, the Key is the most this run can cost you. * Stage 1's Stage Boost is already visible. * Ten scores sit at zero: you plus nine bots. ![The briefing you acknowledge before the clock starts](https://cdn.jsdelivr.net/gh/dropbear-hl/size-docs-assets@master/trial-briefing.png) ## 0:00 to 3:00: Stage 1 * Markets are live. Trade any market in the asset dropdown, one or several. * Your score updates continuously as you make decisions. * Trade toward the Stage 1 boost shown on screen. * Watch your rank in the field as well as your PnL. ## 3:00: First elimination * The lowest score of the ten is eliminated. Their positions close automatically. * Nine remain. * Stage 2 boost appears. Stage 1 emphasis is gone. ## 3:00 to 6:00: Stage 2 * Adjust to the new boost. * Positions from stage 1 carry over unless you closed them. * Near the bottom in stage 1? You need a strong stage 2. ## 6:00: Second elimination * Lowest of nine is out. Eight remain. ## 6:00 to 9:00: Stage 3 * Mid Trial. New boost, same job: stay off the bottom. ## 9:00: Third elimination * Seven remain. ## 9:00 to 12:00: Stage 4 * The field is stronger on average. Weak bots are mostly gone. * Rank swings can be violent. Protect your downside, only yolo trade for score if you must. ## 12:00: Fourth elimination * Six remain. ## 12:00 to 15:00: Stage 5 (final stage) * Last boost. Last three minutes. * Fight for #1 among the survivors. ## 15:00: The buzzer * Every open position closes automatically. Positions also close automatically whenever a player is eliminated. * The final elimination lands: lowest of the six is out. * Five survivors place #1 through #5. The highest score wins the Alpha Life. #2 to #5 are Finalists. #6 to #10 were already eliminated. ## After the buzzer * [Your Grading](/docs/playing-a-trial/your-grading.md) for everyone, plus your run's [medal](/docs/playing-a-trial/medals.md) recap. * Finish #1 gets a Life: [auto-equip rules](/docs/after-you-win/earn-a-life.md). ## Survival checklist | Time | Entrants | If you are last right now | | ----- | -------- | ------------------------------------------- | | 3:00 | 10 → 9 | You are eliminated | | 6:00 | 9 → 8 | You are eliminated | | 9:00 | 8 → 7 | You are eliminated | | 12:00 | 7 → 6 | You are eliminated | | 15:00 | 6 → 5 | Lowest of six is eliminated; top five place | ## Tips * Learn the layout in Practice. Do not spend the first thirty seconds figuring out the UI in a Key Trial. * A small lead going into 2:45 beats a coin flip at 2:59. * Middle of pack mid-stage: consistency beats hail marys. * Last with sixty seconds left: you need size and direction immediately. ## Related * [How to win](/docs/playing-a-trial/how-to-win.md) * [How scoring works](/docs/playing-a-trial/how-scoring-works.md) * [The bots and Field Rating](/docs/playing-a-trial/the-bots-and-field-rating.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://size.club/docs/playing-a-trial/a-trial-minute-by-minute.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.