OnPlayerConsumableUse
Jump to navigation
Jump to search
onPlayerConsumableUse
LEGACY NAME — NOT EMITTED BY THE PRODUCTION SERVER
This page previously described a callback that is not connected to the production consumable pipeline. Do not register new code for
onPlayerConsumableUse.The old signature covered only a legacy mana-result payload and did not represent food, health restoration, periodic effects, or the current two-stage durable inventory transaction.
Replacement from update 0.1.3
Use the callback that matches the information your server resource needs:
- onPlayerConsumableDurablySettled — the primary read-only success callback after inventory and the final authoritative snapshot are durable.
- onPlayerConsumableEffectTick — each successfully applied, non-zero health or mana tick from a periodic consumable.
- onPlayerConsumableCommitRequested — advanced stage-one persistence lifecycle notification.
- onPlayerConsumableFinalizeRequested — advanced final-snapshot persistence lifecycle notification.
- onPlayerConsumableDetachedSnapshot — advanced disconnect-recovery lifecycle notification.
The last three callbacks are transaction infrastructure owned by the bundled gothic_rp resource. Other resources may observe them, but must not remove inventory, apply progression values, or attempt to acknowledge the transaction.
There is no one-to-one server-side rejection callback under the legacy name. Pre-validation rejection and the client-visible result remain part of the authoritative native protocol rather than this Lua event.