Carousel Jumps - Out of XM
The Ingress carousel model is one that we've had ever since the early days of the Classic client.
When building a portal, as you deploy and hit resonator limits, it drops down to the next level of Resonators. When you open the carousel up again, it's back at the Resonator you last selected to begin deploying. This works great, and makes deploying easier than it would be if you had to manually move the resonator carousel.
However, sometimes while you're spamming the deploy button, it suddenly deploys an R2 then tells you you're out of XM. When you cube and restore your energy, it's still looking at that R2, and you have to scroll the carousel back to where you wanted it to be.
Even in the Classic client days, this used to annoy me a bit. However, since we've moved to Prime, a combination of increased inertia in the carousel, and a bug where after recharging the Carousel doesn't jump back to where it should be, it's harder to manually correct the Carousel back to where you want it to be. And we've all had that situation where we expected to deploy two VRS and accidentally deployed a VRS and a CS because we weren't paying attention.
With this latest Resonator Challenge, and the difficulty of having low level resonators when you're building R6s constantly, those accidental low level deploys are even more annoying so it got me thinking:
Should the Carousel stay put when you run out of XM for the given item?
Firstly, I'm in no way suggesting removing the changes due to Resonator limits etc. Those are good, and successfully reset for the next portal. Just the out of XM version.
Secondly, yes, I know this was "In Redacted", but that doesn't immediately make it a good thing, especially given how the Carousel's interactions are a bit different now.
But given that if you chew "enough" XM that you can't deploy your lowest level resonator or mod, the carousel doesn't jump and simply says Out of XM, I'm suggesting that we take the uncertainty out of this situation, by not jumping when XM is low enough for a lower item but not the one you had selected, and just saying "Out of XM".
I'd be interested to hear whether the behavior is important to anyone's regular gameplay. When I asked others, it was always only niche scenarios and 'when rushing' which doesn't really overrule fixing it for the 90% usage case.