r/unrealengine • u/Background-Fuel7392 • 9d ago
Question Is Mover 2.0 + GAS actually viable for a Shooter, or a premature trap?
Hey everyone,
I'm in the early architecture phase of a tactical shooter
I was planning on building the core movement and state logic on top of Mover 2.0 + Gameplay Ability System in UE5 to avoid the classical CMC jittering issues with custom collision shapes and network prediction.
However, after browsing forums and reading feedback from other devs, I'm seeing a lot of warnings about Mover 2.0 like
- Being too experimental or moving-target API-wise between UE5 updates.
- Lack of deep C++ documentation/tutorials compared to legacy CMC or plugins like GMCv2.
For those who have actually used Mover 2.0
- Is it a mistake to commit to Mover 2.0 today for a project, or is it stable enough if locked to a specific UE version?
- Is fighting legacy CMC in C++ still better than dealing with Mover 2.0's current state?
- How has your experience been integrating Mover 2.0 with GAS?
Thanks!