> For the complete documentation index, see [llms.txt](https://ascendrobotics.gitbook.io/ascend/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ascendrobotics.gitbook.io/ascend/other/extra-stuff/vex-team-resources-high-stakes.md).

# VEX Team Resources (High Stakes)

We are here to help

## Primary Resources

Game video: <https://www.youtube.com/watch?v=Sx6HJSpopeQ&t=99s>

Game Manual (READ THIS!):  <https://content.vexrobotics.com/docs/2024-2025/v5rc-high-stakes/HighStakes-1.0.pdf>

"How to Win Robotics" - a document giving an overview of the process of Robotics, made by a former club member: [https://docs.google.com/document/d/1ss3dj3vwZIJbd0fW2elEkKdIoimpplIeJ7vIDK2Wzq0](https://docs.google.com/document/d/1ss3dj3vwZIJbd0fW2elEkKdIoimpplIeJ7vIDK2Wzq0/edit)

"101 Things I Wish I'd known..." - another overview of VEX robotics, with good general advice: <https://www.vexforum.com/t/101-things-i-wish-id-known-before-my-first-vex-tournament/16081>

"VEX Notebooking Guide" - explains the Engineering Design Notebook well: <https://docs.google.com/document/d/1_Q3tK04eIctlpk9GPR97G4Y_mjCfG2P7fL3U60Ilepc/edit?usp=sharing>

## High Stakes Robot Designs

Finals match from the first major VEX tournament (MOA). This is great for getting an idea of how this game is played at a high level by other teams: (Wait until August 5th)

\#1 Skills run in the World (as of 8/5/24). Skills is how you qualify to States and Worlds!  N/A

Peruse this page if you please: <https://www.youtube.com/results?search_query=vex+high+stakes>

***

Please note that the rest of this website is a work in progress (as of 7/16/24) and will be updated throughout the year.&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ascendrobotics.gitbook.io/ascend/other/extra-stuff/vex-team-resources-high-stakes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.