Inventory enhancements
Deploy Promiscuity Auth API / deploy (push) Successful in 47s
Deploy Promiscuity Character API / deploy (push) Successful in 46s
Deploy Promiscuity Inventory API / deploy (push) Successful in 58s
Deploy Promiscuity Locations API / deploy (push) Successful in 44s
k8s smoke test / test (push) Successful in 7s
Deploy Promiscuity Auth API / deploy (push) Successful in 47s
Deploy Promiscuity Character API / deploy (push) Successful in 46s
Deploy Promiscuity Inventory API / deploy (push) Successful in 58s
Deploy Promiscuity Locations API / deploy (push) Successful in 44s
k8s smoke test / test (push) Successful in 7s
This commit is contained in:
@@ -104,6 +104,14 @@ Optional future fields:
|
||||
- slot occupancy must be unique per `(ownerType, ownerId, slot)`
|
||||
- all mutating endpoints should be idempotent where practical
|
||||
|
||||
## Definition source
|
||||
Item behavior is fully data-driven through the `ItemDefinitions` collection inside `InventoryApi`.
|
||||
|
||||
That means:
|
||||
- no hardcoded stack-size rules
|
||||
- no automatic item-definition seeding
|
||||
- item instances can only be created for `itemKey` values that already exist in `ItemDefinitions`
|
||||
|
||||
## Client shape
|
||||
The Godot client should fetch all items for the currently relevant owner and group them into a bag view locally.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user