So, we’ve currently got an issue with bowling balls (happens about 1/50) where the ball decides to go on a different angle than what you’re aiming at. I’ve attached a youtube video showing the issue below and the ball causing the issue.
I sent you a discord request. I managed to replicate it once and I think I solved the issue, though I am not sure because it took my over 70 attempts to get it to bug out the first time.
Ah that makes sense too. You definitely don’t want to be switching mid-air. You’d probably pick this up in studio if you use Test Server instead of Play Solo and increase the simulated network delay to something large like 1 second. That’s how I find most of my network-related bugs before publishing.
I only use Play Solo because it doesn’t take half a lifetime to start, and there isn’t much difference even when with dealing with network (unless you are trying to make something physics based).
Eyup, seems fixed. Just ran it for the last 3 minutes with an autoclick simulator with 2 detector parts that sandwich a 3rd detector part. The middle one detects correct passes and the ones on the sides the faulty ones. All of them passed through the middle.
This is not appropriate use of the Scripting Support category. Commissions, even for fixes, should be placed in #public-collaboration:public-recruitment especially when monetary compensation is involved. Scripting Support is not a venue for you to dump your broken assets and have people fix it for you: it’s for requesting help on fixng it yourself.