this post was submitted on 15 Jun 2024
247 points (86.6% liked)
Games
32958 readers
1973 users here now
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Weekly Threads:
Rules:
-
Submissions have to be related to games
-
No bigotry or harassment, be civil
-
No excessive self-promotion
-
Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
-
Mark Spoilers and NSFW
-
No linking to piracy
More information about the community rules can be found here.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They do prevent you from linking to your own store within your Steam game though. Even though they don't provide a complete solution for things like microtransactions and DLC.
How it works on Steam:
For that Valve wants 30% of in-app/DLC purchases. At that point it's stripe and nothing more. Unlike standalone DLC Or expansions, these unlock purchases don't come with serving any additional content in the form of downloads.
If you make your own service to handle these transactions (with only a 3-4% transaction rate) Valve will prevent you from linking to it, or mentioning it anywhere on your page, forums or within the game itself. You need to direct players elsewhere and then mention it. Even for cross-platform games where having Steam maintain a transaction list for a portion of the users is just a needless additional layer.
I know how Valve's publisher API works, others are similar in case you didn't know. But that is only true for games that need online validation of some sort, DLCs for offline games don't need to implement this.
Valve is hosting the game, providing the storefront and bringing in a lot of customers. If you didn't think those 30% were worth it you would not have put your game on steam.
Plus all of this is irrelevant to the point that Valve doesn't enforce price parity.
For the base game, which I think 30% is still more, I think it certainly makes sense. Because they're providing a complete solution.
For in-app purchases or unlock purchases, whether or not the purchase is in-app, the solution isn't complete, and not worth the 30% they charge on those transactions. It would be trivial for every transaction to have a custom field where you could store an array of what was purchased in in that purchase and have it returned when the transaction was checked. Boom, complete solution. Specifically for in-app purchases if they wanted to take 5% since all they're doing is the job of Stripe and nothing more, then I'd consider that fair.