> For the complete documentation index, see [llms.txt](https://zenwiki.gitbook.io/zen-republic-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zenwiki.gitbook.io/zen-republic-wiki/nft-collections/rubians/legacy-rubians.md).

# Legacy Rubians

We started The Rubian collection as **Zen Fighters: Rubians** back in Summer of 2022. Those NFTs were supposed to be game characters in VR esports game Zen Fighters. We did manage to make [the game](https://sidequestvr.com/app/5962/zen-fighters), but the idea is still a little too futuristic, considering the very niche audience of VR+NFT fans.

We failed to sell out all 720 NFTs due to various reasons, but 180 were minted, which gave us a little bit of a runway to pivot to other things and find where we belong.

<figure><img src="/files/o7EkjIasyDmPi5RQNjkD" alt=""><figcaption><p>Zen Fighters: Rubians NFT examples</p></figcaption></figure>

We spent a year building various fun things like gamified discord server, WebGL Zen Republic App, a couple of game demos and learning about the whole web3 industry in general. We were especially curious in how we could make web3 games that are not play-to-earn, as this was one of the curses haunting Zen Fighters in development process.

From the failed mint we promised to our holders that Rubians will one day be relaunched into a proper collection of 720 like we envisioned, right when we discover a proper innovative utility. Now  the time has come!

The collection has been renamed to **Zen Fighters (Legacy)** and is still available to trade on secondary market, while only the historic value remains: <https://magiceden.io/marketplace/zen_fighters>


---

# 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://zenwiki.gitbook.io/zen-republic-wiki/nft-collections/rubians/legacy-rubians.md?ask=<question>&goal=<endgoal>
```

`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.