All item IDs are server IDs. Graphics are for client 854.
Total items: 10561
| otb id | name | img | lightinfo | minimap color | wiki | description |
|---|---|---|---|---|---|---|
| 10484 | a closed door | none | - | |||
| 10485 | an open door | none | none | - | ||
| 10486 | a limestone window | none | - | |||
| 10487 | a limestone window | none | - | |||
| 10488 | a limestone window | none | - | |||
| 10489 | a limestone window | none | - | |||
| 10490 | a limestone window | none | - | |||
| 10491 | a limestone window | none | - | |||
| 10492 | pavement | none | - | |||
| 10493 | pavement | none | - | |||
| 10494 | pavement | none | - | |||
| 10495 | pavement | none | - | |||
| 10496 | pavement | none | - | |||
| 10497 | pavement | none | - | |||
| 10498 | pavement | none | - | |||
| 10499 | remains of a water elemental | none | none | Something is wobbling inside. Maybe with a fishing rod you could reach it. |
||
| 10500 | remains of a water elemental | none | none | It has already been emptied of the treasure it held. |
||
| 10501 | unnamed item | none | - | |||
| 10502 | a engraved wedding Ring | none | none | - | ||
| 10503 | a wedding outfit box | none | none | - | ||
| 10504 | unnamed item | none | - | |||
| 10505 | unnamed item | none | - | |||
| 10506 | unnamed item | none | - | |||
| 10507 | unnamed item | none | none | - | ||
| 10508 | unnamed item | 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.