Getting started

Three things happen before you can look at a single stat: import hands, let the pipeline parse and store them, then open a tab. This page covers the first two, and ends with a map of where everything lives.

1. Export your hands

From your poker site's hand history export tool, save a folder of hand history text files, or a single .zip or .rar of that export. megamaster reads GGPoker, PokerStars, WPN, CoinPoker, 888poker, PartyPoker and iPoker exports — .txt for most sites, session .xml for iPoker — and works out which site wrote each file itself, so you are never asked and a folder holding more than one room's exports imports as all of them. The importer is adapter-based, so another site is a matter of writing a new adapter, not a rearchitecture.

2. Import

Open the Data tab and stay on its Import section. Drop your export onto the field (or browse to it), then hit Import. Subfolders are included, so the folder to point at is the one holding every screen name — HandHistory, not HandHistory/yourname. The import runs on a background thread and reports live progress — files seen, hands parsed, duplicates skipped, parse errors — because a real export can run to tens of thousands of hands and a silent multi-minute POST just looks like a hang.

3. What happens during import

• Each hand is parsed into structured players, actions, board, and pot data.
• Position (BTN, SB, BB, UTG, ...) is derived from seat + button, not read off the export literally — so it stays correct for 6-max, 9-max, and shorthanded tables alike.
• Pot type (walk, limped, SRP, 3bet, 4bet, 5bet+) and whether Hero was the preflop aggressor are computed once at import time, so every later query can filter on them directly instead of re-deriving them.
• Bet-size-as-percent-of-pot is precomputed per action, which is what powers the B30/B50/B70-style bucketing everywhere in the app.
• Hero's net result and all-in-equity-adjusted result are computed per hand, feeding the Results tab.

4. Where your data lives

Everything is stored locally in a SQLite database on your own machine. There's no server in the loop for import, storage, or querying — the whole pipeline runs on your machine against your own files.

5. Where everything lives

Five tabs across the top, in the order you'd meet them — the reports you read first, the tools you use away from the table, and the setup you touch rarely.

• Lines — where the app opens: the Lines map, the Preflop view, the decision-node explorer and the line overview, one matchup at a time.
• Train — drills proposed from your leaks, routines, puzzles and free play.
• Population, Results — the reports.
• Solve — Build, Viewer and Library, three sections of one solver workflow.
• Data — Import and Players, from the header menu.

The date/stake/players/position filter isn't a tab: it's the chip in the header, and it narrows every report tab at once. Your database file is also in the header — click it to switch databases.

Next

Once you've got hands imported, the Lines map is where the app opens and the fastest way to see something real: pick a matchup on the rail, and the key nodes of that line are there with your play beside the solver's — the red numbers on the rail say where to look first.