Does this sound like a good idea to you?
It has been suggested before, and yes it would be a good idea. It would be even better, if the reveal-key-button could be pressed only once for the same game/product: even with the new auto-removal feature, it is possible to win something twice, by manually entering more giveaways for a game you already won. Now, if the button you suggested were implemented, a winner could only reveal one of their multiple wins and had to wait until they can mark their first win "not received" (with a fake giveaway or a bad key for example) before revealing a second key for the same game. That's effectively a queue.
Comment has been collapsed.
1 Comments - Last post 7 minutes ago by m0r1arty
631 Comments - Last post 19 minutes ago by mourinhos86
400 Comments - Last post 1 hour ago by mourinhos86
2 Comments - Last post 1 hour ago by EloyOn
306 Comments - Last post 2 hours ago by SebastianCrenshaw
31 Comments - Last post 4 hours ago by encore94
17,387 Comments - Last post 4 hours ago by wigglenose
1,359 Comments - Last post 11 minutes ago by Chris76de
121 Comments - Last post 46 minutes ago by Trashes
7,039 Comments - Last post 49 minutes ago by LeiteComNescau
284 Comments - Last post 53 minutes ago by igel2005
45 Comments - Last post 1 hour ago by xurc
1,833 Comments - Last post 2 hours ago by Axelflox
724 Comments - Last post 2 hours ago by CBlade
Current System ---
The giveaway creator is able to input a Steam key when making the giveaway. This key may be displayed to the winner of the giveaway by toggling a button to "Show Key," or hidden from the winner by toggling it to "Hide Key."
Suggestion (from UltraTaber) ---
Add a button the the winner's page called "Accept Key" which will then display the key to the winner (assuming the creator has toggled his button to "Show Key"). This is a one-time event, independent of the creator's toggle, and once triggered, cannot be undone. Once the button is pressed, it will be known that the key has been seen and possibly used by the winner.
Benefits ---
Drawbacks ---
Comment has been collapsed.