PkgFoundry
Catalog npm
PACKAGE EXPLORERView in registry

@0xhoneyjar/quests-engine

npm

Headless quest engine — substrate-step dispatch bridging (gateway → construct → resolution) + future quest publish/query/complete/claim flows. Framework-agnostic. The construct is OPENED via Effect Requirements; consumers plug in their own grader.

effectenginefreesidequestsstate-machine
Versions collected3
Direct dependencies6From release 0.1.2
Last observed21 Oct, 08:56 UTC

README

Current package documentation

packages/engine — headless quest logic

The core quest engine library. Stateful where needed; framework-agnostic. What cubquests-dashboard/actions/* becomes when the operator-dashboard chrome is stripped from the engine logic.

Status: scaffolded; content extraction pending

Source: world-sprawl/cubquests-dashboard/actions/ + world-sprawl/cubquests/apps/frontend/lib/. Per ../../docs/EXTRACTION-MAP.md.

Planned contents (post-extraction)

filepurpose
publish.tsQuest publishing flow (validate, persist via injected port, emit completion event). Logic only; DB binding is swappable.
queries.tsCached quest queries; cache layer parameterized.
loader.tsQuest discovery + filtering logic.
generators.tsQuest authoring helpers (generate-input + generate-json + diff utilities).
diff.tsQuest-version diff utility (find-json-differences).
claim/Consumer-side claim flow (validate completion, mint badge, emit event). Currently inline in cubquests' apps/frontend/lib/.
index.tsPublic exports

Why "headless"

The engine has logic that operates on schemas + ports. It does NOT:

  • Render UI (that's packages/ui/)
  • Talk directly to a specific DB (that's adapter-injected)
  • Know about Next.js / SvelteKit / framework specifics
  • Own the partner integrations (those stay in CubQuests)

This makes the engine reusable: any app (Purupuru, Honey Port, Mibera, future) can install + wire up the engine to its own UI + DB + chain integrations.

Composition

  • Imports types + schemas from ../protocol/
  • Implements ports declared in ../ports/
  • Doesn't import ../ui/ (rendering is downstream)
  • Doesn't import ../adapters/ (adapters compose with the engine; engine doesn't depend on transport)

Consumers

  • world-sprawl/cubquests-dashboard/ — post-extraction, dashboard wires its actions to call engine functions instead of inline logic
  • world-sprawl/cubquests/apps/frontend/ — claim flows wire to engine/claim/
  • Future world apps (Purupuru Year 2, Honey Port) — install + wire up the engine
  • Server-rendered surfaces that want quest data without a roundtrip

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Versions 3

Collected releases
VersionPublishedDirect dependenciesOpen version
0.1.2Registry latest4 May 20266
0.1.14 May 20266
0.1.04 May 20266
Sorted by available source dates · UTC

Package advisories

0
No matching advisories collected

This describes our collected data; it is not a security assessment.

Repository

PENDING
0xhoneyjar/freeside-quests

Shared repository data · GitHub

License detected in repository
Not collected

Metadata history

Meaningful changes
Current collected state Current

Observed since 21 Oct, 08:56 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package:4cbc83a5753860379bfd206b7dbee890055195aa57ff669c5dfb6f3cfb776192