Quote: "There are some serious scores on there now! Good work! Emily is a 'Double Lane!' machine lol! Her top score is incredible..."
I tried a few more times, and was doing great, until my blind cat started talking to me and broke my focus.
I hope you are a cat lover Emily, because this one seems to be a fan of yours.
The game was challenging enough, but now that she has set the bar that high, it is almost like the ultimate challenge now.
Unless they have a super power or something, then a beginner is going to need a whole lot of practice to even come close.
I wanted to mention the double score glitch.
I noticed a few other people scores were doubled, and thought, wow that was some coincidence that they got the exact same score again.
Now I know it was a glitch and not a coincidence.
When I submitted my score (2nd place) it gave the failed message so I submitted it again, only to find that it had went through the first time and now appeared twice because of the double submission.
I like how you keep the score there for us to resubmit when the connection fails, but maybe you could change that score check.
It seems your condition being used now of matching our old scores is used to determine if we get to submit, so it would only do greater than ( > ) because that is how you have it coded. (right?)
The trouble is that check is not performed on the resubmit, so the successful score submission that was reported as failed is there to be equal to and defy the > check that was performed.
Maybe the submit/resubmit button can fetch the scores and double check that submission before posting it.
I hope this makes sense, because I have not seen your code obviously, but I think I know how it is getting past it.
Anyway, I hope this helps and ignore me if I am thinking about your code wrong.
Coding things my way since 1981 -- Currently using AppGameKit V2 Tier 1
