代码仅遍历数组最后一个元素问题咨询（含碰撞矩形组场景）

Hey Bruno, let’s work through this problem you’re hitting. You’ve got a solid setup with game objects (like trees having separate trunk and branch collision rectangles), but your code’s only picking up the last element in your collision rect array. Let’s break down the most common causes and straightforward fixes:

1. Variable Scope Mistakes (Most Likely Culprit) #

This is the #1 reason for this kind of bug. If you declare your collision rect variable outside the loop, each iteration overwrites it—so by the time you use it, it only holds the last element’s value.

Wrong Example: #

// Variable declared outside the loop—gets overwritten each time
CollisionRect activeCollider;
for (int i = 0; i < treeCollisionRects.size(); i++) {
    activeCollider = treeCollisionRects[i];
    // No collision check here—just updating the variable
}
// Only the last collider is checked here
if (player.getHitbox().intersects(activeCollider)) {
    handleCollision();
}

Fixed Version: #

Move the variable inside the loop, and perform the collision check during each iteration so every collider gets evaluated:

for (int i = 0; i < treeCollisionRects.size(); i++) {
    CollisionRect activeCollider = treeCollisionRects[i];
    // Check collision with the current collider immediately
    if (player.getHitbox().intersects(activeCollider)) {
        // You can even pass the index to handle trunk vs branch differently
        handleTreeCollision(i);
    }
}

2. Accidental Loop Termination #

Check if your loop has a break or return statement that’s cutting the iteration short. For example, if you added a break after the first collision check, you’ll never get to the second collider (like the branch on your tree).

Fix: #

Remove unnecessary break statements unless your logic explicitly requires stopping after the first collision. If you need to handle all collisions (e.g., both trunk and branch), let the loop run through every element.

3. Incorrect Array Population #

If your collision rect array isn’t being filled properly—like overwriting the same index instead of adding new elements—you’ll end up with only the last value in the array.

Wrong Example: #

std::vector<CollisionRect> treeColliders;
// Both assignments target index 0—trunk gets overwritten by branch
treeColliders[0] = createTrunkRect();
treeColliders[0] = createBranchRect();

Fixed Version: #

Use push_back() to add new elements to the array, or ensure you’re using unique indices:

std::vector<CollisionRect> treeColliders;
treeColliders.push_back(createTrunkRect());
treeColliders.push_back(createBranchRect());

4. Collision Logic Outside the Loop #

If you’re collecting colliders in the loop but only checking the last one afterward, you’ll miss all previous elements. Make sure your collision detection logic lives inside the loop so each collider is tested as you iterate.

Quick Check: #

Search your code for where you’re calling the collision check function. If it’s after the loop ends, that’s the problem—move it inside!

Start with checking variable scope and loop placement first—those are the easiest fixes and the most common causes. If those don’t resolve it, double-check how you’re populating your collision rect array to ensure all elements are being stored correctly.

内容的提问来源于stack exchange，提问作者Bruno Filip