elektroAimIsADickUse frame time as the performance metric instead of frame rate (like frames per second or FPS). Frame rate is often misleading.
why are you still on about this
Because it's a prevelant problem in the gaming industry. Frame rate is a worse metric to use for troubleshooting, because the actual frame rate could change while rendering a part of 60 frames.[1][2]
elektroyou claim to want to write a proper "comprehensive" guide but just end up sourcing mastercoms 10 times, are you sure that mastercoms documentation isn't comprehensive enough?
That is a huge overexaggeration. I cite more sources than just mastercoms, like Dell, a college lesson, and some tech articles. The mastercomfig documentation leaves out some tips like chaning DNS servers, finding good servers that don't have high frame time variance, using 30.3ms interp and never 15.2ms, etc.