Build a Farming Table From the Game Wiki
A muse can work through a game's official wiki for you and build the answer into a clean spreadsheet, for example the newest characters in a game, where their parts drop, and which missions are best for farming them.
What it does
Game wikis hold everything, and that is the problem. The facts you need for one decision are spread across dozens of pages, each one crowded with side notes, version history, and links to five other pages. Planning a farming run can mean an evening of clicking before you fire a single shot. A muse reads the wiki the patient way. Give it a precise question and it visits the pages, pulls the same set of facts from each one, and lays them out in a spreadsheet: one row per item, with the drop location, the part, and the recommended mission in their own columns. Once the table exists, sorting and planning are easy. Sort by the mission you feel like running tonight and the evening plans itself. The muse prepares, you decide how to play.
How to use it
- Write the question narrowly. Name the game, the wiki, exactly which items you want covered, and the facts you want for each one.
- Ask for the result as a spreadsheet with one row per item and a column for each fact.
- Spot check a few rows against the wiki pages themselves, especially any row you plan to act on first.
- Ask for fixes in plain words if a column is missing or a row looks off, and have the muse rebuild the table.
- Save the spreadsheet somewhere you can reach it while you play, and ask for a refresh after a big game update.
What you need
- A muse account is enough
- The wiki is public, so there are no accounts to connect and nothing private is shared
- A spreadsheet app helps for sorting the result, but the muse can hand the table back in whatever format you can open
What to watch for
- Wikis are written by fans and change constantly, and a page can carry an error or describe an older version of the game. That is why the spot check matters: three rows checked by hand will catch most problems.
- Keep the question narrow, too. A request covering a whole game comes back shallow, while one covering a single set of items comes back solid.