[EricH]

I started running through multiple ways to count the score in realtime automatically.

Short version, the current version (weight) is the simplest method for both transport and programming. However, as noted, there is a drawback of settle time and if there's a bit of a force applied.

Now, the 2 short-range sensors with both triggered = score is next simplest in execution, at least for transport. However, instead of both triggered = score, I would set it up to that 1 THEN 2 is a score. You can do that--in fact, it's how balls were counted in 2010 and 2012--and it will be pretty accurate. You can also set it to descore if 2 THEN 1 happens, to account for bounce-out (note that a trigger should be both on and off). But you do have to line the whole goal entrance to some extent.

The toughest method to implement would be an inline counter. Not because it's the hardest to program--it's easier than the above solution--but because you have to get incoming frisbees into line, when they're bouncing and sliding around in there. And that takes space and weight that may or may not be available. Slope (to get them to where you want them) can take a lot of material--and then you have to build in something to stop automode scoring at the end of automode, after a semi-reasonable delay to allow for the settling time.