Is Autoselecting Fine in Umamusume: Pretty Derby? What Players Should Know

If you've spent any time with Umamusume: Pretty Derby, you've probably encountered the autoselect feature — and wondered whether leaning on it is holding you back or just saving you time. The answer isn't as simple as yes or no, and understanding why will help you make smarter decisions during your runs.

What Is Autoselect in Umamusume?

In Umamusume: Pretty Derby, the training simulation requires players to make frequent choices during each育成 (ikusei) cycle — selecting which training sessions to attend, which events to respond to, and how to allocate limited energy resources. Autoselect (sometimes called auto-choice or auto-decision) is a feature that lets the game make these decisions for you, either fully or in specific scenarios.

The feature exists primarily for convenience. Training runs can last dozens of turns, and manually evaluating every decision point — especially across multiple characters — becomes time-consuming. Autoselect handles the repetition so you can progress faster.

What Does Autoselect Actually Optimize For?

This is where it gets nuanced. The game's autoselect logic generally prioritizes:

• Stat gains — choosing training tiles that raise core stats relevant to the uma's racing distance
• Avoiding failure — typically steering away from high-risk options when motivation or condition is low
• Energy conservation — sometimes selecting rest or recovery options over training

However, autoselect does not account for:

• Your specific skill targets for a given uma
• The Support Card composition you've built your deck around
• Event flag chains that require specific responses to unlock later bonuses
• Nuanced bond-building strategies with specific support characters

In short, the automation is general-purpose — it doesn't know your plan.

When Autoselect Tends to Work Fine 🎮

For certain situations, autoselect performs reasonably well without costing you much:

Casual or early-game training runs — If you're not targeting competitive stats or specific skill builds, autoselect gets you through runs without major losses. You'll produce a usable uma, even if it's not optimized.

Low-stakes event responses — Many in-game events have responses where the outcome difference is minor. Letting auto handle these rarely causes meaningful harm.

Farm runs for items or currency — If your goal is collecting medals, fan counts, or certain gacha resources rather than maximizing uma quality, autoselect is efficient.

New players learning the game — Watching what autoselect chooses can actually teach you the game's logic before you take manual control.

When Autoselect Creates Real Problems

Where autoselect falls short is in competitive or optimized play. If you're aiming for high-rank races, specific skill combinations, or strong PvP performance in the Circle Match or Champions Meeting, autoselect will leave gaps.

The gap between a manually optimized uma and an autoselected one can be meaningful at high difficulty tiers, particularly when racing content is tuned around stat thresholds.

The Support Card Variable

One factor that significantly changes the autoselect equation is your Support Card deck. Players running strong, well-bonded support decks will see better outcomes from autoselect simply because the pool of available options is higher quality. A weak or mismatched deck makes the auto's average choices worse by default.

Similarly, if your deck is built around a specific gimmick — stacking speed with a particular trainer type, for example — autoselect won't recognize that strategy. It plays the average, not your hand.

Skill Inheritance and the Manual Gap 🧩

One of the most important places manual play beats autoselect is in skill hint accumulation. Skills are one of the primary differentiators between an average uma and a competitive one. Autoselect doesn't meaningfully chase skill hints through training tile selection or event choices — it prioritizes stat bars.

If you're trying to pass down specific inherited skills or build a skill set that complements your target race type, manual oversight of at least the skill-heavy turns is worth the effort.

Player Skill Level and Time Investment

Whether autoselect is "fine" also depends heavily on what you're optimizing for as a player:

• Efficiency-focused players doing high volumes of runs may accept auto's ceiling to save time
• Competitive players targeting leaderboard ranks or tournament brackets typically avoid auto for key decisions
• Completionist players chasing story events or specific uma lore outcomes need to manage event responses manually
• Casual players who primarily enjoy the story and character content often find autoselect perfectly sufficient

There's no universal standard here. The game is layered enough that "fine" means something different depending on what you're trying to accomplish with a given run.

The Part Only You Can Answer

Autoselect handles the mechanics well enough to produce functional results — but it's optimizing for a general case, not your case. The meaningful question isn't whether autoselect works, but whether its tradeoffs align with what you're actually trying to get out of each training run. Your Support Card deck, your target skills, your tolerance for manual input, and the competitive level you're playing at all shape what "fine" actually looks like for your situation.