Promote CHANGELOG Unreleased → 0.10.0 (the schema-driven Build page for world
objects, #11) and bump wally.toml + SurvivorCore.VERSION.
Demo: new demo/server/Stage.luau — one switch for what the demo places in the
world (gather field + quest post, mobs, starting inventory, hand-test props).
The test-station prop rows now default OFF: they're scaffolding for working ON
the engine and crowded the spawn area for everyone else.
Collateral: the Build demo video on the docs Demos line and as an 8th site
video tile; the landing page's Studio card now tells the Build story; version
surfaces bumped across site, README and getting-started.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Found in real use: with no gatherables authored yet, the Build form's Resource
field has no ⌄ picker (there's nothing to cycle) and nothing explains where
entries come from — so the very first no-code run dead-ends at the moment the
flow should feel best.
A field that references authored content now shows "No Gatherables yet —
create one →" when that category is empty, which jumps straight to the right
Content page. Not a mutation, so it isn't wrapped in a ChangeHistory recording.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Found by an adversarial review of the Build page before it was ever run — all
three reviewers independently flagged the first one.
1. The "what is this object?" cards were dead. chooserCard parented a
Size=fromScale(1,1) TextButton into Theme.panel() intending an overlay, but
Theme.panel() contains a UIListLayout, which lays out EVERY GuiObject child —
there is no opt-out, and ZIndex does not affect layout. So the button became
another list row: clicking a card's title/summary did nothing, and the
oversized button spilled past the card and took the click for the card BELOW,
applying the WRONG component (which also strips the previous component's
attributes). This was the page's primary interaction.
Fixed with Theme.panelButton() — the card itself is the button, matching the
pattern OverviewPage already uses.
2. Clear did nothing on an object whose only tag was unknown to this engine,
yet reported success. The page renders exactly that branch with a Clear
button. BuildAdmin.clear now takes the tags to remove explicitly, and the page
passes the unknown tags it just displayed — never removing an unlisted tag
speculatively, since it may belong to another plugin. It also reports
"nothing to clear" instead of a false success.
3. FieldRow's help text set Position inside a UIListLayout parent, so its indent
was silently dropped and every help line rendered flush left. Uses padding now.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Select a Part or Model in Studio, answer "what is this object?", fill a form —
it becomes a gatherable node, a mob or a quest giver. Closes the gap between
authoring a def and setting up a world object, which until now meant knowing to
tag a part and hand-typing PascalCase attributes in the property panel.
Engine — components can declare an attribute SCHEMA:
- src/components/Schema.luau (new): AttributeSpec/Display/ComponentSchema types,
normalize/defaults/get/list, and the schemas for Gatherable, Mob, QuestGiver.
Dependency-free ON PURPOSE: the plugin requires it live at edit time, and the
component modules themselves can't be required there (Harvesting asserts
IsServer; Remotes creates instances in ReplicatedStorage).
- Components.define now accepts EITHER the legacy `attr = default` map or a
schema array, normalizing both to one ordered spec list; bind() reads the
derived default map, so binding is byte-identical. Legacy maps are sorted, as
`pairs` order is arbitrary and would make a UI jitter. New getSchema/
listSchemas. The three shipped components pull name/tag/display/attributes
from the schema; their onSetup bodies are untouched (defaults verified
identical, all 23 attributes).
Plugin — the Build page:
- Field.luau (new): coerce/format/equalsDefault, lifted from ConfigAdmin (which
now delegates), shared by every schema-driven editor.
- FieldRow.luau (new): the shared [○/●] label … control + help row, including a
⌄ picker that cycles authored ids for fields declaring `ref`.
- BuildAdmin.luau (new): live schema read with three distinct empty states,
selection/eligibility/identify, deltas-only attribute writes, applyType
(tag + clear any other component) and clear.
- BuildAdminUi.luau (new): chooser cards, grouped form, multi-select apply,
stale-bind-marker warning, SelectionChanged-driven refresh.
- init.server.luau: record()-wrapped buildActions + the page.
Docs: docs/admin-plugin.md Build section + a 60-second walkthrough,
docs/extending.md schema guide, a CONTRIBUTING rule that new creator components
declare one, CHANGELOG.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Promote CHANGELOG Unreleased → 0.9.0 (player trading #15, the player interact
window, and the bow rate-limit security fix). Bump wally.toml +
SurvivorCore.VERSION to 0.9.0.
Collateral: player-trading demo video as a 7th site video tile and a Demo line
in docs/trading.md + docs/interact.md; a full-width "Player trading" feature
card on the landing page; trading.md + interact.md added to the README doc
index; version surfaces bumped across site, README and getting-started.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The bow release handler enforced no cooldown — the only client-driven action
in the engine without one (melee, harvesting and item use all rate-limit). Each
release also costs up to MaxRange/StepSize server raycasts to simulate the arc,
so the gate now runs BEFORE the arrow is spent and before the simulation.
- Combat.Bow.Cooldown (0.35s) added to CombatConfig + the EngineConfig schema,
so it's tunable no-code in SurvivorCore Studio.
- onBowRelease honours def.weaponCooldown first, falling back to Bow.Cooldown.
weaponCooldown was previously read only by the melee path, even though the
authoring form offers it for every weapon — a bow cooldown was silently
ignored. Its plugin label is now "Cooldown (s)" noting it covers both.
- A release with no matching draw is rejected (a real client fires BowDraw on
press, BowRelease on release).
- BowDraw validates the sender is alive and holding a bow; it previously
accepted anything from anyone.
- Aim points are checked for finiteness: a non-finite Vector3 defeats magnitude
comparisons and would reach the raycast after the arrow was already spent.
- lastShot is cleared in PlayerRemoving alongside lastSwing/drawStart.
Affects v0.8.0 and earlier.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Two UX bugs found while recording:
1. The trade window relied on the SEPARATE inventory menu for staging, and
clicking the menu's backdrop closed it with no obvious way to reopen —
leaving the trade unusable. The window now lists your carried stacks
INSIDE it (read from the replicated inventory attributes): click a row to
offer one, "All" for the whole stack. Dragging from the inventory grid
still works when that menu happens to be open. Removed the auto-open of
the inventory panel that created the trap.
2. The window couldn't be moved. Its header is now a drag handle (mouse +
touch), so it can be pulled out of the way.
Also: the in-window backpack live-refreshes on inventory attribute changes
(coalesced per frame) so a mid-trade pickup can't leave it stale. Panel grown
to 420x476 for the added section.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Replaces the buggy per-character Trade ProximityPrompt — which rendered over
your OWN head (no per-viewer exclusion) — with a TCE-ported interact window.
Walk up to another player → an "[E] Interact" badge floats over THEIR head →
press E / tap → a window shows their name + survival stats and an action list.
Targeting is a client-side nearest-OTHER-player scan (self skipped in the loop,
with hysteresis to stop flicker), so the affordance can never point at you —
the reported bug is fixed by construction.
Extensible: SurvivorCore.Interact.addAction{ id, label, order?, enabled?,
onActivate } — Trade is registered as the first built-in action and just fires
the existing (server-validated) TradeRequest remote, so the invite/Accept flow
is unchanged. Cursor is freed while the window is open; the window auto-closes
on walk-away / target-leaves / death / trade-start.
- src/client/PlayerInteract.luau (new): scan + billboard + window + action registry
- src/systems/Trade.luau: delete the per-character prompt block (keep Died abort)
- src/init.luau: boot PlayerInteract, expose SurvivorCore.Interact
- src/shared/UiConfig.luau: UI.Keybinds.Interact = "E"
- docs/interact.md (new), docs/trading.md, CHANGELOG (Unreleased)
Ported from The Counter Earth's PlayerInspectService/InspectController.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A new server-authoritative, dupe-proof trade system. Walk up to another player,
trigger the "Trade" prompt; they Accept/Decline; both stage loose backpack
stacks (drag from the inventory grid, with −/+ qty steppers) and must Confirm
before anything moves.
Anti-dupe by construction: staging is by-reference (items never leave the owner
until commit), and the commit is one synchronous, no-yield critical section —
re-validate holds → pre-flight both receivers have room (new Inventory.canAccept)
→ remove both → grant with addUpTo → refund any residue. Item count is conserved
on every branch (verified: 200k-iteration conservation + fit-oracle fuzz).
Auto-cancels on death / leave / out-of-range (MaxDistance) / request timeout; a
staging change resets both confirms. New Trade server system + TradeUi client
window, the "Trading" Config section (tunable in SurvivorCore Studio), hooks
trade:started / trade:completed, and a trades_total progression counter. v1 is
backpack stacks only (worn gear reserved behind AllowEquippedItems).
- src/systems/Trade.luau, src/client/TradeUi.luau, src/shared/TradingConfig.luau (new)
- src/systems/Inventory.luau: exported canAccept (weight+slot fit oracle)
- src/shared/EngineConfig.luau: Trading section; src/init.luau boot wiring
- docs/trading.md, README, CHANGELOG (Unreleased), Hooks catalogue, extending.md
- demo/server/TradeTestStation.server.luau: /tradetest 2-player conservation harness
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Promote CHANGELOG Unreleased → 0.8.0 (SurvivorCore Studio, Engine Config #21,
content overrides #40). Bump wally.toml + SurvivorCore.VERSION to 0.8.0.
Collateral: admin-panel demo video tile on the landing site + docs/admin-plugin
Demos line; refresh the admin feature card + value-prop to name SurvivorCore
Studio / Engine Config / content overrides; bump version surfaces across
site, README and getting-started.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Engine: quest overrides with objective*/reward* fields on nested code quests
now WARN at boot (they merge nothing — QuestData prefers nested tables);
EngineConfig + ConfigAdmin reject non-finite numbers (inf/nan).
Plugin: Config group panels auto-size (fixed-height math clipped the last row
of big groups — Theme group lost its Bold font row); Stats panels get the gap
math right; the Engine Config explainer page now REBUILDS the window when the
engine appears (the old hint was impossible — pages were assembled once at
plugin load); create() refuses ids that already have an override (mirror
guard); failed Create/Override reasons render under the create row; rejected
config edits report in the footer; explicit navigation cancels a pending
debounced search jump; the mount-time page restore no longer clobbers the
saved last-page setting during an engine-less session; undo/redo refresh
skips while typing in one of the plugin's own text boxes; search results past
the 50-cap no longer render empty category headers.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Dying again mid corpse-run drops a second bag (old + new coexist in the world,
each on its own 5-minute timer) and re-points the owner's beacon at the new
one. Previously the OLDER bag's later despawn/looting fired the unscoped
beacon-clear and wiped the beam pointing at the newer bag. LootBags now tracks
each owner's latest bag and only its destruction clears the beacon.
docs/loot-bags.md: documented the multi-bag + beacon-follows-newest behavior.
Live-verified: two coexisting bags, beacon on the newest; looting the OLD bag
left the beacon untouched; looting the NEW bag cleared it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Root cause: with StreamingEnabled (the new-place default), respawning away
from the death spot let Roblox evict the bag from the owner's client — the
bag looked deleted, and the local Destroying event fired, permanently killing
the beacon (server bag was fine all along).
- The bag is now a Model set PersistentPerPlayer for its owner
(AddPersistentPlayer) — it never streams out of the owner's view.
- The beacon is position-driven plain data: no Instance in the remote, so no
replication race (the 0.5s delay hack is gone) and no streaming fragility.
- The beam clears on an explicit server nil-fire when the bag is truly
emptied/expired (plus a lifetime fallback), not on replica Destroying.
Live-verified (fresh bytecode confirmed via bag ClassName): beacon appears
instantly, survives respawn, bag stays visible to the owner, loot restores
everything, beam clears on empty.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Beacon: LootBagDropped fired the same frame the bag was created, so the
Instance reference arrived as nil on the client (not yet replicated) and the
owner beacon silently never appeared. The fire is now delayed 0.5s.
- Dead looting: collect() never verified the collector was alive, so a corpse
lying next to its own bag could scoop everything back before respawning.
The server now rejects dead collectors (isAlive gate, Harvesting pattern).
Live verification note: the running Studio session executed stale bytecode
(old collect granted loot to a dead player even though the new source was
synced) — verified source-in-place; behavior verification needs a Studio
restart, which CI/release artifacts are unaffected by.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Samuel Lison