you are misunderstanding.
I don’t think I am. The issue is not that your system won’t work with regional pricing, it’s that it will not work without it.
I’m saying pick a region for the guideline, if its $5 on that region the game has that refund period. Then apply regional pricing.
Yeah, that’s the issue. Some games do not opt into regional pricing, so the price never gets lowered, which means they will be paying $5 and have, for example, only 1 hour to refund the game, just like someone in the US. Their having to pay $5 is already an issue, and now they have even less time to refund it if it sucks.
There’s zero reason to apply a framework for every region that’s more work then needed.
I never adovacted for this. You can tie the refund period to money paid, no problem. You do not need a different refund period framework for every region, and I don’t understand why you think I’m pushing for this to begin with. It’s fine as long as you enforce regional pricing for everyone, which’s not something Steam will do.
Pika@sh.itjust.works 2 weeks ago
At this point, I’m not sure where our disconnect is. I’m not sure how you read what I sent and somehow got that it forces regional pricing or doesn’t force regional pricing. The framework I’m talking about would not require regional pricing at all because the only price it cares about is what the price is in the chosen region.
The system I’m advocating would work with or without regional pricing because the region’s price doesn’t matter.
As an example, say their chosen region is the US and they decide that $5 means it’s a 30 minute return.
But then they have another region that is two dollars.
It doesn’t matter that it’s $2 in that region because the region that is used for the metric is $5.
So the $2 game that is regional pricing would have the return policy of the $5 game because the region that they use for the calculations has it at $5.
I’m not sure why it needs to be so complicated to have specific return policies for every single region. At the end of the day the value in the framework region is isolated from the framework and no changes to its price would change its return policy as it doesn’t matter
mohab@piefed.social 2 weeks ago
I am not advocating for this. I do not understand why you think I’m advocating for this when I never brought it up.
Please re-read my last comment.
Pika@sh.itjust.works 2 weeks ago
ah sorry, yea I reread it and I can see I misunderstood your position,
as for where I got the concept from:
and then
since my post was about having it be based off a policy on pricing based off the current price, I took that as a message stating that it requires regional pricing to work. So I jumped the gun a little and thought you meant that you were advocating that for it to work, they would need regional pricing on everything as such would require regional based refunds for those areas, but I can see where I got overzealous on that so I apologize.
My opinion is still the same on it though, I think it would be better to implement that system than to not, even if the dev doesn’t participate in regional pricing at all, worst case scenario is it’s a static price with a static return based off the only price available and the buyer would know that going into it. I could see how it could negativly impact the buyer like you said but, if the seller is already not participating with regional pricing, there isn’t much else that can be done to fix that.