FAQ

What game formats are supported?

HTML5 ZIP packages with an index.html at the root. Maximum upload size is 500 MB. The zip can contain any assets (JS, CSS, images, audio) and sub-folders — only the root index.html is required.

How long does game review take?

2–5 business days. You'll receive an email when your game is approved or rejected. Rejections include written feedback so you know exactly what to fix before resubmitting.

Can I update a published game?

Yes. Upload a new version zip in the developer portal under My Games. The update goes through review again before going live. Your existing xAPI credentials remain active during the review period.

Are free games allowed?

Yes. Set the price to $0. Free games are still reviewed before publishing to ensure quality for schools.

What subjects and age ranges are supported?

Any subject and any age range from 3–18. You specify subjects and age range when uploading. These are used by schools to filter the marketplace.

What revenue share do developers get?

Developers receive 70% of every sale. edu.games retains 30% to cover platform costs, payment processing, hosting, and support. Payouts are made monthly via bank transfer.

In what currency are games priced?

Prices are set in Australian dollars (AUD). Schools are charged in AUD; their bank or card provider handles any currency conversion.

What payment methods do schools use?

Schools pay by card or purchase order. edu.games handles all invoicing and payment collection — you never deal with billing directly.

Do I need to implement xAPI?

No. xAPI is optional. Standard HTML5 games are fully supported. xAPI enables richer progress tracking for teachers — they can see individual scores, time spent, and completion rates per student.

What happens when a game is approved?

xAPI credentials (key and secret) are automatically generated for your game. Find them under Plugins & SDKs in the developer portal. These credentials authenticate your game with the LRS.

What xAPI version is supported?

xAPI 1.0.3. The LRS is fully spec-compliant for all core endpoints: statements, state, agents, activities, and about.

Can I use the same credentials for multiple games?

No. Each approved game gets its own unique key and secret. This allows per-game reporting and lets you revoke credentials for one game without affecting others.

How are learners identified in xAPI statements?

You choose. The most common approach is email (mbox). For privacy-conscious deployments, use the account form with an opaque user ID — no email is sent to the LRS. Both forms are fully supported.

Is there a rate limit on the LRS?

There is no hard rate limit for normal game traffic. If you're doing bulk data migration or load testing, contact us at developers@edu.games so we can accommodate your usage.

Can I query statements for all my games at once?

Each set of credentials only has access to statements submitted using those credentials. To aggregate data across multiple games you'll need to query each credential set separately.

Are xAPI statements permanent?

Yes. xAPI statements are immutable by spec — once stored they cannot be edited or deleted. State documents and profile documents are mutable and can be overwritten or deleted.

Can my game run in an iframe on a school's VLE?

Yes. The LRS uses CORS with Access-Control-Allow-Origin: * so xAPI calls work from any origin, including games embedded in Moodle, Canvas, Google Classroom, or any iframe host.

Does the LRS support SCORM?

No. The edu.games LRS speaks xAPI (1.0.3) only. SCORM is not supported. If you have a SCORM game, convert it to HTML5 + xAPI or contact us for options.

Can I test xAPI without submitting a game for review?

During development, use the /xapi/about endpoint to verify your credentials are correct. Once your game is approved, credentials are active and you can submit test statements from any environment.