> For the complete documentation index, see [llms.txt](https://docs.bigindie.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bigindie.games/game-portfolio.md). # Game Portfolio A growing portfolio built for players, communities, and long-term ecosystem growth. ### Memes At War Memes At War is one of the flagship games of BIG Indie Games: a meme-powered GameFi first-person shooter where memecoin communities meet fast-paced competitive gameplay. Players can control meme-inspired characters, enter action-packed battles, compete across maps and game modes, and take part in a broader community-driven gaming experience. The game combines classic FPS gameplay with the energy of Web3 communities, while keeping skill, teamwork, and strategy at the center. Project page: ### Pulse Arena Pulse Arena is an in-development multiplayer battle arena game and high-quality mobile MOBA built around fast competitive battles in a clean sci-fi universe. The game is designed for regular mobile gamers: easy to start, smooth to play, fair to compete in, and rewarding to master. Players can choose heroes, join team battles, control the map, push objectives, and outplay opponents in a futuristic arena built for clarity and competition. Project page: --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bigindie.games/game-portfolio.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.