CompleteWorldItemDrop: Difference between revisions
Document upcoming 0.1.9 custom native keys, shared doors, server Lua callbacks and persistence; not a release |
Release 0.1.9 / BUILD264 / Protocol42: availability and download setup; preserve experimental limits |
||
| Line 3: | Line 3: | ||
<!-- customkeys019:start --> | <!-- customkeys019:start --> | ||
'''Available from 0.1.9 | '''Available from 0.1.9. Use matching updated server and clients.''' | ||
== Custom-key persistence owner == | == Custom-key persistence owner == | ||
Latest revision as of 13:26, 20 October 2026
completeWorldItemDrop
Available from 0.1.9. Use matching updated server and clients.
Custom-key persistence owner
completeWorldItemDrop(playerId, objectId, committed) returns a boolean. For custom keys, only the resource that registered the key and received the pending onWorldItemDrop request may settle that exact player/object reservation. Ordinary-item persistence still belongs to gothic_rp. True commits publication; false cancels and rolls back live inventory where connected. Duplicate/wrong-owner completions fail. Do not remove inventory a second time. See transaction and recovery requirements.
Player/object IDs are positive numeric integers; committed is a boolean. This existing settlement primitive becomes usable by custom-key defining resources from 0.1.9. A true return means the requested settlement was accepted, including when committed=false requested cancellation. A false return means it was rejected.