Heart & Soul Kurt Poké Balls guide
Choose Kurt’s special Poké Balls using the maker’s type affinities and encounter conditions, without guessing berry recipes or catch multipliers.
Start with Kurt in Azalea Town
The official FAQ directs players to bring Kurt berries in Azalea Town. It says the balls retain Heart & Soul’s type-based behavior alongside their GSC/HGSS behavior. Follow this game’s documentation instead of assuming a remembered vanilla apricorn recipe applies.
Before making a large batch, read the in-game requirement and check the current item reference. This guide does not supply unverified berry recipes, batch sizes, processing times or purchase prices. A listed item value alone would not prove what a shop charges.
Which ball matches your target?
| Ball | Maker-listed affinities or conditions | Planning question |
|---|---|---|
| Heavy | Rock, Ground, Steel; heavy Pokémon | Does the target fit a listed type or weight condition? |
| Lure | Water, Dragon; fished-up Pokémon | Is this a fishing encounter or a matching type? |
| Fast | Fire, Electric, Fighting; fast Pokémon | Does the target fit a listed type or speed condition? |
| Level | Normal, Flying, Ice; low-level Pokémon | Does the target fit the listed level or type context? |
| Love | Psychic, Fairy; opposite gender | Is the type match clear, or does gender matter here? |
| Moon | Dark, Ghost, Poison; Moon Stone users | Does the target match a listed type or evolution category? |
| Friend | Bug, Grass; friendship | Is friendship part of your reason for catching it? |
These are item-description summaries, not a ranked catch-rate formula. The documentation used here does not establish the exact numerical multiplier for each overlapping condition. A type match is a reason to consider a ball, not proof that it always beats every alternative.
Make a shortlist from checked target facts
Use the target’s actual typing in your installed run, especially if types are randomized. Select checked facts; undocumented entries remain visibly unresolved. This helper reads no game files and resets when the page reloads.
Unconfirmed shortlist — check the remaining facts
- Check the target’s current primary type.
- Check its second type, or choose no second type.
- Check whether this is a fishing encounter.
No candidate established from these selections.
This is an unranked shortlist. It does not calculate catch odds, combine bonuses or evaluate weight, speed, relative level, gender or Moon Stone conditions.
Based on the maker’s v2.0.6 item descriptions checked 8 Oct 2026. Read the bag description and available stock before choosing a throw. List order does not rank effectiveness.
Example: Dark and Fire give two reasons to inspect your stock
For an illustrative target whose current types are Dark and Fire, select those two types and confirm the encounter method. Fast and Moon appear because each description matches one of the entered types. The helper deliberately leaves both candidates available. It does not choose a numerical winner.
Read the item descriptions in your bag, then compare the stock you actually have. If one candidate is unavailable, that is an inventory limit rather than a change to the target’s typing. If both are available, the list alone cannot establish which has the higher final catch chance.
Example: Water, Dragon and fishing still produce one Lure candidate
Entering Water and Dragon and selecting a fishing encounter gives multiple descriptive reasons for Lure, but only one candidate row. The reasons do not add into a calculated multiplier. Do not read three reasons as three times the bonus.
If one type is not documented, the result remains unconfirmed while retaining any reason you have established. That is useful for planning, but it is not a completed check of the target. Read the current in-game information before using scarce stock, particularly in a randomized run.
The friendship checkbox describes a goal after the catch. It adds Friend as a candidate to inspect without pretending that friendship alone ranks its catch effectiveness. For the next team task, use caught-candidate preparation.
Build a small stock around your next session
Choose a target or a route before spending resources. Record the target’s current in-game typing, how you expect to encounter it and whether you care about friendship. Then use the table to make a shortlist.
Example: a planned fishing session
Lure belongs on the shortlist because its description explicitly includes fishing. That still does not justify using every berry you own. Keep a general catching option available, check the target when you meet it and use the actual encounter to decide what to throw.
For a mixed route, a small variety can be more practical than a large stock selected for one assumed target. For a specific collection goal, specialize only after confirming the Pokémon’s information in your own version. This is an inventory-planning approach, not a tested optimization of the catch formula.
Handle overlapping types and changed rules
A Pokémon with two relevant types may put more than one special ball on your shortlist. The table alone cannot resolve that tie. Do not add the descriptions together or assume two matching types double a bonus unless the game’s formula confirms it.
If you enabled randomized types, check the Pokémon as it exists in your run. A familiar species name is not enough to establish its current typing. Read the battle or Pokédex information available to you before selecting a ball on that basis.
Keep the catching decision separate from team building. A Pokémon can be easy to target with a special ball yet still be a poor fit for the role you need. Think about what you intend to do with it after the catch as well as how you will catch it.
Confirm place, time and method before choosing a ball
A suitable ball cannot make a species appear in an encounter table. Use the v2.0.6 wild-encounter reference, checked 8 Oct 2026, to identify the target’s exact area, time and method first.
| Target | Maker-listed entry | Planning implication |
|---|---|---|
| Larvitar | Dark Cave South Side; daytime land; 5%, levels 2–4 | Match the named side and daytime table |
| Gastly | Sprout Tower 2F; night land; 35%, levels 4–6 | A different floor or daytime search is a different table |
| Houndour | Route 36; night land; 10%, level 5 | Arrange the night search before specializing the ball stock |
| Poliwhirl | Route 31; Super Rod; 40%, level 40 | The Old Rod table is not interchangeable with this method |
For a normal, unrandomized run, copy the relevant row into a short session plan. Then check the target’s actual typing and shortlist a special ball using the affinities above. A listed encounter percentage describes that reference’s table; it does not promise a number of attempts or establish your final catch probability.
Example: the rod is the missing prerequisite
You stocked Lure Balls for Poliwhirl but are fishing with an Old Rod on Route 31. The maker’s Old Rod list names Magikarp and Poliwag, while the Poliwhirl example belongs to Super Rod. Resolve the acquisition method first, or consciously choose an earlier form and research its evolution. Changing the ball cannot resolve the table mismatch.
For day/night boundaries and the consequence of a deliberate clock edit, use the time-planning section. If you enabled randomized encounters, retain that setting in your note before treating these ordinary table examples as a promise for your run.
Is your target a gift or a capture?
Check how the Pokémon joins your adventure before planning scarce ball stock. The creator's Gifts & Statics reference separates gifts from static encounters. A reward handed to you and a Pokémon you battle call for different preparation.
For a gift, prioritize its listed conditions and the result you intend to receive. For a battle encounter, prepare the party and balls as well as access. If you want a shiny, identify whether the exact entry is fixed, locked or uses a documented retry method before choosing a checkpoint.
Example: you want the Dragon's Den shiny Dratini reward. Buying a preferred special ball does not satisfy its quiz condition. Lake of Rage Gyarados is instead a battle capture: obtaining the desired result includes actually keeping it after the encounter.
The fixed shiny reward comparison explains these two examples. Keep the gift conditions and the actual catch result separate from the type-based ball affinities above. Source checked 8 Oct 2026.
A practical pre-catch checklist
- Confirm the game and documentation version.
- Check the target’s current type and relevant encounter conditions.
- Select candidate balls from the maker’s descriptions.
- Read the in-game item wording before using scarce stock.
- Keep a backup catching option for unexpected encounters.
- Review the result without treating one catch or failure as proof of a multiplier.
Random outcomes make a single throw a weak test. If you report a suspected issue, include the ball, target, current type, encounter method, version and active randomizer settings. That gives the developer a reproducible context rather than a guess about which ball should have won.
Safari recruitment: choose properties before treating the catch as complete
A target's availability, its capture and its usefulness as a teammate are separate questions. Heart & Soul's maker documents Pokéblock feeders for selecting properties of Safari encounters. That is a recruitment system, not an extra ball affinity to add to the table above.
- Confirm the target is available in the area and run you are using.
- Decide which attacking or defensive properties matter to your intended role.
- Use the matching feeder plan where applicable.
- Inspect the caught Pokémon's actual summary.
- Choose whether to keep and train that catch before spending further resources.
Example: the species you wanted is finally caught, but your plan also required a specific Nature. The capture succeeded; inspect the Nature separately. Do not conclude that the encounter table or ball description failed because a different recruitment preference was unmet.
Follow the Pokéblock colour, flavour and Nature guide for the documented feeder choices. It does not promise a target species or provide a capture multiplier. Creator reference, checked 8 Oct 2026.
Sources and scope
Primary reference: official v2.0.6 item reference and the official FAQ, checked on 7 Oct 2026. Check the in-game wording if your version differs. No ROM, BIOS or prepatched-game download is provided.
Based on the creator's documentation, checked 8 Oct 2026. Not hands-on tested unless a section says 'We played it'.
How we check