**Understanding GX in the SpaceBudz Universe**
### **What is GX?**
GX is a unique classification within the SpaceBudz universe, highlighting a specific group of Budz. It encompasses those characters that possess at least one gadget but notably exclude the commonly seen covered helmet, chestplate, and belt. The term "GX" derives from "G" in gadget, acknowledging the presence of at least one gadget, and "X", indicating the absence of the three most common gadgets.
### **Count of GX**
The GX category includes a total of 96 distinct Budz, each showcasing a combination of gadgets that sets them apart from the standard gear setup. The distribution is as follows:
* **1GX**: 47 Budz with a single gadget.
* **2GX**: 43 Budz with two gadgets.
* **3GX**: 5 Budz with three gadgets.
* **4GX**: 1 Bud with four gadgets.
A 2GX Rhino
### **The Origin of GX**
The concept of GX arose post-mint as collectors started noticing Budz without the trio of common gadgets. It became a way to explore and appreciate the uniqueness within the SpaceBudz collection. GX represents the community's curiosity and passion for discovering and defining sub-rarities within the universe.
### **Exclusions in GX**
Certain animals and gadgets are either not represented or are extremely rare within the GX category. Notably, Bulls and Wolves do not appear as GX Budz. Additionally, apart from the covered helmet, chestplate, and belt, specific items like the SPO, Star Suit, and Camo Suit are absent in GX Budz. On the rare side, singular occurrences of GX Budz include the Dino, Rhino, and Shark, as well as unique gadgets like Binoculars, Candle, Flag, and Jetpack.
### Usefull GX links
\
---
# 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://spacebudz.gitbook.io/spacebudz/the-collection/the-gx-budz.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.