All item IDs are server IDs. Graphics are for client 854.
Total items: 10561
| otb id | name | img | lightinfo | minimap color | wiki | description |
|---|---|---|---|---|---|---|
| 2116 | a rocking horse | none | none | - | ||
| 2117 | a rocking horse | none | none | - | ||
| 2118 | a rocking horse | none | none | - | ||
| 2119 | a rocking horse | none | none | - | ||
| 2120 | a rope | none | none | - | ||
| 2121 | a wedding ring | none | none | - | ||
| 2122 | an elven brooch | none | none | - | ||
| 2123 | a ring of the sky | none | none | - | ||
| 2124 | a crystal ring | none | none | - | ||
| 2125 | a crystal necklace | none | none | - | ||
| 2126 | a bronze necklace | none | none | - | ||
| 2127 | an emerald bangle | none | none | - | ||
| 2128 | a crown | none | none | - | ||
| 2129 | a wolf tooth chain | none | none | - | ||
| 2130 | a golden amulet | none | none | - | ||
| 2131 | a star amulet | none | none | - | ||
| 2132 | a silver necklace | none | none | - | ||
| 2133 | a ruby necklace | none | none | - | ||
| 2134 | a silver brooch | none | none | - | ||
| 2135 | a scarab amulet | none | none | - | ||
| 2136 | a demonbone amulet | none | none | - | ||
| 2137 | golden fruits | none | none | - | ||
| 2138 | a sapphire amulet | none | none | - | ||
| 2139 | an ancient tiara | none | none | - | ||
| 2140 | a holy scarab | 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.