Three Numbers and One Contaminated Price: Decoding the NBA Fantasy Market

On the draft board of a Yahoo points league, Lauri Markkanen was selected at pick 27. His ADP was 39.2. The 31.1% gap — the largest on the board — made him the most debated name of the night. But when I opened his game log, the numbers appeared far colder: 55, 47, 42. The past three seasons. A total of 144 games out of roughly 246 possible — 58.5% availability. Across nine seasons, he has reached 60-plus games only three times. One-third of his career. One manager called it "a bargain the market forgot." I call it an unanswered question: for a player present 58.5% of the time, are you paying for talent, or for the hope that this season will be different? Every number I touch carries a scar. To understand this mock draft, you first have to understand the rules shaping it. This is a Yahoo points league. The roster requires PG, SG, G, SF, PF, F, C, C, two UTIL slots and three bench spots. Two starting center slots are the single most important detail — they turn big men into a structurally scarce commodity priced above general market value. When every team needs two starting centers and only a handful of centers can genuinely start, the market inflates the price on its own. That is the rule, not a personal preference. Points formats also differ from category formats in one fundamental way. Category leagues split value into discrete boxes: FG%, FT%, threes, points, rebounds, assists, steals, blocks, turnovers. You win by winning more boxes. Points leagues blend everything into a single score, and player value depends on what the system rewards. This is where I stop. The analysis never states whether the league penalizes turnovers. That is not a minor detail. If turnovers carry a penalty — common in Yahoo points leagues — then the entire "efficiency does not matter" argument weakens, and the praise for Castle's high-turnover games becomes a genuine analytical gap, not a matter of taste. I have tracked fantasy leagues for years. What I learned: the best players are not the best stat-sheet readers. They are the ones who understand what the scoring system rewards, and find players mispriced by the gap between formats. This mock draft is a perfect example — with three central names: Markkanen, Embiid and Castle. Start with Joel Embiid, because his case is the clearest and least disputed. 96 games over three seasons. Out of roughly 246 possible, that is 39.0% — about 32 games per season. For a max-salary player in his early thirties carrying a heavy career workload, this number is not only about health. It is about the fact that, most of the time, the team has to learn to live without him. The mock draft pushed Embiid from ADP 51 to pick 65, a 27.5% fall — the largest on the board. The logic is coherent: the team has been reconstructed so it no longer depends on him in the regular season, so it will manage his rest, reduce his minutes, reduce his usage, preserving him for the real playoffs. Three negative adjustments compounding. But I want to pause here. Is a 14-pick fall enough? Applying the article's own logic — managed rest, fewer minutes, lower usage, on a roster that no longer needs him to carry — that number may still be generous. The market sees the mechanism, but may not fully price the consequences. And here is the crux the analysis touches but never names: Embiid's biggest fantasy problem is not that he plays worse, but that he does not play at the right time. Fantasy playoff weeks typically fall in the final three to four weeks of the regular season — exactly the window in which the team rests him. The best player is absent in the most important week. That is a structural paradox, not bad luck. Markkanen faces a similar paradox, but from the opposite direction. The analysis attributes his low games-played totals partly to tanking for lottery position. That empty summer, but the data never rests. It means he was shut down in March and April — exactly the fantasy playoff window. A contender and a tanking team can destroy their players' fantasy value for opposite reasons. But the consequence is identical: he is not there when you need him most. Three 60-plus-game seasons in nine is not randomness. It is a structural pattern. For a shooting big man with a rare and valuable skill, the question is not whether he is talented. The question is whether he is available. And on a revamped roster, his usage may decline — good for real basketball, bad for a points format where volume production is what gets paid. Castle follows an entirely different trajectory. 18 double-doubles, 5 triple-doubles in a single season. For a guard, triple-double frequency is a strong marker of sustained multi-category volume — precisely what points formats pay for. He was valued at 51st in fantasy points per game but drafted at pick 39. The market is paying for trajectory, not current production. That is a reasonable bet, provided you accept he is not yet a finished product. What is interesting is that the author's analyses of Markkanen, Embiid and Castle are observational, not self-serving: none appear on his 13-man roster, and the cited picks (27, 39, 65) do not match his own slots (11, 14, 35, 38, 59, 62, 83, 86, 107, 110, 131, 134, 155). That increases the credibility of his contrarian calls. But there is a notable internal tension. He praises Castle being taken at pick 39, while he himself selected Jalen Duren at pick 38 — passing on the player he endorses one pick earlier. It could be positional priority, given the two-center requirement. But it also shows: even a strong analyst has to bend to the rules of the game. Now to the part few people say out loud. None of the three stories above are about basketball skill. They are about the difference between two pricing languages: the language of real basketball and the language of points formats. The same player, two systems that pay differently, sometimes in opposite directions. Markkanen is the counter-flow example. A revamped team may reduce his usage, moving him into a more efficient role — good for real basketball. But in points formats, lower usage means lower volume production, and that is bad news. One event, two opposite consequences. Which means: advanced metrics describing a more efficient player do not mean he is more valuable in a points format. Two measures, two verdicts. But there is something the analysis does to itself. It scrutinizes other managers' picks for availability risk — Embiid, Markkanen — but does not apply the same standard to its own build. James Harden, Pascal Siakam, Ivica Zubac, Norman Powell, DeMar DeRozan — that is an old roster, and availability risk compounds with age. A framework not applied to its own user is not a framework, only a selective tool. The same reason that makes you doubt Embiid makes you doubt half your own roster. And here is the deepest point the mock draft touches but never names: ADP is a contaminated price. It is the blended result of category-format and points-format players, across leagues with different rules and sizes. When you read an ADP, you are reading the average price of systems that are not the same. Someone who knows this can exploit it — a market inefficiency that can be identified and used. But there is a loop here. The mock draft is both the instrument that measures ADP and the input that produces ADP. I join drafts to prepare, and my own selection behavior produces the data others use to prepare. The market feeds itself. And those who contribute most to producing the data are those most influenced by it. That is why ADP-based strategies tend to converge on consensus rather than exploit it. And that is why the author's critique — "ADP is a blend of formats" — is worth more than any individual pick recommendation. One more variable worth tracking. San Antonio owns a crowded backcourt and wing rotation — with Castle, De'Aaron Fox, Devin Vassell and the rise of a new talent. Four players competing for touches and minutes is a season-long role question, not a one-week draft note. It affects development curves, extension talks, and the possibility of a trade. This is the most durable observation in the piece — not a pick recommendation, but a structural question about how a team allocates its resources. So if there is one thing worth carrying away from this mock draft, it is not a list of players to draft. That advice expires in days, when the draft ends. The thing worth carrying is a question: what is your scoring system paying for, and in whose language are you pricing your players? Before you watch the game, watch how the data breathes. The signals I am tracking: Embiid's minutes over the first twenty games, San Antonio's backcourt minute distribution, and Markkanen's usage rate when the season tips off. The chaos on the court always has an underlying order. And that order, this season, has a name: availability.