(difficulty: easy, requires teacher access to a course) Using the attached package add the attached SCORM2004 zip file (SCORM2004-sample) as a SCORM package to your site. Enter the SCORM package as a student Ensure that the package loads the first screen and a JavaScript pop-up does not appear. (see screenshot for JavaScript error that occurs prior to this patch) You do not need to "test" the SCORM package further - SCORM 2004 is not fully supported and other issues may occur. (Alternative instructions, NOT required) Using the Prodding SCO Download the Prodding SCO , precisely the SCORM 2004 package : Extract the archive and change the imsmanifest.xml file to read: ... <item identifier="DB4B88FC-DD3A-11DA-9B41-B622A1EF5492" identifierref="EA10429C-DD3A-11DA-9B41-B622A1EF5492"> <title>SCORM Diagnostic SCO</title> <adlcp:dataFromLMS>Some SCO Information</adlcp:dataFromLMS> </item> ... Select all the extracted files, including the XML file just changed, and create a new SCORM archive representing our customized package Add a new SCORM activity using the customized package above Enable SCORM API debugging , including debugging at DEVELOPER level. Be sure to allow browser popups before starting the next step Attend to it as a student using FF cleaning its cache first - Note: CR has sometime issues with giving the right room to visualize the SCO in the Moodle player - , the prodding SCO will appear Click on the API Prodder tab and issue a sequence of: Initialize GetValue , using cmi.launch_data as data element . You should get the value set in the manifest file i.e. Some SCO Information Terminate Ensure that everything is fine e.g. no debugging messages on the API logging windows