@Patricia Moore great question, and honestly a really practical one for your use case — short-range most of the time with occasional long-range bursts is a pretty common deployment pattern.
The honest answer is the MultiNav Pro+ doesn't do automatic adaptive power control the way some cellular or WiFi stacks do. It's not dynamically reading RSSI and throttling TX power on the fly. What you *can* do is set TX power in firmware — so if you know ahead of time that a node is in a dense cluster, you can configure it at a lower output level and save some power, then bump it when you need the range. The AI Firmware Builder in the Dev Hub is actually pretty good at generating that kind of conditional logic if you describe your topology to it.
That said, even at full power the current draw isn't ruinous, and if you're running the Power/Program Kit with the supercapacitor setup you've got enough headroom that it probably won't bite you. But yeah, if battery efficiency is a real constraint for your short-range nodes, manual TX power tiering in firmware is the way to go right now rather than expecting the hardware to figure it out automatically.
Worth posting your specific power budget in the thread too — someone else here may have already implemented exactly this kind of range-adaptive power scheme and could share their firmware approach.
