Redeemable Codes Warning

[Immolation]

You made me smile. Thanks.

[Colloray]

wats a redeem code?

[Dragoon1140]

wats a redeem code?

A redeem code, which can be obtained by winning various PVP events or by donating money, is a special series of numbers that, when used by the owner, give somebody rare cards, unique card art, or Electrum.  They can only be used once.

[nerd1]

this thread is awesome it should totally be in the humor section 

[ZephyrPhantom]

Factual yet entertaining. Good for a quick LOL.

[Sir Rebrl]

+2 points to my night for the quick laughs here. Well done. Everyone loves information disguised as humor. ^_^

[yee]

Note to self:
If I ever get another reward code, only use it in computer with good internet!

Realy funny post from Zanz

[Jyiber]

If you look very closely between the lines of humor you can barely make out the passive-aggressive cover that's concealing the vast well of seething frustration filled with all the help requests Zanz has ever gotten...

This would actually be a great disclaimer to attach to the actual thing. That's as good as saying "the developer is not responsible for general stupidity, bad luck, freak accidents, or cats in the 3 second time period between clicking this and this."

[xchronox0]

As for the validation before and after, I was thinking about a system that communicates to the system before, so that the system knows the account that is about to use the code so that it will not allow any other account to use the code. Then after the reward is chosen it communicates which reward is chosen so the server can easily keep track of the number of 'before validations' and 'after validations'. If your computer broke in between these phases you simply log in once again to your account, use the same code (it's still valid because the reward has not been given, but it's already limited to your account) and then you can choose the reward and finish the process. Thus using multiple accounts could not be abused, but I'm not sure if it leaves other forms of abuse possible... quite likely, I'm not an expert.

Hmm... other solution would be to validate the code not after you write it in, but after you choose the reward... probably something is wrong with this one too, maybe gold is given before the nymph is chosen, that would break the whole thing...

oh, I guess I'm just thinking too much.

[/end of Xinef-specific-similar-to-sarcasm-thingy]

Or, a really easy way to do it, would be prompting the user again if they have not claimed their reward from said giftcode/oracle, after logging back in.
This is the ONLY game I have ever seen with this problem.
But I guess I shouldn't expect anything beyond effort for this game.

[iancudorinmarian]

As for the validation before and after, I was thinking about a system that communicates to the system before, so that the system knows the account that is about to use the code so that it will not allow any other account to use the code. Then after the reward is chosen it communicates which reward is chosen so the server can easily keep track of the number of 'before validations' and 'after validations'. If your computer broke in between these phases you simply log in once again to your account, use the same code (it's still valid because the reward has not been given, but it's already limited to your account) and then you can choose the reward and finish the process. Thus using multiple accounts could not be abused, but I'm not sure if it leaves other forms of abuse possible... quite likely, I'm not an expert.

Hmm... other solution would be to validate the code not after you write it in, but after you choose the reward... probably something is wrong with this one too, maybe gold is given before the nymph is chosen, that would break the whole thing...

oh, I guess I'm just thinking too much.

[/end of Xinef-specific-similar-to-sarcasm-thingy]

Q - Could you please just check my account history and find evidence that, in fact, I did not eventually get my reward?
A - I could, but it would take me 20 minutes... That means I am not going to do it.

Q - But...
A - No.

I guess the answer is pretty clear.

[xchronox0]

Q - Could you please just check my account history and find evidence that, in fact, I did not eventually get my reward?
A - I could, but it would take me 20 minutes... That means I am not going to do it.

Q - But...
A - No.

I guess the answer is pretty clear.

You misunderstood his post.
He was suggesting an automated solution, as every single other game in existence has done.

[Xinef]

You misunderstood his post.
He was suggesting an automated solution, as every single other game in existence has done.

Not exactly "every single other game in existence", since only a small fraction of games in existence actually have redeemable codes, and still not every one of them has the problem solved optimally.

Yes, it's true I was suggesting an automated solution, but it's important to note that actually adding an automated solution to an existing system does require some work, so Zanzarino's point still stands in a way. That's why I was simply suggesting some solutions, rather than complaining or making demands or something.

And quite importantly - you do realize you're quoting three year old posts? I'm not totally against necroposting, but only if you've got very good reasons to do so. I see you did make a suggestion:

a really easy way to do it, would be prompting the user again if they have not claimed their reward from said giftcode/oracle, after logging back in.

but this isn't really a solution to the problem - it's just one obvious part of it. It's just a description of what should happen on the user's side. The important question is what should happen on the server's side to prevent abuse, and how should the server communicate with the client, when you assume that communication can be faulty (there's a chance of messages not reaching their target or reaching it in the wrong order etc.)

So, in my opinion your suggestion wasn't good enough to justify a three year old necropost. Unless I misunderstood your suggestion and you actually have an idea how it should work on the server side, and how to easily implement this, in which case I'm sorry for doubting you