A gamer knowledge base that reads every wiki and patch note
Ask it anything about any game and get a straight answer, no scrolling through ten year old forum threads.
The problem
You need to know which boss drops the Obsidian Greaves, but you end up on a wiki page full of spoilers, a YouTube video with nine minutes of intro, or a Reddit thread that devolves into memes. Game knowledge is scattered across a hundred sites, and finding the one detail you need can take longer than the fight itself.
What AI makes possible now
Models now read entire game wikis, official manuals, patch notes, and community guides in one go. They understand screenshots and can listen to a voice question while you play. This product ingests all that text, indexes it, and answers your exact question in seconds. It cites the source, knows when a mechanic changed in patch 2.4, and never spoils the story. You get a calm, direct answer, not a content farm.
How it works
- You type or speak a question like 'Where do I farm void salts in the current patch?'
- The system searches its indexed corpus of official documentation, trusted wikis, and curated community guides for that game.
- An answer is generated from the retrieved chunks, with a short citation and a warning if the information might be outdated.
- You can upvote, downvote, or ask a follow-up. Flagged bad answers trigger a re-index of newer sources.
The first thirty days
Index the top five most-requested live service games. Build a simple web app where a user types a query and gets a plain text answer with source links. No accounts, no voice yet. Ship within 30 days and let a few Discord communities test it.
How it earns
Free tier for ten questions a day. A monthly subscription removes the cap and adds voice input, image upload for item identification, and a personal library of saved answers. Later, a white-label version for game studios to embed on their support sites.
Why now
Long context windows and cheap inference mean you can ingest millions of words per game and keep them fresh without a large team. Voice interface makes it usable while your hands are on a controller.
First customers
Competitive players who need fast, accurate mechanical details. Speedrunners who care about patch-specific glitches. Modders and server admins who reference old build notes.
The hard part
Data licensing is the honest hard part. Some wiki owners will want compensation. Staying current across dozens of live games requires reliable ingestion pipelines and a way to detect when a source quietly updates.
Build this with us
We would start by ingesting the wikis and patch histories of two games you care about, then put a bare answer engine in front of a small group of players. If you run a gaming community and you are tired of answering the same questions, apply to build this with Nexibeo.