In sectors with a lot of items like asteroids or hulk debris, the binds for targeting cargo in range often do not work or will select a couple of items and then get "stuck", or one will work and the other will not, making it so you can't go back the other direction.

Affected binds:
/RadarPrevNearestPowerup
/RadarNextNearestPowerup

Pointing your reticle at a specific piece of cargo and using /RadarNextFront still works fine.

I've confirmed this happens with no plugins installed and a clean start of the game, but not in every sector. Good examples of places where this is a problem are Deneb skirmish sectors, pirate Trident sectors, and Hive skirmishes. Where there is a lot of ships, debris, and other junk cluttering the radar.

The RadarNextNearestPowerup command should only ever choose the nearest powerup, not be able to cycle through multiple powerups (well, unless you're moving, in which case the nearest powerup changes). If you're experiencing something different, please let us know how to reproduce it.

We have confirmed that the RadarPrevNearestPowerup does stop working if a powerup is outside your radar range, so we'll need to fix that.

If it was only ever to choose the nearest cargo then why have a RadarPrevNearestPowerup at all?

I've had both functions get "stuck" before but it really depends on the sector. In empty space with just a few items, both of them will cycle through them continuously in opposite directions.

We're going to look a little further into this. Apologies for Ray's tendency to be a little knee-jerk in his assessment of "the code technically works, therefore all is well". We need to examine some commit history about why it was implemented this way.

There's a good chance this was changed a long time ago, from the originally intended "NextNearest", because the prior "select from an array of nearby powerups" didn't functionally work very well when the player was in motion.

I can tell you that it has simply "selected nearest" for a long time. Any variation you've noticed has probably been because you were moving.

Honestly, it might have very well been broken for ages, but it's only a problem I noticed now because we have sectors with hundreds/thousands of useless items to flip through and /radarnext and /radarprev take forever to find a piece of cargo in the unrat Trident sector or botting the Unknown system.

Myself and others sometimes use plugins to work around this (TargetTools, CargoList, etc) but they often stall the client in busy sectors with how many things it has to loop over to find "Fused Composite Plating" or "Textured Vegetable Protein"

It's not a huge bug or anything, but it would be cool if the built-in function worked in a useful way.