Skip to content
This repository has been archived by the owner on Jun 25, 2021. It is now read-only.

Suggestion: Improve redemption amount parsing #4

Open
raytech70 opened this issue Mar 24, 2021 · 2 comments
Open

Suggestion: Improve redemption amount parsing #4

raytech70 opened this issue Mar 24, 2021 · 2 comments

Comments

@raytech70
Copy link

raytech70 commented Mar 24, 2021

Hi, nice work!

Instead of the last three digits being the payment amount, can you maybe do it like this:

12#45#7#

Whereas the # is the three digits used to specify the amount? That way multiple card redemptions won't look suspicious.

Hope you have the Google Play part ready soon! The plugin I was using yesterday no longer works and it's frustrating.

Modder Paul Scambaits is my YouTube and Twitch channels if you are interested... funny stuff!

--Ray

@maxichrome
Copy link
Owner

maxichrome commented Mar 27, 2021

Hi Ray!

Thanks for checking out the repo & showing it in action in a video! This was a little "weekend project" I did about two years ago & just restored the Target extension's functionality a few weeks ago. I'm definitely looking to get other features working again soon, but it isn't a major priority for me at the moment as I've had to spend a lot of time working on code for actual work things.

Re: Google Play, it's absolutely something I'd love to get working well, and it's just a matter of finding the time to sit down and do it.

Thanks so much for your support! I look forward to making some improvements as time goes 🎉

@raytech70
Copy link
Author

raytech70 commented Mar 27, 2021 via email

@maxichrome maxichrome changed the title I love the Target redemption but have a suggestion Suggestion: Improve redemption amount parsing Mar 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants