claude
050b8251a7
ci / verify (push) Successful in 48s
Four always-on-screen slots, items as data, and loot tables on enemies and bosses. Health potions drop rarely from trash and always from the Warden; the Warden also drops a Warden's Ration, one per living player, which does nothing at all. The ration is not filler. Player-instanced loot is a separate code path from shared loot -- a distinct entity per owner, filtered per peer in the snapshot encoder -- and the cheapest way to keep that path honest is to have something in the game that exercises it on every boss kill. Item actions ride the input frame rather than becoming new client messages. InputFrame gained BTN_USE, BTN_DROP and a slot byte, which buys the packet-loss redundancy, the replay guard on last_input_tick, ordering against movement on the same tick, and a rate limit of one action per tick -- all of which a separate RPC would have needed bolted back on. The cost is that anything in the frame which must not repeat has to be edge-triggered, since frames are resent and a starved server coasts on the last one it holds. Instanced loot is enforced in NetCodec.encode_snapshot, beside the actor interest radius: a peer is never told another player's copy exists. Hiding it client-side would have been the same mistake as relying on fog to hide enemies. Inventories live on the character and are written to the store on every transaction, so a crash between "picked it up" and "wrote it down" cannot lose or duplicate an item. Anything dropped becomes world-shared whatever it was before, and a potion used at full health is refused rather than spent. tools/diag_loot.tscn covers drop -> snapshot -> pick up -> persist -> use -> drop plus both visibilities on the wire, for the same reason diag_progression exists: bots are poor shots and almost never produce a drop. It asserts each input frame was actually consumed, after an early version silently dropped its first press and every later check passed for the wrong reason. check.sh clean, 266 tests, SMOKE PASS, all three diagnostics green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
31 lines
1.4 KiB
GDScript
31 lines
1.4 KiB
GDScript
class_name ItemDef
|
|
extends Resource
|
|
## Data-only description of an item, in the same spirit as [EnemyDef]: adding an
|
|
## item is a table entry in [Items], never a branch in the simulation.
|
|
##
|
|
## Items are deliberately thin. A slot holds an id and nothing else -- no
|
|
## charges, no durability, no stack count -- because everything the game
|
|
## currently needs is expressible as "one id per slot", and the wire format,
|
|
## the persistence record and the UI all get simpler for it. When something
|
|
## needs a count, add it here rather than teaching four layers about it.
|
|
|
|
enum Effect {
|
|
## Consumed and does nothing. Not a placeholder: the boss ration exists to
|
|
## prove the player-instanced loot path works end to end, and it can only
|
|
## do that if using it is a real, observable transaction.
|
|
NONE,
|
|
## Restores [member effect_value] percent of MAXIMUM health, so a potion
|
|
## keeps its value at level 15 instead of becoming a rounding error.
|
|
HEAL,
|
|
}
|
|
|
|
@export var id: StringName = &"item"
|
|
@export var display_name: String = "Item"
|
|
@export var effect: Effect = Effect.NONE
|
|
@export var effect_value: float = 0.0
|
|
## Index into the renderer's item icon table. Same idea as [member
|
|
## EnemyDef.visual]: the simulation never learns that art exists.
|
|
@export var visual: int = 0
|
|
## HUD tint. View-only, kept here so one table describes the whole item.
|
|
@export var tint := Color(0.85, 0.85, 0.9)
|