All item IDs are client IDs for 854.
Total items: 10378
| cid | name | img | lightinfo | minimap color | wiki | description |
|---|---|---|---|---|---|---|
| 10450 | a undead heart | none | none | - | ||
| 10451 | jade hat | none | none | - | ||
| 10452 | a terramite shell | none | none | - | ||
| 10453 | a terramite eggs | none | none | - | ||
| 10454 | a terramite legs | none | none | - | ||
| 10455 | a lancer beetle shell | none | none | - | ||
| 10456 | a sandcrawler shell | none | none | - | ||
| 10457 | beetle necklace (speed +2) | none | none | - | ||
| 10458 | a dead lancer beetle | none | none | - | ||
| 10459 | a dead lancer beetle | none | none | - | ||
| 10460 | a dead lancer beetle | none | none | - | ||
| 10461 | a dead lancer beetle | none | none | - | ||
| 10462 | unnamed item | none | none | - | ||
| 10463 | unnamed item | none | none | - | ||
| 10464 | unnamed item | none | none | - | ||
| 10465 | unnamed item | none | none | - | ||
| 10466 | unnamed item | none | none | - | ||
| 10467 | unnamed item | none | none | - | ||
| 10468 | a part of a giant stone dragon | none | none | - | ||
| 10469 | a part of a giant stone dragon | none | none | - | ||
| 10470 | a part of a giant stone dragon | none | none | - | ||
| 10471 | a part of a giant stone dragon | none | none | - | ||
| 10472 | a part of a giant stone dragon | none | none | - | ||
| 10473 | a part of a giant stone dragon | none | none | - | ||
| 10474 | a part of a giant stone dragon | none | none | - |
If wiki links get '?action=raw' appended to them, there's "| itemid = NNNN" inside. This means we can map more directly to the data in the wiki, especially in the db dump. The item IDs are comma separated.
Item IDs are also on a dedicated page, too which shows how it's dynamically computed: by specifying `| includes= {Infobox Object}:itemid` inside a `DPL Table`.
A dump is on nas. It's a 60mb .xml.7z with one 200mb .xml inside with all pages, which should therefore be individually processed and categorized.