Let the way a creature dies change what it leaves behind

A deer killed by fire should not drop a perfect hide, and one that drowned should not come with fresh meat. Small rules like these make a survival world feel physical, but they can easily delete drops that should remain, or apply in the wrong order and produce items that make no sense.

Why this works

Players believe a world when the way they act leaves a mark on what they get. A fixed order of small steps keeps each rule easy to read, and it stops two rules from undoing or doubling each other.

When not to use it

Skip it when every creature should give the same reward, or when players could be tempted to choose a weapon only for the better drop and ignore everything else. Keep drops fixed, and reward style in other ways.

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 "Let the way a creature dies change what it leaves behind" (read_entry how-it-died-changes-what-it-drops) 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