# Unit System
Our team has designed a "Unit System" system that allows us to create and change racetracks as quickly and easily as possible when needed.
Racetracks consist mainly of 4 different courses—it is worth noting that they do not necessarily consist of all the courses at the same time and with the same number—besides the various kinds of connection parts that help to differentiate the racetrack design. Each course is a blank page and has various length options.
With just the four different courses and lengths, we can create an almost infinite number of racetrack blackouts without obstacles. Even if the racetrack blockout is the same, players go through different numbers of various courses and see different obstacle combinations. Connection parts also play an important role in separating racetracks. These parts help us create new experiences even though there are only 4 course options.
Blank courses are suitable for any obstacle combination, so the same combinations may be used in different course types. For example, players encounter the pendulum-speed circle combo on the swimming course and the flying course, even on the same racetrack.
The other convenience the "Unit System" provides is that our **community** has a chance to be part of our racetrack design process. The community's involvement in our development is greatly appreciated, and "User Generated Content" events will be regular. **Third-party partnership** possibilities are also extended in this way.
---
# Agent Instructions: 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:
```
GET https://whitepaper.fundora.life/game-overview/racetrack/unit-system.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.