This is an easy fix, just didn't think about the value of reading to more than one index at a time, so didn't add it.

This behavior would also be consistent with what happens when a player is within range of more than one index.