The concept of an "imbalanced" custom vec - obviously implying that the differential skews in its favour, i.e. it's overpowered instead of underpowered - essentially boils down to it being imbalanced against
stock content; that is stock vehicles and pedestrian weapons alike.
Wanna figure out whether your shiny, new, 100hrs+ developed variant has imbalance issues? There's a very easy and reliable way to test for that: get two people of as
equal skill as possible in every relevant UT skill/discipline together, have one get into said custom vec and the other sequentially go through all the stock content options (fight it in every vec and however they can on foot), and note who wins each duel. Test multiple times and alternate the two players often to control for skill disparity despite previous assumptions. Does your custom vec have a
consistent success rate above 75%? If so, congratulations, you're the proud creator of an overpowered piece of new gear. Is its success rate steadily below 25%? Congratulations again, you're probably the only modder in UT history to've ever produced an underpowered vehicle out of excess wariness.
Why are these watersheds so high and low respectively? One reason is, because not even all stock content is perfectly balanced against each other to begin with (and that's okay). That is typically offset via adjusting each vec's scarcity (scorps and mantas are plentiful, levis are rare) and the resulting [in]frequency of 1-on-1 encounters (scorp vs levi is quite rare, scorp driver won't care much that their chances of winning are slim even on Day One, let alone Year Ten). The other reason is simply because there's no such thing as 2 people of identical skill level. Lastly, because fighting isn't the only way vehicles enable players - there's also speed and location access, and a game designer has to balance for those two as well.
Experience gained over several years of thousands upon thousands of such match-ups will usually iron over those statistical issues and will give ppl a fairly grounded (objective even) sense of how likely a fight in one vec against another would be to go their way
on average. After so many years, I'm willing to bet most people still playing ONS today will agree that the stock loadout is indeed well balanced, with the scorp perhaps being the only low outlier in terms of overall effectiveness (IMO the game's biggest deathtrap, in fact).
So, with all that in mind, is the Falcon overpowered? To my mind, the answer is absolutely, undeniably in the affirmative. Pitch it against any piece of stock content and,
all other things being equal, it will come out victorious over 80% of the time. An average 213 hp/sec of either mid/close-range spread dmg output or steady, scalpel-precise stream from afar, and an agility consisting of nearly-double
at minimum accel rates compared to the common raptor make for a pretty potent combination; and merely adjusting to its pace enough to not be crashing it all over the place while wielding such firepower doesn't constitute
that much of a skill counterbalance, IMO, either. Do people in Falcons get taken out by peds, stock content or lesser custom rides? Sure, all the time. Are there maps where the Falcon doesn't single-handedly decide the match's outcome? Also yes. But if that's the entire basis of one's argument that the Falcon's fine (instead of, say, cumulative death/frag counts across matches and maps), you're pretty much discarding any significant criterion of power balance.
What compounds the problem to the point of repeated discussion is its ubiquity among custom vec maps, both of which can be traced back to a specific server and a specific period during which certain logic checks became woefully absent in favour of an "arms race". I'm sure most of you are familiar with the other, notorious offenders hailing from that same era.
How should the Falcon issue best be addressed? IMO, better than toning down the stats of what's been an entirely derivative vec like that for 5+ years now (as is recently being attempted with the Wasp) will only annoy those who like it and probably confuse the rest coming up against one as well. I believe a better solution is the one we've already implemented with the mino here: keep it as it is, but just gradually phase out the maps where it alone ruins gameplay, either through re-edits that won't contain it or outright removal from the roster. An OmahaBeach version where the Falcon's replaced with a Phoenix is quite possible down the road - although I by no means mean to shit all over Wormbo's current efforts here, this could be months later and simply applied on his pretty broad edit - not to mention sounds much more interesting, considering how more reasonable Solace's winged bob-omb is.
Lastly,
-FuNkY-MoNk-UK wrote:It isn't over powered in my opinion, you have to get quite close to do any real damage. It's speed is the biggest problem, but it's not that hard to take down with a LG and shock combined, 5-6 hits and its gone.[...]
For reference, it only takes the Falcon 3.3 single shots to take a standard health ped out and it can spit those out in 0.462 seconds. How fast can you pull that LG/SR trigger? Also, "quite close" is where the Falcon does most of its real damage too

.
Wormbo wrote:[...]Not paying attention to someone driving a Kraken (or even just a Leviathan) across the entire map and deploying it at the enemy core -
well, tough luck.

[...]
To be fair, something like that can usually happen only during a nearly empty server, i.e. in a 4vs4 at most. Other teammates were probably busy zipping around in the four corners of the map to flip nodes, the bots that might've seen him rolling over didn't give a damn either and that's how he got there unnoticed and unharmed. Camping and chain-spawnkilling everything there seems kinda unsportsmanlike to me, but I doubt that mattered much in the end as his team must've been down one human throughout the match and, I expect, lost. Fittingly enough, that version of RedPlanet is also another case where the Falcon is the dominant vec of the map - not the mino, nor the Kraken. Anyway, matches with so few ppl rarely confer any expectations of quality gameplay, so I don't really see why OP bothered to report it in the first place :/.