Pocket Deal Radar
Search
Player help · official documentation

Heart & Soul EXP Share explained

Understand the key-item EXP Share, held EXP Share S and the documented 100 EXP example before training your team.

Reference: v2.0.6Checked 7 Oct 2026

Two similar names, two different systems

The key-item EXP Share takes priority when switched on. In that state, healthy party members receive experience and held EXP Share S items add nothing. Turning the key item off makes the held-item system relevant again.

Start your diagnosis with the key item, not the item a Pokémon is holding. A benched teammate gaining experience without a held item can be expected behavior. Equally, putting EXP Share S on every teammate does not create an extra reward while the key item is on.

For ordinary team building, choose the system that fits your goal: broad passive training or deliberate training of selected holders. That is an editorial recommendation, not a claim that one option produces the best result under every challenge configuration.

The maker’s 100 EXP example

With the key item on, battlers split two thirds of battle EXP; other healthy teammates each receive 28%. The FAQ gives a full-party example: one battler receives 66 EXP and five others receive 28 each from a 100 EXP battle. A lone healthy Pokémon receives the full 100.

Why the party total can exceed 100

Using those documented example values, the party receives 66 + (5 × 28) = 206 EXP in total. That arithmetic explains why dividing 100 equally between six Pokémon gives the wrong expectation. It is not a separate measured result or a general rounding formula.

With the key item off, half goes to battlers and half to EXP Share S holders. The maker’s one-battler, one-holder example gives 50 each.

These examples describe the documented cases. They do not establish every rounding edge case or the order in which multipliers, caps and other battle modifiers are applied. Use them to recognize the system, not to promise an exact award in every battle.

Choose a training plan before grinding

Bring a new teammate into a working party

First decide whether you want everyone to grow together. With the key-item system, inspect the party after a normal battle and check the new member’s experience bar. You do not need to expose that member to an unsafe matchup just to test whether passive training is happening.

Train one chosen reserve

If you prefer the held-item approach, check that the key item is off and that the intended reserve holds EXP Share S. Look at the award after a battle before committing to a long training session. This catches a configuration mistake early.

Keep challenge rules visible

Write down your level-cap and EXP multiplier settings alongside the sharing choice. If a Pokémon stops progressing, comparing only two experience bars may conceal a rule that you intentionally enabled. The settings guide covers those separate decisions.

Before the Johto League: Route 47 and Lucky Egg

The official FAQ points to Route 47’s ground Lucky Egg: descend through the caves to the water and use an accessible waterfall. It records a 1.5× held EXP bonus and daytime Chansey encounters at 40% on that route.

Separate reaching the area, obtaining the item and selecting the Pokémon you want to train. If you cannot use the needed travel moves yet, make that access question explicit rather than assuming the item is already available to your party.

The held bonus does not answer the EXP Share interaction by itself. Keep the key-item sharing state, held item and challenge settings visible. This guide does not establish a universal multiplication-and-rounding order for every combination, or promise that a benched holder receives a particular final award.

Example: one new teammate needs training before the League. Choose broad party training or the held EXP Share S plan above, inspect the first result, and then decide whether to continue. A route recommendation does not remove the need to check your party’s health and your run’s caps.

Rematches: select the battle variant before using it for preparation

The official trainer reference, checked 8 Oct 2026, separates first battles, rematches and Post-Sinjoh battles. Its location and unlock lines provide a better starting point than returning to each leader’s original Gym.

LeaderRecorded rematch locationRecorded unlock
FalknerCeladon Department StoreAfter reaching Vermilion
BugsyViridian ForestAfter reaching Vermilion
WhitneyGoldenrod Department StoreAfter reaching Vermilion
BrockDiglett’s TunnelAfter defeating him
MistyRoute 25After defeating her
Lt. SurgeRoute 10After defeating him

The selected Johto cards also list a later Saffron Fighting Dojo VIP-room battle after completing the Sinjoh Ruins storyline. Use the tab for the stage you actually intend to face. These examples are a navigation aid, not a complete rematch map or an assertion that every leader shares one unlock.

  1. Pick the leader and confirm the listed unlock.
  2. Open that leader’s matching battle tab and read its party.
  3. Decide whether the goal is a challenge, a team-role check or experience gain.
  4. Set the sharing system deliberately, then prepare for the listed opponent.

Example: you plan to meet Falkner again but consult his first-badge Pidgey and Noctowl roster. The rematch tab describes a different battle. Resolve that reference mismatch before choosing a reserve to train; availability of a rematch does not make it an easy training fight.

For a campaign access question, return to the progression checkpoints. If the actual battle differs because of your run’s options, keep the selected tab and settings in your note. This guide does not claim a fastest EXP-per-minute route, a repeat interval or a guaranteed payout.

Why an older walkthrough can show a different EXP fraction

The official walkthrough warns that it was written for an older version and gives priority to the other, current-build references where they disagree. Use the v2.0.6 FAQ for the sharing numbers on this page rather than blending the two descriptions.

When comparing advice, keep the source version beside the claim. A difference between an old guide and the current reference is a documentation question first; it is not enough to show that the emulator is awarding experience incorrectly.

Check unexpected experience in this order

  1. Confirm your game version against the documentation reference below.
  2. Inspect whether the key-item EXP Share is on or off.
  3. Check the health of the party and which members actually fought.
  4. If the key item is off, inspect held EXP Share S items.
  5. Review challenge settings before treating a different award as a bug.
  6. Repeat one ordinary battle and note the before-and-after experience values.

A useful support report includes the game version, sharing state, party health, battlers, held items and enabled challenge rules. “EXP is broken” leaves all of those possible causes unresolved. Back up your normal save before experimenting with unfamiliar challenge settings.

Train toward the species requirement, not an assumed trade rule

Choose a concrete target before a long EXP session. The maker Pokédex lists Haunter and Kadabra’s non-trade evolutions at level 42, and Machoke and Graveler’s at level 38. These selected thresholds belong to the checked v2.0.6 species cards; they are not one universal level for all former trade evolutions.

Example: your Kadabra is level 35. Training toward the documented level-42 route addresses the evolution objective. Your Onix is a different case: resolve its Metal Coat action in the item-method comparison before spending that session on extra levels.

A level-cap rule can constrain an evolution plan without making EXP Share defective. If your run reaches its current cap before the target level, compare the next progression objective with your existing team roles. Read the exact evolution requirement first, then set the sharing system; do not promise that every reserve will evolve after the same number of battles.

Sources and scope

Primary reference: official v2.0.6 player 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