GreyNovember, on 03 February 2025 - 09:07 PM, said:
Why isn't the Firemoth allowed the same level of acceleration, but top speed is fine?
Was there an actual problem if it started to move back and forth too often?
This was actually addressed almost two months ago. I will post here what I edited into the Leaks post. I simply forgot to add it since this info was released in December.
Dated 12/13/2024 Via Leaks channel in the Cauldron Feedback Discord
Posted by Tiyos
Since this question will be asked a million times.
"In the past you said the Fire Moth would break MWO, why are you releasing it now PGIMan?"
You might remember the week of super speed event queues we did around 4 months back. This was operating as a test to see exactly where things started to break down. One thing we learned was that the real offender against hitreg was more acceleration and deceleration rather than just top speed. The Fire Moth will move 209 kph with full skills + MASC engaged, but it won't have the full mobility you would expect of a 20 tonner(more akin to a Mist Lynx rather than a Locust or Flea). The Fire Moth will also gain a reduced acceleration/deceleration bonus from its MASC. This doesn't mean the mech has no maneuverability, just slightly less than your average 20 tonner. Instead, it will make up for it with its massive top speed.
Sorry about forgetting that bit of info.
TLDR: accel/decel causes game to go wonky if its too much. Not top speed. So has to be reigned in to prevent problems with spaghetti code.
TheMadTypist, on 03 February 2025 - 09:57 PM, said:
I'm intrigued by the activity with Conquest, and I'm pleased that they're testing in event queues. Perhaps game-mode research for a potential MWO-2 default game-mode?
Nothing to do with MWO2.
If you have a conquest match with drop decks it usually ends before you get through half of your drop deck. At least thats been my experience in the past.
Edited by Moadebe, Yesterday, 10:18 PM.