Why We Need Hitscan, and Why MagicChain Just Won't Cut It
So, as all of you are no doubt aware, one of the more controversial changes that has been made in the Tribes PTS is the removal of hitscan sidearm weapons.
As one might expect, there are plenty of pubbies who can't comprehend anything more complicated than an overgeneralisation like "hitscan = no skill". I'm not hoping to convince that crowd of anything; there's no point arguing over pubs since there's bugger all in the way of balance to be had there.
What I do want to do is to make the case as to why keeping hitscan sidearms around doesn't make balancing the PTS more difficult, and why they're necessary for a significant portion of the playerbase, regardless of what HiRez can come up with in terms of improved lag compensation or netcode.
Assumptions
Saying anything about Tribes 'in general' is a risky proposition. Every mechanic in the game is far too complex to sum up in a single sentence or dot point that holds true under every circumstance and every condition... not that this stops people trying.
So for the purposes of this post, I'm only going to consider a very low-level view, of the 'balance' of a single weapon in isolation.
This leaves out consideration of realistic dueling (e.g. multiple weapons, positioning, reloads), let alone consideration of proper comp/pug rule CTF. Trying to consider that stuff would make it impossible to keep this simple.
Part 1: Why hitscan is not a balance problem
The first argument that shows up whenever hitscan is so much as mentioned claims that hitscan is, by some inherent virtue, unbalanced, or 'less skillful' than other weapons. Comparing hitscan to explosive weapons is pointless, anybody who makes this argument on the basis that anything but explosives is easy isn't worth arguing with. The only interesting comparison to be made is between hitscan and chain / 'non-explosive projectile' weapons.
Ultimately, in most respects, the act of balancing a chain weapon is pretty similar to that of balancing a hitscan one. Both have the same main balance parameters:
There are of course many secondary parameters (including reload times etc.), but just considering those listed, the calculations required in balancing a weapon is pretty similar in these categories for both hitscan and chain weapons.
The major difference of course, is that bullets have travel time and therefore require leading. At long range, this acts as a 'natural' or emergent alternative to falloff or spread, since leading accurately becomes exponentially more difficult as distance increases.
As hitscan weapons lack travel time, they therefore require a more aggressive falloff curve, with a hard limit. This has other flow-on effects, but it isn't a particularly tough balancing act, in the scheme of things.
There is an argument that the act of leading itself constituted a 'skill', and that therefore hitscan weapons are inherently less skillful than chain ones. To address that: first off, almost every other competitive FPS would disagree with that notion, since they almost universally use hitscan weapons balanced through some combination of falloff and spread or recoil.
Other games aren't Tribes, though, which brings me to the second point: leading in T:A as it applies to chain isn't a meaningful form of mechanical skill. How much effort it takes to lead depends on distance to some degree, but it is also inherently tied to latency and jitter. In a low-ping, short range duel scenario, almost no leading is required, making chain a 'pure aim' skill, just like hitscan. In a longer range scenario, the effect of leading is overridden by factors outside the consideration of pure weapon balance - positioning and movement, primarily.
In anything but a ping- and jitter-matched environment, though, leading is a mechanic for which the player with lower latency/jitter has an inherent advantage, regardless of skill level. This isn't just true at very high latency, it's true when the difference is between 16 ping and 30 ping.
To summarise: the differences in balance between hitscan and projectile chain weapons aren't significant enough to warrant the removal of hitscan based on the idea that it's easier to balance with chain only.
Part 2: Why hitscan is needed at high ping
Honestly, there's not a lot to explain here. This is just obvious. As mentioned before, chain is incredibly sensitive to latency and jitter, even at the low end of the scale.
In most areas of the world, a significant proportion of the player base is going to have to play with ping above 30, and many are going to have to play with significant jitter. Even within a region, people who otherwise would be capable of amazing chain are held back by latency. Hitscan doesn't truly equalise that; higher ping players are still at a disadvantage. But it helps.
And it's in the inter-region case that this becomes a serious problem. If an AU player wants to play an American pickup or comp game, they can effectively do one of three roles: capper, sniper or hitscan-based offence. With the new PTS, one of those is effectively gone.
Even for EU -> NA (or vice versa), hitscan is the reason inter-region play happens as often as it does. Taking that out is going to isolate regions, and in the long run hurt the playerbase for the game.
Part 3: Why better netcode isn't a solution
Better netcode and improved latency compensation is a great idea. I'm glad HiRez are planning to implement it. I'm used to playing in the 50-80 ping range, and for people in that range, these changes will improve the issues with how dependent chain is on having sub-30 ping.
However, it doesn't constitute a solution to the overall problem of ping dependency. The only way we could ever have truly ping-independent projectiles would be to have them calculated client-side, which is a can of worms in and of itself.
Latency compensation (MagicChain, pre-step compensation, or whatever else) isn't magic. It can improve the experience at higher pings, but ultimately you have tiny, server-side modelled objects moving at very high speeds, in a scenario where precise collision is paramount.
Improved netcode will improve the game experience for a lot of people, but it doesn't obviate the need for some way to at least be viable in a high ping scenario.
Tl;dr
High-ping is never going to be an optimal scenario, and HiRez aren't in any position to make it that way, but the least they can do is not make it actively worse for players with high latency or lots of jitter.
Turning the Colt and Eagle into projectiles doesn't magically solve balance issues with them; it doesn't even affect most of the balance parameters, and the ones it does just have new problems substituted for old ones.
HiRez ought to reverse the removal of hitscan sidearms. With the impulse glitch fixed, and the Colt's ping-dependent rof fixed at ~50 ping rof, very little balancing needs to be done on those weapons. Then, they can instead focus on the things in the game that actually need to be fixed.