Players rarely open a game service with a product in mind. They open it with a question: what to do first at launch, how long the grind will take, whether they can be ready for raid night. An AI gaming companion exists to answer it, and the interesting engineering sits between that first message and the plan, or the order, that comes out.
The examples below come from LFCarry, which pairs an AI companion for game questions and planning with a marketplace of optional services from professional players, called Pros. The running case is World of Warcraft: Forever, launching November 4, 2026 at 3:00 p.m. PST.
Stage 1: Turning free text into structured intent
Take an opening message from a player who mains a Hunter, works weekdays and wants level 60 before the first raids. It holds 4 fields a planner needs: game, character, time budget and a dated goal. The companion’s first job is to extract them and ask plainly for anything missing, because a plan built on a guessed level or schedule can cost days.
The company’s homepage chat entry points map onto this step: labels such as “Research a custom question”, “Help plan and calculate” and “Consult with agent” let a player state the kind of help they want, and goals no listing covers get a custom quote in chat.
Stage 2: Grounding every answer in dated game data
A companion is only as reliable as its facts, so calendars, content counts and class changes belong in a structured layer where every entry carries a source and a check date. According to Blizzard, WoW Forever adds 4 new zones, more than 1,000 quests between levels 1 and 60, and 9 new dungeons for groups of 5 covering levels 13 to 60. The first raids, Barrow Deeps, Hyjal Summit and Onyxia’s Lair, open on December 9, 2026.
The layer also has to model what is still unknown. The Hardcore ruleset is due after launch with no announced day, and dual spec sits at level 40 for now while Blizzard discusses that level. Stored as open items, such gaps let the companion say plainly that a date is unannounced.
The company also documents a Model Context Protocol server, so other software can read this kind of data: 12 public reading tools answer JSON-RPC calls, including list_games for coverage, read_guide for a guide’s sections and dated current state, weekly_reset for the weekly rotation and get_offer for a service page’s options. The homepage’s WoW Forever shelf alone lists more than 100 guides.
Stage 3: Planning logic turns constraints into options
Planning becomes a constraint problem: goal, deadline, the player’s own hours and the size of the job. Launch day and the first raids are 35 days apart, and the full 1-60 route takes about 150 hours in game at a professional pace.
A planner then lays the options side by side. A player with free evenings levels alone and leans on the companion for routes, talents and professions. A player who wants company stays on the character while a Pro plays alongside or coaches, and coaching is sold by the hour on a brief confirmed in chat. A player short on time hands the route over: 1 Pro playing 12 hours a day reaches 60 in 10 to 14 days, and 2 Pros in shifts play around the clock and finish in 5 to 7 days.
Plans also come in pieces: the leveling calculator splits 1-60 into 10-level rows, so a player can order a smaller bracket first and add levels, professions or gear later. Each leveling order comes with a personal plan too, covering talents, gear, professions and dual spec.
Timing logic matters as much as volume. A leveling pre-order starts on launch day or on a later day the player names in the order chat, at the same price; raid slots wait for December 9; Hardcore orders begin when that ruleset goes live. Jobs key to a date or to an event with no date yet, and a planner has to handle both.
Stage 4: Handing the request to a human professional
A companion that routes work to people has to know where its own job ends. After checkout, the system matches the player with an available Pro and opens an order chat, where the Pro confirms the schedule. A clean handoff carries the confirmed brief, the options and the plan, so the first message can be about the work itself.
Human-to-human handoffs need the same discipline. On 2-Pro leveling orders, each shift change runs on a written checklist: quest log, hearth, bags and repairs. Metering follows the same idea: hours start counting when the character is in the world and moving.
Stage 5: Keeping the chat as the record of the order
The least visible choice may be the most useful: the conversation becomes the record of the order. Progress is tracked in that chat until completion, the start day is named there and add-ons are requested there, so every change has a time, an author and a context both sides can read back.
The developer documentation follows the same model: tools used on behalf of a player list that player’s orders with code, status and a link to each order’s chat, and read the replies posted there. On piloted leveling orders, where a Pro plays the character, a free live stream of the whole playtime adds a visual record.
A checklist for judging any companion
The pattern travels beyond games. A companion worth using should:
- extract structured intent and ask for whatever is missing;
- answer from dated data and say plainly when something is unannounced;
- plan against real constraints such as deadlines and available hours;
- hand work to people with the full brief attached;
- keep the conversation as the history of the order.
It should also be worth opening when nobody plans to buy anything. LFCarry, operating since 2016, describes its companion that way: a place to ask questions, explore options and plan play, with professional services as an optional layer.