> For the complete documentation index, see [llms.txt](https://docs.funsoccerworld.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.funsoccerworld.app/introduction.md). # Introduction ## The Opportunity The intersection of gaming and blockchain represents one of the largest opportunities in Web3. Billions of people play casual and competitive games every day, yet the vast majority of that time and skill generates no tangible value for the players themselves. Web3 gaming promises to change that by giving players true ownership of their assets and a share of the value they help create. However, many play-to-earn games have failed for one simple reason: they were not actually fun. They prioritized token mechanics over gameplay, attracting speculators rather than players, and collapsed once incentives dried up. Soccer Fun takes the opposite approach — the game comes first. ## The Soccer Fun Approach Soccer Fun is built around a core loop that is instantly accessible yet endlessly competitive. Anyone can pick up the game and control their pill-shaped striker with simple arrow keys, but mastering superpowers, timing, and positioning is what separates casual players from champions. The crypto layer rewards that mastery rather than replacing it. --- # 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://docs.funsoccerworld.app/introduction.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.