As of this week, it was found that since v1.1 of the game removed deterministic accuracy, we finally have figured out somewhat how the accuracy mechanic functions now. We're able to say that the accuracy on teeshots and possibly second shots in some scenarios depends fully on stroke count and the iteration of the course you're on. By iteration, I mean how many times you've "restarted from hole 1" after first entering the course.

Every single iteration of a course has the same pattern attributed to it. The notes on the first iteration patterns will be refined and posted as a concise guide here on src/mgsr under guides, once finished. Third iteration and after seem to be relatively unimportant as they offer nothing significant for the amount of time spent to get to them, nor are any good for score attack records.

The weirdness comes from the second iteration, aka restarting from hole 1 once. This costs about 6.5 seconds and does the following: EVERY single teeshot will have the hardest left mishit (right if playing as a lefty), EVERY second shot will have the furthest right mishit, and the third shots will all have some left mishit that is mostly unimportant. The importance of this is that a hard left mishit also maximizes distance, which means that some shortcuts barely possible before are now 100% accessible given good weather. Provided you know exactly how to play a given wind direction with your shot's lie and the known mishit on the frame of power you hit, you could hole out a significant number of times. Yeah, I know, this is utterly ridiculous lol.

I'm not really sure how to go about this on the leaderboard altogether, as a lot of people have worked hard with the presumably random accuracy in mind. For All Courses, it functions as a safety method as using it on all 6 courses will basically eliminate chances of WR already without holing out 12-15 times. For All Birdies, it provides significant timesaves and possibly requires a reroute for playing from Bonny front tees and Rookie tees of other courses. For Score/Time Attack, it could be worth having a column or other descriptor that delineates between this bug abuse and natural/risk mitigation play, as score attack records are bound to be beaten with this method eventually. Let me know your thoughts if you have any on the topic!