You just played three full games with your favorite card. He went 7-for-12 with two homers. And yet, when you open the card detail screen, the parallel progress bar looks like it barely moved. Before you assume the game is broken, take a breath — in the vast majority of cases, the PXP is being earned exactly as designed. The problem is that the way MLB The Show displays parallel progress is one of the most misunderstood systems in Diamond Dynasty. This guide walks through every common reason a card appears to stop earning PXP, how to tell a display quirk from a real problem, and how to verify your true progress with a simple tracking routine built around the Free Diamond Dynasty PXP Calculator.
Quick Triage: Is Anything Actually Wrong?
Let’s start with the good news. Genuine PXP tracking failures — where the game truly fails to record stats a card earned in an eligible mode — are rare. They do happen, usually around server hiccups or patch days, but they are the exception. The overwhelming majority of “my card isn’t earning PXP” complaints trace back to one of six predictable confusions, and every single one of them has a clear explanation and a clear fix.
Here’s the thing that makes this topic so frustrating for players: the symptoms of a display quirk and the symptoms of a real bug look identical in the moment. In both cases, you finish a game, check the card, and the bar hasn’t moved the way you expected. The difference only becomes visible when you know where to look, when the numbers update, and how much PXP your performance should have generated in the first place. That last part is where most players are flying blind — they have a vague feeling that “two home runs should be worth a lot,” but no concrete expectation to compare reality against.
That’s why the single most useful habit you can build is forming a numeric expectation before you check the bar. If you know your card should have earned roughly 240 PXP from a game, and the tracker shows roughly that, nothing is wrong — your expectations were just calibrated to a different number. You can build that expectation in about thirty seconds by entering your stat line and difficulty into the Diamond Dynasty PXP Calculator, which converts performance into estimated PXP using the current game-year values.
The 90-second rule: before assuming a bug, do three things — back fully out to the main Diamond Dynasty menu and re-enter the card screen, compare the number against a calculator estimate for the same stat line, and confirm the mode you played actually awards PXP. Those three checks resolve the vast majority of “missing PXP” cases without a single support ticket.
If you’re brand new to the parallel system and some of the vocabulary in this guide feels unfamiliar, it’s worth reading the foundational explainer on what PXP is and how parallels work first. This article assumes you know the basics and focuses entirely on the gap between what you expect to see and what the game shows you.
How PXP Tracking Actually Works Behind the Scenes
To understand why the display so often confuses people, you need a mental model of what’s happening under the hood. PXP isn’t a single number that ticks up live as you play. It’s the end product of a pipeline with several stages, and confusion creeps in whenever a player checks the number at the wrong stage of that pipeline.
The four-stage pipeline
While you play, the game logs every eligible stat action your card performs: hits, total bases, walks, runs, RBI, strikeouts thrown, innings pitched, and so on. At this stage nothing is PXP yet — it’s raw stat data tied to the specific card that performed the action. If a different version of the player performed the action, the stats belong to that card, not the one you meant to level.
When the game session ends (or when you exit through a valid path), each stat action is converted to base PXP using the per-action values for the current game year. A single is worth one amount, a home run more, an inning pitched another amount. If you want the full menu of what each action pays, the companion guide on how PXP is earned from every stat action breaks it down line by line.
Base PXP is then scaled by the relevant multipliers: the difficulty you played on, and in some modes, an online or mode-specific bonus. This is where a huge share of “missing” PXP actually goes — a player mentally calculates the All-Star value of their performance while grinding on Rookie, and the gap between those two numbers gets blamed on a bug.
Finally, the earned PXP is written to the card’s cumulative total and the progress bar updates. This write isn’t always instant. Server load, the path you took out of the game, and simple menu caching can all delay when the new total becomes visible — which brings us directly to the first and most common confusion.
Once you see PXP as a pipeline rather than a live counter, most of the mysteries in this guide stop being mysteries. A “stuck” bar is almost always a question of which stage you’re looking at, not whether the stages ran.
Confusion #1: Display Lag and Where Progress Actually Shows Up
The most common source of panic is also the most boring one: the number you’re staring at simply hasn’t refreshed yet. MLB The Show caches card data in several menus, and depending on where you check, you can be looking at a snapshot taken before your last game finished syncing.
Where players check — and which spots lie to you
There are at least four different places in the Diamond Dynasty interface where you can see some representation of a card’s parallel progress: the post-game summary, the card detail page reached from your squad screen, the card detail page reached from the collection, and the small parallel badge on the card art itself. These do not all update at the same moment. The post-game summary reflects the session you just played and is generally the most trustworthy immediate readout. The collection and squad views may lag behind until the menus reload their data, which usually happens when you back out to the main mode screen and re-enter.
The “back out and back in” fix
It sounds like superstition, but it’s grounded in how the menus cache data: fully exiting to the Diamond Dynasty home screen and re-opening the card view forces a refresh in most cases. Restarting the application entirely is the heavier version of the same fix, and on patch days or during server congestion it’s sometimes the only thing that works. If the number is still wrong after a full restart and the post-game screen showed the PXP being awarded, you may be looking at a sync delay on the server side — these have historically resolved on their own within hours, with the earned PXP appearing retroactively.
Important distinction: display lag means the PXP was earned but isn’t shown yet. It is not lost. Players who immediately replay a grind session “to make up for lost PXP” often end up double-counting their own progress and then get confused a second time when the totals jump unexpectedly later.
How to tell lag from loss
Write down (or screenshot) the card’s lifetime PXP before a session. Play one game. Note the post-game summary’s reported PXP. Then check the card detail an hour later. If before + reported = after, everything tracked correctly and you simply caught the menus mid-refresh earlier. This tiny experiment, run once, will permanently change how much you trust the in-game bar — and it pairs naturally with an estimate from the free PXP calculator so you can sanity-check the reported number against your actual stat line at the same time.
Confusion #2: PXP vs. XP vs. Program Progress — Watching the Wrong Number
Diamond Dynasty runs several progression currencies in parallel (no pun intended), and they all spike on the same screens after a good game. It is remarkably easy to watch the wrong one. A player sees “+1,250 XP” flash by, expects the card’s parallel bar to leap forward, and then feels cheated when it crawls — not realizing that the 1,250 was account XP for the seasonal reward path, which has nothing to do with the card’s parallel progress.
The three numbers that get tangled
PXP (Parallel XP)
Earned by a specific card through its own in-game stats. Drives that card’s parallel level and nothing else. This is the number this whole guide is about — and the one the parallel bar measures.
Account XP
Earned by you across almost everything you do. Drives the seasonal XP reward path. It often dwarfs PXP numerically, which is exactly why it hijacks attention on summary screens.
Program Progress
Earned by completing missions and moments tied to a specific program. Sometimes a program mission references PXP (“earn 5,000 PXP with Team Affinity players”), which blurs the line further.
The cruelest overlap is when a mission requires PXP earned by a category of cards. Players complete the mission, see the program tick up, and assume the individual card also paralleled — or the reverse: the card levels but the mission doesn’t move because the card wasn’t eligible for that program. Neither is a tracking failure; they’re two systems that happen to share a vocabulary word.
If you’ve ever caught yourself unsure which of these three numbers a screen is showing you, the dedicated comparison article on PXP vs. XP vs. program progress untangles all three systems with annotated examples. For the purposes of troubleshooting a “stuck” card, the rule is simple: the only number that matters is the card’s own lifetime PXP on its detail page. Ignore every other counter while diagnosing.
Enter the game’s stat line into the Waldev PXP calculator and compare its estimate against the card detail page — if they roughly match, your card is tracking fine and a different currency was fooling you.
Confusion #3: The Multiplier Math Feels Lower Than You Expected
Here’s a scenario that fills forums every single game year. A player grinds Conquest on Rookie because the games are fast and easy. Their slugger goes 4-for-4 with two homers. They’ve read somewhere that a home run is worth a meaty chunk of PXP, they double it, add the singles, and arrive at an expectation. The actual award comes in at a fraction of that. Conclusion: “my card isn’t earning PXP properly.”
What actually happened is that the per-action values they read were quoted at a higher difficulty’s effective rate, while Rookie applies a steep downward multiplier. Difficulty scaling is the single biggest silent reducer of PXP in the game, and because the game doesn’t show you the math — it just shows the final number — players consistently misattribute the gap to a bug.
An illustrative example of the gap
The table below uses illustrative numbers to show the shape of the problem rather than exact current values (which shift between game years and patches — always check current figures). Suppose a stat line generates 300 base PXP before difficulty scaling:
| Difficulty Played | Illustrative Multiplier | PXP Awarded | Player’s Likely Reaction |
|---|---|---|---|
| Rookie | ×0.25 | 75 | “Where did my PXP go? This must be bugged.” |
| Veteran | ×0.50 | 150 | “This feels low but maybe I’m misremembering.” |
| All-Star | ×1.00 | 300 | “This matches what the guides said.” |
| Hall of Fame | ×1.25 | 375 | “Nice, bonus PXP.” |
| G.O.A.T. | ×1.50 | 450 | “Worth the sweat.” |
Notice that the Rookie player and the G.O.A.T. player can produce the identical stat line and walk away with totals that differ by a factor of six. Neither experienced a bug. They experienced a multiplier. The full mechanics — including how online play layers its own bonus on top, and where the per-hour sweet spot usually lands — are covered in depth in the guide to PXP difficulty multipliers from Rookie to G.O.A.T.
The compounding version of this confusion
The multiplier confusion gets worse when players switch difficulties mid-grind. If you played five games on All-Star yesterday and five on Rookie today, today’s haul will look mysteriously anemic next to yesterday’s even though your performance was similar. Without a written log, the brain averages everything together and concludes the system became stingier overnight. The fix is to keep difficulty as a recorded variable in your tracking — and to recalculate your expectation every time you change it. Plugging the new difficulty into the PXP calculator before you queue up takes seconds and pre-empts the entire disappointment cycle, because you’ll know in advance that a Rookie session simply pays less.
Rule of thumb: any time your PXP “drops” right after you changed difficulty, mode, or game length, the change is the explanation. Genuine tracking failures don’t correlate with your settings — multiplier math does.
Confusion #4: The Wrong Card Version, the Wrong Slot, or the Wrong Guy Entirely
PXP belongs to a card, not to a player. That one sentence resolves an astonishing number of “not leveling” complaints. Most star players exist in Diamond Dynasty as several distinct cards — a Live Series version, program versions, flashback or legend variants, seasonal awards versions. Each is a separate item with its own separate PXP total. Stats earned by one version contribute nothing to any other version.
The duplicate-version trap
Here’s how it bites people in practice. You pull a new, better version of a player you’ve been grinding. You slot the new card into your lineup and keep playing your usual sessions, glancing occasionally at the old card in your collection and wondering why it froze. Or the reverse: you intend to keep leveling the old version for its parallel rewards, but the lineup actually contains the new one. The game did nothing wrong — the stats went exactly where the lineup said they should.
The bench and substitution trap
Cards earn PXP from stats they personally accumulate in the game. A card sitting on your bench through a full 9-inning game accumulates nothing, no matter how glorious the team’s performance was. Cards that enter as substitutes earn from the moment they enter — so a pinch hitter who takes one at-bat earns one at-bat’s worth. Players running squads with deep benches sometimes spread appearances so thin that individual cards barely move, and the slow crawl reads as a malfunction. It isn’t; it’s arithmetic. If your goal is leveling one specific card, that card needs maximum playing time, ideally in a lineup built around feeding it opportunities.
The two-way and pitcher/hitter split
Pitchers earn primarily through pitching stats and hitters through hitting stats, with each archetype’s actions valued on its own scale. A pitcher who bats in a no-DH setup earns hitting PXP for those at-bats too, but the totals are usually small next to a full pitching line. Players sometimes evaluate a pitcher’s progress after a game where he was pulled in the third inning and conclude PXP stopped tracking — when in reality the card simply logged three innings’ worth of actions. The positional differences are mapped out fully in the comparison of hitter PXP vs. pitcher PXP.
Thirty-second check: open your active squad — not the collection — and confirm the exact card art, series badge, and overall of the version in the lineup slot. If you own multiple versions of the player, this check should be the very first step whenever progress looks frozen.
Confusion #5: Modes and Situations That Award Little or No PXP
Not every way of playing baseball in MLB The Show feeds the parallel system equally, and a few situations feed it nothing at all. Players who bounce between modes without knowing these boundaries are the ones most likely to report “random” tracking failures — because from their perspective, the same card behaves differently on different days for no visible reason. The reason is the mode.
Where PXP flows freely
The reliable PXP environments are the core Diamond Dynasty gameplay modes: Conquest and other Play vs. CPU formats, Mini Seasons, and the online head-to-head modes such as Ranked, Events, and Battle Royale (online play typically carries its own bonus multiplier on top of difficulty). These are the lanes where the pipeline described earlier runs end to end, and where the strategies in guides like Conquest PXP farming live.
Where PXP gets thin or stops
Co-op play. Cooperative modes have historically awarded reduced or no parallel progress, varying by game year. If your grind sessions are co-op sessions, check the current year’s rules before blaming the tracker — this is one of the most common hidden causes of “frozen” cards.
Friendly / custom matches. Unranked friendlies and custom lobby setups often sit outside the progression loop entirely, precisely so they can’t be farmed between cooperating accounts.
Moments and some mission content. Moments use fixed scenario rosters and typically award program progress rather than parallel progress for your own cards. Stats your card “earns” inside a Moment usually don’t touch its lifetime PXP.
Games abandoned through invalid exits. Quitting through a valid in-game path generally banks the stats accumulated to that point, but force-closing the application or disconnecting mid-game can result in the session not being recorded. The line between safe and unsafe exits is tested in detail in the quitting-early PXP myths article.
Other game modes entirely. Road to the Show, franchise, and exhibition play outside Diamond Dynasty have no connection to your DD cards’ PXP, obvious as that sounds — but new players genuinely do conflate them.
The pattern to internalize: PXP rules are per mode, per game year. When a card that leveled smoothly all week suddenly stalls, ask what was different about today’s session before asking what’s wrong with the game. Nine times out of ten, the answer is “I played a different mode.”
Confusion #6: You’ve Hit a Cap — or Misread a Threshold
The final confusion is the quiet one nobody suspects: the card is tracking perfectly, and the bar genuinely isn’t moving because it has nowhere left to go, or because the bar is measuring a longer journey than the player realizes.
The Parallel 5 ceiling
Once a card reaches its maximum parallel level, PXP display effectively becomes moot — there is no next bar to fill. A player who buys a card secondhand off the marketplace may not notice it’s already maxed, plays a few games, sees zero bar movement, and reports a bug. Check the parallel badge before checking anything else: a card at the cap isn’t broken, it’s finished.
The non-linear threshold staircase
Parallel thresholds are not evenly spaced. Early levels arrive quickly; later levels demand multiples of everything that came before. A bar that filled visibly with every game during Parallel 1 will appear nearly motionless per game during the climb to Parallel 5, even though the underlying PXP-per-game is identical. The perception of “slowing down” is built into the threshold design, and it is the most common reason experienced grinders — who clearly know the card is earning — still feel like something broke late in the grind. The exact staircase, with the current year’s threshold figures and how to read them, is documented in the reference guide to PXP thresholds for each parallel level, and the psychological toll of that final stretch gets its own treatment in the hidden time cost of Parallel 5.
Reading the bar correctly
One more subtlety: the progress bar shows progress within the current level, not lifetime progress toward the final parallel. Crossing a threshold resets the visual bar to near-empty for the next level. A player who checks mid-session, sees the bar lower than it was an hour ago, and doesn’t realize a level-up happened in between will swear PXP was deleted. Nothing was deleted — the odometer rolled over.
The Free Diamond Dynasty PXP Calculator takes your card’s current PXP, your average performance, and your difficulty, and estimates the games remaining to any parallel level — so a slow-looking bar never has to feel like a mystery again.
The Full Diagnostic: Symptom → Likely Cause → Fix
Everything above, compressed into a single reference you can run through in under two minutes the next time a card looks frozen. Start at the top and stop at the first row that matches your situation — the rows are ordered from most to least common.
| Symptom | Most Likely Cause | Fix / Verification |
|---|---|---|
| Post-game screen showed PXP, but card detail page didn’t change | Menu caching / display lag | Back out to the DD home screen and re-enter; restart the app if needed; re-check after an hour before concluding anything. |
| Big “+XP” numbers after the game, tiny parallel movement | Watching account XP or program progress instead of PXP | Ignore all counters except the card’s lifetime PXP on its detail page; compare against a calculator estimate of the stat line. |
| Great stat line, PXP far below expectation | Low difficulty multiplier (or expectation set at a higher difficulty’s rate) | Recompute the expectation at the difficulty actually played; consider moving the grind to the highest difficulty you can win efficiently. |
| Card frozen for days despite regular play | Different version of the card is in the lineup, or card rides the bench | Open the active squad and verify the exact card version and its playing time; consolidate at-bats/innings onto the target card. |
| Card levels in some sessions, never in others | Mixing eligible and ineligible modes (co-op, friendlies, Moments) | List which modes you played on which days; confirm current-year PXP rules per mode; grind in core DD modes. |
| Bar lower than it was earlier today | A parallel level-up reset the visual bar | Check the parallel badge — it likely incremented; the “missing” PXP is banked in the completed level. |
| Bar never moves at all, ever | Card already at maximum parallel | Check the parallel badge for the cap; a maxed card has no further bar to fill. |
| Session ended in a crash/disconnect, no PXP anywhere | Invalid exit — session not recorded | Unrecoverable in most cases; exit through valid menus in future and avoid force-closing mid-game. |
| All of the above ruled out; post-game showed PXP that never landed | Genuine sync failure (rare; often patch-day related) | Document with screenshots, wait 24 hours for retroactive sync, then contact support with the evidence. |
If you work through this table and land on the final row more than once in a season, something unusual is going on with your account or connection — but for everyone else, the table ends the investigation at row one through seven. Many of these traps are also covered from a prevention angle in the broader roundup of PXP grinding mistakes that waste hours.
Building a PXP Tracking Routine That Ends the Guesswork
Every confusion in this guide shares one root cause: the player had no independent record of what the card’s PXP should be, so the in-game display became the only source of truth — and the display, as we’ve seen, tells the truth on a delay, in a dialect, with several lookalike numbers shouting over it. The cure is a lightweight tracking routine. It takes about a minute per session and converts every future “is this bugged?” moment into a thirty-second lookup.
The five-line session log
Before the session, open the card detail page and note the lifetime PXP and current parallel level. A phone photo is enough. This is your baseline, and it’s the single most valuable line in the log.
Mode, difficulty, and game length. These three variables explain nearly every “unexplainable” swing in PXP-per-game you will ever see, but only if you wrote them down.
After the session, take your stat line and run it through the Diamond Dynasty PXP Calculator at the difficulty you played. Write the estimate down before looking at the in-game number. This ordering matters: it trains your intuition and makes discrepancies pop instantly.
The post-game summary is your most immediate official readout. Estimate and summary should land in the same neighborhood; small gaps are normal (bonus actions, rounding, partial appearances), while a gap of half or more means one of the six confusions is in play — usually the multiplier or the mode.
An hour later, or at the start of the next session, confirm the card’s lifetime PXP equals baseline plus the session’s awards. When it does — and it almost always does — you’ve proven your tracking pipeline is healthy, and you never have to wonder again.
Why the estimate step is the keystone
Notice what the calculator step really does: it replaces a feeling (“two homers should be worth a lot”) with a number (“this line at this difficulty is roughly X PXP”). Feelings are what get mugged by multipliers, threshold staircases, and account-XP confetti. Numbers aren’t. Grinders who adopt this habit also get a free byproduct — an accurate measure of their PXP-per-hour across modes, which is the foundation of every efficiency decision covered in the advanced planning articles, from estimating games needed for any parallel level to choosing between grind modes in the first place. The guide explains the concept, but the calculator is what lets you apply it after every single session.
Three Real-World Scenarios, Solved
Theory is tidy; grinding is messy. Here are three composite scenarios — assembled from the patterns players report most often — walked through with the diagnostic method. All PXP figures are illustrative examples, not exact current values.
Scenario 1: “My new flashback hasn’t gained a single point in a week”
Marcus pulls a flashback version of his favorite shortstop and decides to take it to Parallel 5. A week later, the card shows the same PXP it had on day one. He’s played every evening. Bug, right?
Running the diagnostic: the post-game screens during the week did show PXP being awarded to a shortstop — so stage four of the pipeline is working for somebody. He opens his active squad and finds the answer in ten seconds: the Live Series version of the same player, which his squad-building screen auto-slotted by overall rating, has been starting every game. The flashback has been sitting in the collection the entire time. Every run, hit, and web gem went to the Live Series card, which is quietly approaching Parallel 3. Fix: manually slot the flashback, bench the duplicate, and the “frozen” card thaws immediately. Total PXP lost to bugs: zero. Total PXP donated to the wrong card: a week’s worth.
Scenario 2: “I switched to faster games and my PXP fell off a cliff”
Dana has been grinding Mini Seasons on All-Star with 9-inning games, averaging (illustratively) about 350 PXP per game on her ace pitcher. To speed things up she switches to 3-inning games on Veteran. Her per-game number collapses to a small fraction of what it was, and the per-session total is down too. She suspects the patch that dropped that morning broke pitcher tracking.
The diagnostic says: two settings changed at once, so the change is the explanation until proven otherwise. Three innings means roughly a third of the innings-pitched and strikeout actions per game — that alone cuts the base PXP to a fraction. Then the Veteran multiplier takes its bite out of what’s left. Multiply the two effects and her new per-game figure is exactly what the math predicts; her per-hour figure is the only fair comparison, and depending on game speed it may even have improved. She runs both configurations through the PXP calculator, sees the projected totals match reality in both cases, and realizes the patch was innocent. The deeper version of this exact trade-off is the subject of the 3-inning vs. 9-inning PXP comparison.
Scenario 3: “The bar went DOWN. Explain that.”
Theo checks his catcher’s progress bar mid-session: about three-quarters full. Two games later it’s barely a quarter full. He has screenshots. Surely this is the smoking gun — PXP was deleted.
One look at the parallel badge closes the case: the card was at Parallel 2 in the first screenshot and Parallel 3 in the second. Between the screenshots, the card crossed a threshold; the bar emptied and began filling toward the next, much larger requirement. Nothing was deleted — the odometer rolled over, and because thresholds grow level over level, the new bar also fills more slowly per game, compounding the illusion. Theo’s screenshots, far from proving a bug, are a perfect illustration of how the parallel level system displays progress within a level rather than across the whole journey.
The common thread: in all three cases the player had real evidence of a real anomaly — and in all three cases the anomaly was the display model, not the tracking. The diagnostic table earlier in this guide would have resolved each one at the first or second row.
Frequently Asked Questions
Why is my card not earning PXP at all?
Work through the causes in order of likelihood: you’re checking a cached menu that hasn’t refreshed; a different version of the same player is actually in your lineup; you’re playing a mode that awards reduced or no parallel progress (co-op, friendlies, Moments); or the card is already at its maximum parallel level. Genuine tracking failures are rare and are usually visible as a mismatch between the post-game summary and the card’s lifetime total that persists past a full app restart and a 24-hour wait.
How do I check how much PXP my card actually has?
Open the card’s detail page — from your squad screen or the collection — and look for the lifetime PXP figure and the parallel progress bar. The post-game summary shows what a single session awarded, while the detail page shows the cumulative total. For an independent cross-check, estimate the session’s expected PXP from your stat line with the Waldev PXP calculator and confirm the lifetime total advanced by roughly that amount.
Does PXP update immediately after a game?
The post-game summary updates immediately, but the card detail and collection views can lag behind due to menu caching and server sync. Backing out to the Diamond Dynasty home screen and re-entering usually forces a refresh; on busy patch days the sync can occasionally take longer, with the PXP appearing retroactively. Lagged PXP is delayed, not lost.
Why did my progress bar go down after a game?
Almost certainly because the card leveled up between your two checks. The bar measures progress within the current parallel level only, so crossing a threshold empties the bar and starts filling toward the next, larger requirement. Check the parallel badge on the card — if it incremented, nothing was lost.
Do bench players earn PXP?
No. PXP comes from stat actions a card personally performs in the game. A card that never enters the game earns nothing, and a substitute earns only from the point it enters. If you’re targeting one card for a parallel grind, build the session around giving that card maximum at-bats or innings.
Does quitting a game early delete the PXP I earned?
Exiting through a valid in-game menu path generally banks the stats accumulated to that point, while force-closing the application or disconnecting mid-game risks the session not being recorded at all. The safe and unsafe exit paths — and the myths around them — are tested in detail in our dedicated quitting-early guide.
Why does the same performance give different PXP on different days?
Because something else changed: the difficulty multiplier, the mode (online play typically carries a bonus; some modes pay reduced rates), or the game length. Identical stat lines at different settings can differ by several times. Keeping a short session log of mode, difficulty, and game length makes these swings predictable instead of mysterious.
When should I actually contact support about missing PXP?
Only after you’ve ruled out the common confusions: the post-game screen showed PXP being awarded, the correct card version was in the lineup, the mode was eligible, the card isn’t capped, and the lifetime total still hasn’t advanced after a full app restart and roughly 24 hours. At that point, screenshots of the post-game summary and the unchanged card detail page give support something concrete to investigate.
Stop Guessing — Verify Your Grind in Seconds
A “stuck” card is almost never a broken card. It’s a cached menu, a lookalike currency, a quiet multiplier, a duplicate version, an ineligible mode, or a threshold staircase doing exactly what it was designed to do. The players who never get burned by these illusions aren’t luckier — they simply carry an independent expectation into every session, so the display can’t gaslight them.
That expectation is one form away. Enter your card’s current PXP, your typical stat line, your difficulty, and your mode, and the Free Diamond Dynasty PXP Calculator tells you what each session should produce and how many games stand between you and the next parallel. Before your next grind session — and especially before your next support ticket — run the numbers with the calculator. The guide explains why the bar behaves the way it does; the calculator proves your card is on track.
Estimate PXP per game, verify your tracking, and plan the exact number of games to any parallel level: waldev.com/diamond-dynasty-pxp-calculator
Keep reading in this series
Avoid the traps
9 PXP Grinding Mistakes · PXP vs. XP vs. Program Progress · Quitting Early: Myths Tested
Disclaimer: All PXP values, multipliers, and threshold figures in this article are illustrative examples used to explain how the system behaves. Exact values vary by game year and can change with patches. Waldev is not affiliated with Sony Interactive Entertainment or San Diego Studio; MLB The Show and Diamond Dynasty are trademarks of their respective owners. Always verify current in-game values, and use calculator results as planning estimates rather than guarantees.