> For the complete documentation index, see [llms.txt](https://infinity-command.gitbook.io/infinity-command/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infinity-command.gitbook.io/infinity-command/crew-stations/control-center.md).
# Control Center
The **Control Center** module consists of a handful of buttons, switches, and sliders. The labels are all configurable, so each crew station can have an individualized version of this module that aligns thematically with their role.
The primary purpose of the Control Center is to facilitate **Special Procedures**: open-ended tasks that the crew must work together to accomplish. When a Special Procedure begins, the system generates a list of tasks for the crew to perform with their Control Center. As they complete the tasks, the Special Procedure progresses toward completion. The entire crew can see the task list and the overall progress, so they can help and encourage each other.
The power of a Special Procedure is that it can be anything — *"hack into the alien mainframe," "scan for intruders," "extend the shields around the colonists' vessel,"* etc. This fills a crucial gap because it's impossible for the built-in crew station UI to fully cover every possible action that a crew might need to perform. Whenever the story calls for something extra or unexpected, that's where Special Procedures come in. This gives the Flight Director great storytelling freedom, all while keeping the crew closely involved with progressing the plot forward.
Sample Control Center specification in the Ship's config file:
```
"Modules": [
{
"Id": "ControlCenter",
"Label": "Control Center",
"Settings":
{
"SliderA": {
"Title": "Fuel Injector",
"IncrementLabels": ["0", "25", "50", "75", "100"]
},
"SliderB": {
"Title": "Docking Clamps",
"IncrementLabels": ["A", "B", "C", "D", "E"]
},
"SliderC": {
"Title": "Axis Stabilizers",
"IncrementLabels": ["0%", "10%", "20%", "30%", "40%", "50%", "60%", "70%", "80%", "90%", "100%"]
},
"FlipSwitchA": {
"Label": "Heading Lock"
},
"FlipSwitchB": {
"Label": "Nav Beacon"
},
"ButtonA": {
"Title": "Throttle Array",
"Label": "Recharge",
"SpritePath": "Icons/ufo-5.png"
},
"ButtonB": {
"Title": "Flight Recorder",
"Label": "Log",
"SpritePath": "Icons/triangle-reticle-locked.png"
},
"System":
{
"ImagePath": "ControlCenter/Astrolabe.png",
"Title": "Astrolabe Nexus",
"Label": "Crystal Alignment"
}
}
}
]
```
---
# 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://infinity-command.gitbook.io/infinity-command/crew-stations/control-center.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.