Keep the number of items lying on the ground in check without losing treasures

After a long fight a level can be covered in loot, and the game slows down or the player cannot tell what is worth taking. Removing items to keep the floor tidy is easy; removing the wrong ones, or one that just appeared, is what players remember. This entry chooses what goes.

Why this works

A cluttered floor hurts both the game and the eye, but players forgive tidying only when it is not spotted. Removing the least valuable and oldest first, and sparing what just appeared or must be kept, makes the cleanup fair and mostly unseen.

When not to use it

Don't remove items in a game where the place is the memory, such as a home or a base the player decorates with finds. There, a missing item is a loss. Offer storage or a button to sweep up, and let the player choose.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 20 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Keep the number of items lying on the ground in check without losing treasures" (read_entry dropped-items-on-the-ground-have-a-cap) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP