Trung Le

Different reason but the same issue with #115 I'll take a look

I tested the `epicgames-client` client, it seems to work just fine for normal games. However, for mystery games, it will require a param `captchaToken`. Without this, it will return 400...

After some debugging, seems like the freebies now have hcaptcha built in to the checkout method, init with `https://talon-service-prod.ecosec.on.epicgames.com/v1/init`  Well, I think we cannot use `epicgames-client` anymore.

> @jackblk Even for one account? yeah, for all freebies

> Picked up manually there was no hCaptcha Because hCaptcha sees you as a normal person on a normal browser, not a bot. We purchase by requesting directly to server....

> I don't see any captcha on my end. I tried both browser and EFC. But I still don't know why I get `We could not confirm your purchase at...

@Revadike I think we should just fix the wrong message first. I've checked the code and I think it's an easy fix in epicgames-client. Maybe we will catch the error...

@Revadike I doubt that they will remove captcha in the future. Well, either we discontinue this project or we find a way to avoid the captcha. I think that @vogler...

@Revadike instead of using `history.json` we can check in the account via client, func `findActiveEntitlementByName` or get all with `getEntitlements`

> I only need to press place order, no captcha or anything The captcha is implemented in the API call. It does the calculation to see if you're a robot...