Community ManagerCareful with rollbacks. By definition, in Agile development, the standard approach is to roll forward and resolve bugs through incremental updates, especially on the backend. Rollbacks are usually avoided unless there is a critical failure that makes the application completely unusable, for example if the app or game goes offline entirely. Whatever went wrong here with the netcode and gameplay hasn’t caused a catastrophic failure. The game is still online, even though it's barely playable right now due to lag and broken mechanics.
From a technical standpoint, broken or unbalanced gameplay doesn’t count as catastrophic, even if many players would think it should. A rollback could also cause major issues with player inventories and live data, which would likely trigger even more outrage. Just look at what happened with Rivaldo when a simple visual bug led to people accidentally exchanging him. That’s why devs may choose to disable parts of the apps temporarily. In the case of FCM, that might mean disabling the market, the store, or Daily Rivals instead of risking a rollback. I’ve never seen them do one.
Also worth keeping in mind, a lot of features in live-service games are shipped under the MVP (Minimum Viable Product) model. That means publishers will often release the bare minimum functional version of the app, then rely on player feedback to fix, expand, or enhance those features. Obviously, a two-way conversation is needed for feedback to actually work. *Cough*.
Anyway, by design and by the framework used, bugs or missing functionality are unfortunately expected. That doesn’t make it right, but that is how the process and the framework work in simple terms.
In my view, Agile is basically a licence to cut corners, so yeah.
One thing that is definitely missing here, and has caused a lot of frustration and anger over the past month, is clear communication. Updates from EA should be happening more frequently.
Like I said (with regard to a VSA rollback), if it’s not that easy (and you make a convincing argument that it’s not) then EA should just communicate that to us and indicate what they plan to do. But creating an update that not only doesn’t fix well-documented points of pain but actually creates new ones deserves more than a “thanks for your feedback” message from EA — it deserves some immediate action. On that I think we all agree.
Yep in most cases its not as easy as rolling back a windows update so keeping FCM with broken gameplay was probably lesser of a headache/evil at least that is how it appears from distance when you are not a part of the dev group.
We wont know until its shared (if they ever will share), to regain the community trust they definitely should be transparent and open a proper feedback channel where you can have a two way conversation
I'd love to get my hands on their test plan and the test summary report to see where it went wrong, and what mistakes not to repeat at my work hahah.
