Target Cycling
Targets cycle both ways: Tab forward, Shift+Tab back.
What: Targets cycle in both directions now, Tab forward and Shift+Tab back, and the same split on the shoulder buttons. The input took two attempts. At first, letting go of Shift while still holding Tab counted as a fresh press, so the target jumped when nothing had been pressed. The controller version was worse: holding the button down made it race through every target on screen. Both behave now. The other half is what happens when the selected target ducks behind something. They used to drop out of the list, everything after them shuffling up, so the next press landed on someone completely unrelated. They hold their place while they are out of sight now, greyed out until they can be seen again. Cycling away from them on purpose still drops them, which is the point.
Why: A list that rearranges itself while it is being used is hard to learn.
Follow the build: get the updates by email, or see everything about NULLWEAVER.