hikari bb60ae3390 fix: auto-quest continues after quest failure (#92) ...

## Summary

Fixes #87. When a quest failed, the tick loop detected the failure and turned auto-quest off so the "player could reassess". This meant every quest failure required the player to manually re-enable the toggle.

## Root Cause

The tick applies quest failure by resetting the quest to `status: "available"` with `lastFailedAt` set. Auto-quest picks up `available` quests automatically — so turning off auto-quest on failure was entirely unnecessary, it just broke the loop.

## Fix

Remove the auto-quest-off-on-failure block entirely. The quest returns to `available` immediately after failure, so auto-quest naturally retries on the next tick. Players can still disable it manually if they want to stop.

✨ This PR was created with help from Hikari~ 🌸

Reviewed-on: #92
Co-authored-by: Hikari <hikari@nhcarrigan.com>
Co-committed-by: Hikari <hikari@nhcarrigan.com>

2026-03-20 09:35:55 -07:00

..

src

fix: auto-quest continues after quest failure (#92)

2026-03-20 09:35:55 -07:00

test

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

eslint.config.js

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

index.html

feat: error handling, logging, analytics, OG tags, and sticky sidebar (#44)

2026-03-09 19:54:42 -07:00

package.json

release: v0.2.0

2026-03-19 21:24:55 -07:00

tsconfig.json

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

vite.config.ts

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00

vitest.config.ts

feat: initial prototype — core game systems (#30)

2026-03-08 15:53:39 -07:00