1.6 KiB
1.6 KiB
Item Type Template
This page is the practical template for the current plugin-driven item architecture.
Plain-English Flow
When adding a new item type:
- Server item package
- Add
server/app/items/types/<item_type>/with:definition.pyfor metadata/constantsvalidator.pyforvalidate_update(item, next_params)actions.pyforuse_item(item, nickname, clock_formatter)plugin.pyfor registration
- Server plugin file
- Add
server/app/items/types/<item_type>/plugin.pyexporting:typeordermodule
- Shared type acceptance
- Item type ids are string-based in protocol/state models.
- For generic new types, no enum/union list updates are required.
- Client runtime behavior (optional)
- Default: no item-specific client module needed.
- Add
client/src/items/types/<item_type>/behavior.tsonly if this item needs custom client runtime UX/audio logic (for example piano mode).
That is enough for a first working item type.
Reference Sample Folder
See docs/examples/item-type-sample/ for a complete copyable folder.
Minimal plugin.py Example
from ..plugin_helpers import build_item_module
from . import actions, definition, validator
ITEM_TYPE_PLUGIN = {
"type": "counter",
"order": 25,
"module": build_item_module(definition, validate_update=validator.validate_update, use_item=actions.use_item),
}
Checklist Before Commit
- Add/adjust server tests for
useandupdatevalidation. - Run
cd server && uv run --extra dev pytest. - Run
cd client && npm run lint && npm run build. - Update
docs/item-types.mdanddocs/item-schema.mdif behavior/defaults changed.