## Drop Tables

**The filename is the ID.** A drop table is looked up by its filename stem
(`gem_table.yaml` → `gem_table`); reference it from behaviors/mobs by that name. Do not put
an `id:` field in the file — it is ignored.

Shared drop tables can be referenced by multiple behaviors:
```yaml
# data/drops/gem_table.yaml
drops:
  - item_id: uncut_sapphire
    weight: 47
  - item_id: uncut_emerald
    weight: 16
  - item_id: uncut_ruby
    weight: 4
  - item_id: uncut_diamond
    weight: 1
```

Bird's nest drop table:
```yaml
# data/drops/birds_nest_drop.yaml
drops:
  - item_id: credits
    weight: 50
    quantity: 200
  - item_id: credits
    weight: 30
    quantity: 500
  - item_id: credits
    weight: 15
    quantity: 1000
  - item_id: credits
    weight: 4
    quantity: 3000
  - item_id: credits
    weight: 1
    quantity: 10000
```

Referenced from a gather behavior:
```yaml
drops:
  - item_id: copper_ore
    weight: 90
    depletes: true
  - table: gem_table          # pulls from data/drops/gem_table.yaml
    weight: 10
    depletes: false
```

---