The Re-Draw That Taught PUBG’s Prize Team to Knock Twice

The Battlegrounds team did not expect the final chapter of its pre-registration celebration to begin with silence. In early 2022, the team had promised bonus rewards to a handful of lucky Survivors, but several announced winners could not be reached. The envelope did not slam; it sighed. So the team returned with the promised re-selection, a second draw that turned a simple giveaway into a small story about patience, logistics, and the stubborn gap between a name on a list and a prize in someone’s hands.

Looking back from 2026, the episode reads like a time capsule from the era of the pre-registration Invite a Friend event. Winners were randomly selected from players who had received their in-game rewards from that event by January 31, 2022, at 11:59 PM UTC. The re-draw was not a wild card. It was a correction. The previous chosen winners who could not be contacted were no longer eligible, and the team made that clear with the calm tone of someone tidying a table before dinner. No small feat, considering the prize pool involved.

🎁 The Prize Pool That Waited

The rewards were not cosmetic trinkets. They were hardware trophies: an Alienware x15, an Xbox Series X, a PlayStation 5, and a Razer Kraken V3 Hyper Sense. The prize pool waited like a row of silent sentinels under arena lights, each box holding a different kind of victory. For the team, the real challenge was not choosing names. It was making sure those names could become addresses, and those addresses could become delivered boxes.

The claim process was deliberately careful. Personal information such as home addresses had to be collected for reward delivery. Separate related instructions were sent to the winner’s KRAFTON ID. Winners had to send their information to a dedicated promotional inbox before the deadline, and the calendar tapped its foot: March 15, 2022, at 12 AM PDT, 8 AM CET, and 4 PM KST. The clock was ticking, and the team could not simply leave prizes at the door of a username.

📋 The Checklist Behind the Loot

For the winners, the checklist was less glamorous than the loot. The message had to include the PUBG nickname, the nickname used on a social media channel such as Instagram, Twitter, Weibo, Discord, or NAVER Cafe, and an address written in both the winner’s language and in English, plus a phone number. A file attachment was required too: a screenshot of the winner’s character in the main lobby with the PUBG nickname clearly shown. A screenshot including other party members would not be acknowledged. If the current PUBG nickname differed from the one written in the message, the winner had to take a screenshot of the current nickname. There was, as they say, a pause. Then the team moved on to the fine print.

⚠️ The Fine Print That Protected the Drop

The notes were strict because delivery is strict. Rewards would be sent once the required information from every winner was received. Additional costs such as customs duties or taxes could occur. Rewards could not be transferred or delivered to another individual. If a winner did not wish to receive the reward, they had to say so in the message. If the team failed to contact winners, or if winners chose not to receive the rewards, the team would proceed with another re-draw and announce the new selections separately. Winners might also be asked for additional personal information to confirm identification. It was a headache, but a necessary one. A giveaway is not a magic trick; it is a chain of confirmations.

In 2026, the dates are history, and no new claim window has reopened for that 2022 promotion. Yet the story still has a clean arc. The team addressed its players as Survivors, promised a re-selection, and then built a paper trail sturdy enough to carry consoles and headsets across borders. The previous unreachable winners became a footnote, no longer eligible, while the new winners received a second chance to answer. The Battlegrounds team signed off with a simple line: see you on the Battlegrounds. The prize pool, at last, had somewhere to go.",

"language": "en