How bloodorca/hollow works
Hollow is a browser-based Hollow Knight save editor. Users select or drag in a PC save, or choose Nintendo Switch mode for plain-text saves; the app loads JSON into an editor, lets users modify or reset it, and downloads an encrypted PC save or plain Switch save. Recent edits are kept in browser storage and can be reopened. The main control flow is visible in src/index.js; codec internals and history persistence are also sampled. Other UI and persistence details are represented only where documented or directly evidenced.
Main entry points: index.js App controller · functions.js Save codec · history.js History manager · windowDrag.js Drag handler
Components 10
Editing workflow
- App controller
src/index.js - Drag handler
src/windowDrag.js - JSON editor
src/index.js
Save conversion
- Save codec
src/functions.js - Base64 codec
src/base64.js
Recent history
- History manager
src/history.js - Browser storage
Other components
- User
- Save file
- Downloaded save
Connections 14
- User → App controller: selects save
README.md - User → Drag handler: drops save
README.md - Drag handler → App controller: dispatches drop
src/index.js - App controller → Save file: reads file
src/index.js - App controller → Save codec: decodes PC save
src/index.js - Save codec → Base64 codec: decodes bytes
src/functions.js - App controller → JSON editor: renders JSON
src/index.js - JSON editor → App controller: edits JSON
src/index.js - App controller → History manager: updates history
src/index.js - History manager → Browser storage: reads and writes
src/history.js - App controller → History manager: reopens entry
src/index.js - App controller → Save codec: encodes PC save
src/index.js - Save codec → Base64 codec: encodes bytes
src/functions.js - App controller → Downloaded save: downloads save
src/index.js