Pokemon TCG Pocket's Trading Feature Faces Backlash, Prompts Developer Response
DeNA, the developer of Pokemon TCG Pocket, has pledged improvements to the game's recently implemented trading feature following significant player criticism. The controversy centers around the perceived high cost and restrictive nature of the trading system.
High Cost of Trade Tokens Fuels Player Discontent
Introduced on January 29th, 2025, the trading feature allows exchanges of 1-4 Diamond and 1-Star rarity cards from Genetic Apex and Mythical Island booster packs. While welcomed by players aiming for Pokedex completion, limitations – specifically the restricted card selection, introduction of a new in-game currency (trade tokens), and the high cost of trading – have sparked widespread negative feedback.
DeNA acknowledged the player backlash on February 1st, 2025, via a Twitter (X) post, stating they are actively exploring solutions. One planned change involves providing alternative methods to acquire trade tokens, potentially through in-game events. Currently, obtaining tokens requires sacrificing higher-rarity cards, creating an imbalance where acquiring enough tokens to trade even a 4-Diamond card necessitates discarding numerous other valuable cards.
DeNA justified the stringent rules as a measure against bot abuse and multi-account exploitation, aiming to maintain a fair and enjoyable card-collecting experience.
Genetic Apex Booster Pack Accessibility Concerns
Further complaints surfaced regarding the release of Space-Time Smackdown booster packs on January 29th, 2025. Some players reported the disappearance of Genetic Apex packs from the main screen. While this was clarified as a UI issue – the older packs are accessible via a less prominent "Select other booster packs" option – the poor visibility led to significant player concern and speculation about the removal of the original booster pack.
Although potentially a marketing oversight, players suggested improving the home screen display to showcase all available booster packs, preventing future confusion. DeNA has yet to directly address this specific UI issue.
