Pixelmon Pasture

Pixelmon Pasture 0.3.1 — Pokémon Duplication Hotfix

Fixed

• Fixed a serious issue where retrieving a Pokémon from a Pasture could duplicate the Pokémon.
• Removed incompatible calls to Pixelmon's PlayerPartyStorage.sendClientUpdatePacket() method.
• Deposit and retrieval now rely on the supported party-storage operations and Pixelmon's save handling.
• Pasture's existing synchronization system continues to refresh the GUI after Pokémon are moved.

Why This Was Changed

Pixelmon Pasture was attempting to call:

PlayerPartyStorage.sendClientUpdatePacket()

That method is not available in the version of Pixelmon being used by the mod.

During retrieval, the sequence could become:

Pasture → Pokémon added to party → invalid method called → exception → Pasture never cleared

This left the returned Pokémon in the player's party while the original Pokémon data remained stored inside the Pasture, allowing the same Pokémon to be retrieved again.

Changed

• Removed the incompatible manual Pixelmon party-update call from Pokémon deposit.
• Removed the incompatible manual Pixelmon party-update call from Pokémon retrieval.
• Party changes are still marked for saving.
• Pixelmon Pasture's own server/client synchronization continues to update the Pasture interface.

Unchanged

The production and balancing features introduced in 0.3.0 remain intact, including:

• Configurable production times and output amounts.
• 20-minute default production cycle.
• Wooloo's configurable multi-wool harvest.
• Wheat Seed requirement for egg production.
• Producer-specific configuration.
• Improved GUI scaling.
• Atomic output insertion protection.

Compatibility

Minecraft 1.21.1 • NeoForge 21.1.x • Pixelmon 9.3.x

Client and server installation required.

Important

Because this fixes a Pokémon duplication issue, 0.3.0 should be considered superseded by 0.3.1 and should not be used once 0.3.1 passes testing.