Bad steam key from Indie Gala Bundle - Take-Off Mega

[TechnoBotix]

Dear Dev,

I have just attempted to redeem my key from an old IndieGala bundle - Take-Off Mega, purchase date 14/01/2016 and upon activation, it reports Duplicate Product Code.
I would like to know if you revoked unused keys please? If so, if I give you my key could you check it against your list of revoked keys.

Thanks

[AlexRemX]

Hello TechnoBotix,

Sad to know you faced with such issue. Nope, the keys shouldn't be revoked. Unfortunately I haven't technical possibility to grant you new key or something.

[TechnoBotix]

Hi AlexRemX,

Thank you for replying.

[nikadee]

Same problem. I bought the same bundle from indiegala, and then purchased it again during a "happy hour" sale. None of the keys for this game work (the keys for the other games in this bundle work, it is only the keys for this game that don't).

Looks like you guys revoked them.

[AlexRemX]

None of the keys was rewoked by me. Last two years I didn't manage the development and any business with this game at all. However, now it looks suspicious. ```Duplicate Product Code``` means that code is already used, as I know.

If codes was leaked somehow on some level, I'm afraid it will be nearly impossible to investigate that now.

It looks also a bit strange that you guys decided to use that codes after more than 3 years from getting it... Because I didn't faced such complains before.

[TechnoBotix]

Strange or not, I can use my code when ever I want! What I don't expect is the code not to work.
For the code not to work, means that someone else had the same code as me or the developer revoked it.
I have about 3 other developers revoke codes before, hence my initial question.

Fortunately, I did have another code, from the Build a Greenlight Bundle 34, which I purchased 07/11/2015. This worked with no problem.

As for why you haven't faced such complaints before, then maybe other people have not yet tried to redeem their codes!

I can ask around though in the IndieGala and Groupees forums. Maybe you'll get some more complaints

[AlexRemX]

There were a thousands of keys I granted to IG, most of them have been activated during the years, and everything was okay until now. I deleted the keys on my side immediately, just to not get confused. Probably something happened with those parties of keys recently by mistake or because of unscrupulous partners I had - it's hard to say and I can't blame anyone.

That isn't your problems ofc, but I only can say that keys didn't rewoked for sure - I'm not interested in it and it simply pointless to me. I have not been doing any things related to the game for a long time.

And sorry if I touched you with `a bit strange` part, it isn't my business of course.

[GuyWonder22 ♿🎮]

Another piece of dung stealing from people. No matter how long its been or not you were still apart at 1 time and that attitude you take towards customer just screams shady. And yes I have a key also I was saving to gift to person on my own time when I felt the right person needed it. So you have no right to question or dictate what a person does with a item they bought. Only thing you are responsible for is to make sure it works. Period

[ReptilianWorldOrder]

There's a way to find 100% matter-of-fact truth here.

You can ask Steam Support about the key's status. They won't tell you who activated it, but they'll let you know whether it was actually activated (I think when too, if requested), or whether the key was indeed revoked by the developer intentionally.

Steam Support isn't terribly helpful about revokes usually (well, or any complicated issues unless you eventually reach someone higher-up past the automated-FAQ replies and the real-person-automatically-posting-FAQ level), but they're aces when it comes to binary "check-->confirm" sorts of matters.


You'll get your answer for sure, though it might take a few days to get a response since I think it still requires an actual person to confirm. So it's not something I'd ask too often--like trying to find out if any given key I've got is activated already--but it's absolutely ideal for when these real issues do arise.

Originally posted by AlexRemX:

It looks also a bit strange that you guys decided to use that codes after more than 3 years from getting it... Because I didn't faced such complains before.

Gotta say that your comment here screams guilty as ♥♥♥♥ to me, as this is absolutely the go-to rationalization for devs when fraudulently deactivating keys. But there's no point to speculation when an answer can be determined for certain. I'll stick with good-faith and presume benefit of the doubt unless shown otherwise.