Are these features related to coupons possible?
What's the intended use case for coupons? I see it as a possible method for selling virtual items / features based on payment processors not currently supported. But things like fraud are a concern too.
It would also be nice to be able to import coupons. So that we can generate them in a style of our choosing.
Is there any security to block brute force attempts to redeem coupons?
Coupons can be generated for any item in your catalog, so that you can use them however you like - emailing to customers for promotions, giving them away at conferences, using them as rewards for contests, etc. We do not currently provide a view of the list of active coupons or check a specific coupon's status, though that is on our backlog for future development.
As with other GUID type systems, coupon codes are a combination of letters and numbers generated randomly. Given that any client hitting the service with frequent requests gets throttled (and potentially blocked if it does it enough), the odds of anyone brute-force finding one within the lifespan of a game make it exceedingly unlikely that anyone would bother trying.
I agree that it's unlikely, but if we could choose to have the codes be made longer it would make people even less likely to bother trying. I'd like a minimum of xxxxx-xxxxx-xxxxx rather than what's now xxx-xxxx-xxx. Being able to import a code list instead of generating for an item would be best case for me.
When a user enters a 0 (zero) in a code does that count as a O (letter)?
Are the codes case sensitive? Making the generated codes all caps by default would be better.
Having i and 1 is problematic. I noticed there are no zeroes, but capital I and 1 can look too similar. I would prefer that only 1 is in the code list, and then have i be accepted. Same with 0/O I would prefer 0 and not O, but allow them to be interchangeable when redeeming coupon codes.
It would be handy to be able to have a string value able to be set as the start of codes generated. This can make them easier to identify. For example: DEX-A4C95-T3Y6N-KUT7S
I'd also like a curse word filter if it doesn't already exist. I can do this manually to prune curse words, but with my own code generation I have seen it happen.
Thanks - the more we hear from folks on things they'd like to see, the easier it is to do our prioritization. I do have to be clear, though - this is the first time we've ever heard this request, so I don't believe it's going to be something we'll be able to prioritize anytime soon. As I see it, you have three requests:
To answer your other questions:
