Tool
What the LMS actually sees.
Course and tracking data sit side by side. The course runs in the frame; everything it reports — initialise, set, commit, terminate — lands in the panel next to it, in the order it happens. Refresh the page and the attempt resumes, the way an LMS restores cmi.suspend_data.
A real Storyline 360 export, published for SCORM 1.2 — the same package you would hand to an LMS. Every call it makes is listed on the right.
What the LMS sees
- api
- SCORM 1.2
- session
- not started
- status
- —
- score
- —
- location
- —
- session_time
- —
- suspend_data
- 0 chars
API calls
- Nothing yet — start the course on the left.
Runtime
A small LMS written in TypeScript: the eight API functions, the data model, read-only rules and error codes for both SCORM 1.2 and 2004.
Discovery
The package walks up the window chain looking for API_1484_11, then API — the same routine Storyline and Rise ship inside every export.
Why it exists
Most portfolios claim SCORM knowledge. This page demonstrates it, and doubles as a debugger when a package misbehaves in a client's LMS.
Next: The Screening will be published here as a real Storyline export, so you can play the module and watch its measurement layer report at the same time.