Abstract
Technological shifts within the video game industry have enabled many games to evolve into platforms for repeated expenditure, rather than a one-time purchase product. Monetising a game as a service is challenging, and there is concern that some monetisation strategies may constitute unfair or exploitative practices which are not adequately covered by existing law. We asked 1104 players of video games to describe a time when they had been exposed to transactions which were perceived to be misleading, aggressive or unfair. We found 35 separate techniques over eight domains: game dynamics designed to drive spending, product not meeting expectations, monetisation of basic quality of life, predatory advertising, in-game currency, pay to win, general presence of microtransactions and other. Notably, several of these reported practices seem to not align with existing UK consumer protection regulations. We discuss this potential misalignment, as well as the implications of identifying what players believe to be problematic monetisation techniques.
You have requested "on-the-fly" machine translation of selected content from our databases. This functionality is provided solely for your convenience and is in no way intended to replace human translation. Show full disclaimer
Neither ProQuest nor its licensors make any representations or warranties with respect to the translations. The translations are automatically generated "AS IS" and "AS AVAILABLE" and are not retained in our systems. PROQUEST AND ITS LICENSORS SPECIFICALLY DISCLAIM ANY AND ALL EXPRESS OR IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES FOR AVAILABILITY, ACCURACY, TIMELINESS, COMPLETENESS, NON-INFRINGMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Your use of the translations is subject to all use restrictions contained in your Electronic Products License Agreement and by using the translation functionality you agree to forgo any and all claims against ProQuest or its licensors for your use of the translation functionality and any output derived there from. Hide full disclaimer






