Samples¶
Import from Package Manager → RevLearning → Samples → RevLearning Samples. They are not compiled into your project by default — the Samples~ folder has a tilde, so Unity does not import it until you ask.
| File | What it shows |
|---|---|
QuickstartExample | Initialize, report status and score, commit |
QuickstartResumeExample | The same, plus suspend and resume through a bookmark |
XApiQuickstartExample | Configure an endpoint and send statements |
Scenes/SCORMValidationScene | A panel for exercising a real LMS by hand |
Scenes/XApiValidationRunner | The same for an LRS |
The quickstarts¶
Read QuickstartExample first. It is deliberately the shortest thing that works end to end, and it shows the two places courses go wrong: checking the result of the commit rather than LastError alone, and handling a null Cmi instead of assuming a connection.
QuickstartResumeExample is the one to copy if your course is longer than one sitting. Resume is the feature most likely to be discovered broken by a learner rather than by you, because it only fails on the second visit.
The validation scenes¶
These are not demos. They are the harness for working through Tests~/CONFORMANCE.md against a live platform: build to WebGL, package, upload, launch, and press the buttons in order while watching what the LMS records.
They earn their place because no automated test can replace them. The two most serious defects fixed before this release — a proxy that swallowed every LMS error, and a refused correct_responses re-write — were both invisible to a fully green suite and both found here, on SCORM Cloud.
Which is also why the panel is worth extending carefully. It shipped for a while able to record only a correct answer, which made incorrect-answer vocabulary impossible to confirm by any live run. A validator that cannot produce the failure case cannot validate the failure case.