So, I think the radio button values being obfuscated makes getting a refill worth supporting. Automating it in ASH is much more involved than the single visit_url() needed for the pantogram (unless the radio button values are able to be gotten in a manner more simple than this: https://pastebin.com/BJZyKdkb ).Things I'm not sure if we should support or not:
Recognising which things we've unlocked - as native interface shows it well
Changing setup of Latte mug - like Pantogram it's complex, and native interface works well.
So, I think the radio button values being obfuscated makes getting a refill worth supporting. Automating it in ASH is much more involved than the single visit_url() needed for the pantogram (unless the radio button values are able to be gotten in a manner more simple than this: https://pastebin.com/BJZyKdkb ).
Urgh, the values change every time you visit the page! That's a nightmare! What possible benefit is there to doing that or is it just to mess with scripters?
(Edit - I'd guess it was actually there to stop us learning what all the options were, and stop us brute forcing ones others had discovered. But then it was decided to show them all to make it more user friendly)
But would my values work for you! Given that it'd be much easier if we could use the same code for everyone!The values changing doesn't actually matter. You can use old values and they work just fine (at least this has worked for me since last night).
But would my values work for you! Given that it'd be much easier if we could use the same code for everyone!