What to do, what to hand in, and how to keep the work useful.
Create an account and choose Educational Agent Design or SPARC Intro Scene. The first group explores both collaborative and competitive NPCs. The second redesigns the opening game experience using Unity (recommended) or three.js.
Your instructor can move you between groups. You do not need a Microsoft or GitHub login to use this portal.
Open My assignments. You will see tasks for your group and tasks assigned directly to you. Read the purpose, required deliverables, and review criteria before starting.
The kickoff is this week’s starting point. A deadline is shown only when your instructor sets one, using America/New_York time. Your first task does not assume a finished, production-ready system.
Explain the learner, the learning goal, the interaction, and how you will know it helps. Clearly label hypotheses, unfinished parts, and open questions. Distinguish confirmed SPARC background from proposed story additions.
For team work, list your teammates and each person’s contribution. Each student submits a document or link under their own account so individual work can be reviewed.
Submit from the assignment page with documents, GitHub links, or a playable demo/walkthrough. Attach a summary and contribution note. New submissions create new versions rather than overwriting the old ones.
Check My submissions for feedback. “Needs revision” includes the instructor’s next-step notes; “Accepted” means that version has been accepted.
Upload PDF, DOCX, PPTX, MD, TXT, PNG, JPG, or WebP. Each submission supports up to five files: 20 MB per file and 40 MB combined, with a 250 MB document allowance per student.
Put code in GitHub. Keep large Unity project folders, builds, and videos on a repository or shared drive and submit an HTTPS link. A private repository needs to be shared with the instructor on GitHub separately.
Upload buttons do not publish your documents. Downloads require a signed-in account with permission. File types are checked, but files are not antivirus-scanned; only open documents you trust.
A player winning a challenge, moving faster, or spending more time in a scene is not automatically evidence that they learned. Define what understanding looks like, then design a small check for it.
Use reliable sources for factual explanations, flag uncertainty, and keep educational NPCs away from personal medical advice. Do not collect classmates’ health information or identifiable research data in this portal.
A smaller, testable idea beats
a bigger, unexplained one.
Classmates: signed-in students can see student names, usernames, and group membership. Email addresses, submitted documents, repository links in submissions, feedback, and individual assignments are not shared with classmates.
Instructor: the instructor can see all accounts, email addresses, assignments, submission versions, and feedback; manage group membership; pause accounts; and reset student passwords. The instructor cannot read the original password from its stored hash.
Public visitors: can read the project descriptions, getting-started guide, kickoff summaries, and announcements deliberately addressed to “Everyone.” They cannot browse student rosters or submissions.
Retention: previous versions are retained so the instructor can follow progress. Contact your instructor for removal or correction of account data or coursework. The portal has no automatic retention/deletion policy and does not send email notifications.
Access: registration is open until the instructor pauses it. An email is used as an account/contact field, not as verified university enrollment. Use a unique password of at least ten characters; the instructor account can change its password in Account.