# Game Onboarding and Acquisition

The long-term success of OOBIKOO Games hinges on our ability to onboard interesting new games capable of engaging our audience. Our onboarding model is based on two key pillars, *Financial Incentives* and *Developer Support*.

### Financial Incentives

Our value proposition is simple: bring your game to our platform and you will make money. You bring the game, you use our platform to enable a web3 ecosystem, and we bring you an audience of engaged players ready to spend.

To support this model, while keeping our developers invested in the success of our platform and ecosystem, we incentivise developers with $OOBI token allocations distributed via milestone based unlock system.\
\
The token amount and milestone structure will be negotiated on a case-by-case basis, but the table below offers a representative example:

| Unlock Milestone    | Token Allocation | Post Unlock Vesting Period |
| ------------------- | ---------------- | -------------------------- |
| Deal Sign           | 10%              | 1 Year                     |
| Web3 Prototype      | 20%              | 1 Year                     |
| Launch              | 30%              | 3 Years                    |
| MAU Target Achieved | 40%              | 3 Years                    |

Locked tokens can't pay the bills, so, on a case-by-case basis we will also provide direct financial support to developers via fiat or tethered tokens such as USDC.

### Developer Support

Although getting developers onboard with a rewarding set of financial incentives is important, we also need to ensure that developers deliver. Out developer platform offers a suite of tools to ensure the transition from web2 to web3 is as frictionless as possible. Our platform will include tools to enable use cases like: 

* card packs and NFT loot boxes
* secure token generation for gameplay activities
* dividing a game world in to user owned spaces<br>

Support doesn't end with the technical platform, we are also developing our *Delivery Framework* a set of workshops, processes, and tools that help game designers understands how best to transition their product to web3. We will help ensure they understand the space so they can answer questions like: Where should NFTs be used? Should I include player owned spaces? Can our game logic be decentralised?

## Other Onboarding Paths

Although our initial focus will be on inviting existing web2 games to our web3 ecosystem there are a number of other ways for games to enter our ecosystem.

### Web3 Games

Even developers of games that are already targeting web3 can struggle with the technical complexity and challenging game design problems that arise in web3. Or maybe they know the tech but can't build a community. Our platform is also a perfect match for these developers.

### New Games

Although some of our tools are clearly geared towards migration our platform will also provide excellent support developers building new games. Once we have proved our platform through our own games and several successful migrations we will begin aggressively targeting new games. We will look for experienced developers who are passionate about creating truly unique and engaging experiences.

### Acquisition

Some developers may be willing to give up their IP for the right price, but may not be interested in making the web3 transition themselves. Although we prefer to have original developers onboard, we know that sometimes a product may be such a good fit that we are willing to outright acquire the IP. This presents an excellent opportunity for more *dog-fooding,* allowing us to test both our technical platforms and our game design tools by doing the same work we ask our developers to do.

Acquisitions suitability and terms will be handled on a case-by-case basis.

***

**Disclaimer**\
\&#xNAN;*The information presented in this whitepaper is provided for informational purposes only and does not constitute legal, financial, or investment advice. All statements regarding plans, projections, business strategies, or other forward-looking information are based on current expectations and are subject to change due to evolving business, market, and regulatory conditions. This document is not a guarantee of future performance or outcomes, and no liability is assumed for any reliance placed upon its contents.*<br>


---

# 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://docs.oobikoo.games/tokenomics/game-onboarding-and-acquisition.md?ask=<question>
```

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.