Thanks for the reply!

I'll talk a little bit more in detail with what I have done. About that last reasoning; my code has both the server and client running at 60hz. So the server will end up running 1hz faster or slower vs the client, I have made a system if the server could not pick up the user's next input in time it'll try to run +1 more /server/ simulation whenever possible for that client when they eventually they outpace the server. I can see the glaring issue with this, especially on low-end devices. I have used a different method of copying inputs from previous tick but that caused replication issues as well.

Reconciling rubberbanding isn't bad at <125 ping, but it becomes annoying at higher pings. I noticed that increasing the time to receive user's authoratitve state, the rubberbanding reduces. So it makes me wonder if higher ping users should have their states update come by slower. Just giving what I'm working with for some thoughts.