Skip to content

Where It Installs

RevLearning arrives as a .unitypackage and lands in Assets/RevLearning, rather than installing as a package under Packages/.

That is partly the Asset Store's delivery path and partly a choice. The reason is narrower than the one RevFramework gives for the same decision, and it is worth stating precisely rather than borrowing an argument that does not apply.

The reason: the samples are the evidence

Under Packages/, a package does not appear in the Project window at all. Its samples sit behind an Import button in Package Manager, and documentation inside it lives in a folder Unity never displays.

For most libraries that is fine. For this one it is the wrong trade, because the sample scenes are not a tutorial — they are the proof.

Samples/Scenes/SCORMValidationScene and XApiValidationRunner are the panels the published conformance run was driven through, on a real LMS, reading the actual LMSSetValue traffic out of a registration debug log. Every one of the nineteen checklist steps maps to a control in them. The claim this package makes about conformance is only worth anything if you can go and re-run it yourself.

A buyer who has to know that Package Manager has a Samples tab, and press a button there, before they can find any of that, is a buyer who mostly will not. In Assets/RevLearning/Samples/ the scenes are in the Project window, where somebody opens them on the way to something else — which is most of how anyone learns what a library actually does.

The reason that does not apply

RevFramework's install page gives two arguments, and only the second is true here.

Its first is that you are meant to remove parts of it — delete a system you do not use and the rest still compiles, which is the normal way to use it, so the delivery mechanism has to be one where removing things is expected.

RevLearning is not like that. It is a bridge with a frozen public API, and there is no half of SCORM to delete. You depend on it the way you depend on a library. On that axis a package under Packages/ would be the textbook answer, and it loses to the sample-visibility argument above rather than beating it.

Said plainly because an argument that sounds good and is not true about the product is worse than no argument.

What you can remove

Two folders, and the runtime does not care:

  • Samples/ — the quickstarts and the validation scenes. Delete it once you have what you need from it and nothing else changes. The samples assembly is autoReferenced: false, so nothing in your project references it unless you made it; an unreferenced assembly is stripped from a player build, and the scenes are not in your Build Settings unless you put them there.
  • Documentation/ — the guides, the FAQ, the mental model, the data and privacy statement and the conformance record. Also online, so delete it freely: https://revandrab.github.io/RevLearning/

Keep Samples/ while you are standing up your first course. It is the quickest way to find out whether your LMS agrees with how you are reporting state, and finding that out after you have written a course is expensive.

What does not ship

The test suite. 336 EditMode tests run in CI on every push, and they are not in the package. Under Assets/ they would compile into your project and appear in your Test Runner beside your own tests, which is noise you did not ask for. The counts and what each suite covers are in Documentation/CONFORMANCE.md.

The trade, stated plainly

A new version is re-imported over your copy.

Keep your own work outside Assets/RevLearning. Your scripts, prefabs and scenes belong elsewhere in the project. Do that and an update is uneventful. Put them inside the product folder and an update becomes a merge.

This is the cost of installing into Assets/, and it is the one thing worth setting up correctly on day one.