About
A standalone, independent Dark Age of Camelot client model-ID reference database - mobs, items, objects and colors. Built as a modern successor to old ID lists such as Metty's ID List / Los Ojos, which have gone offline or become incomplete over the years. This project has no relationship to any DAoC CMS, freeshard admin panel, OpenDAoC or Dawn of Light project - it documents client model IDs, never server-specific database IDs, and this site is only one interface to a plain, downloadable JSON dataset that lives independently of it.
Sources
| ID | Name | Type | Status | Notes |
|---|---|---|---|---|
metty | Metty's DAoC ID List | historical_web_database | offline | Primary historical image source. Recovered from Wayback Machine snapshots of metty.the-bart.org and its Uthgard-hosted image mirror. |
opendaoc_client_gamedata | OpenDAoC client gamedata.mpk (monsters.csv / items.csv) | client_data_export | active_source | Extracted directly from a real OpenDAoC client install's gamedata.mpk (a proprietary MPAK-format archive of per-file zlib-compressed CSV tables, cracked and documented in docs/MPAK_FORMAT.md). This is the client's own authoritative model-name table - the actual generic visual identity of a model ID, as opposed to whatever specific name a given server's content happens to reuse it under. Cross-checked against a live DOL/OpenDAoC-derived server database: 95.4% of that server's live mob Model IDs exist as a row in this table, confirming DOL/OpenDAoC servers generally share this same client ID space. |
dol_opendaoc_server_db | Dawn of Light / OpenDAoC server database | server_database_export | active_source | One-time, offline export of Model->Name->Realm associations from a live Dawn-of-Light-derived server's mob and item-template tables. Used only to seed real, verified client model data, since DOL/OpenDAoC-based servers generally share the same or very similar client model IDs. This project never connects to a live server at runtime and has no ongoing relationship with any specific server. |
community_verification | Community verification | manual | active_source | A contributor confirmed an identification against a live client or reliable secondary evidence. |
manual_investigation | Manual investigation | manual | active_source | Direct research by a project maintainer. |
project_capture | Project screenshot capture | new_media | active_source | A new screenshot taken specifically for this project, per the screenshot standard in docs/DATA_FORMAT.md. |
opendaoc_client_render | Rendered from client 3D model | generated_render | active_source | Rendered directly from the client's own NIF 3D mesh and its real texture files (Blender + the NifTools importer, Cycles CPU, orthographic 3/4 framing - see docs/NIF_RENDER_PIPELINE.md). A render is only ever accepted if every texture the model references was actually found on disk; if even one was missing, no image is produced for that model at all - a placeholder or partially-black render is never published as if it were real. |
community_submission | Community submission | manual | active_source | Submitted through the public submission form by a visitor, and manually reviewed and approved by a project admin through the backend before being merged into the dataset. The original submitted image and metadata are kept in data/submissions.json even after approval, so provenance is never lost. |
Identification status
Verified - checked in DAoC or confirmed from multiple reliable sources (including a direct export from a live server's own database, which is exactly what a running client uses).
Probable - strongly supported but not independently verified.
Unverified - a historic description exists but hasn't been checked.
Unknown - the model ID is catalogued but we don't yet know what it is. This is a valid, permanent, useful state - IDs are never hidden for lacking one.
Invalid - testing indicates the model ID isn't valid or usable.