Skip to main content

Course Policies

Please read these policies carefully. Unless an assessment explicitly states otherwise, the policies on this page apply throughout the course.

At a Glance

PolicyRule
AttendanceClasses are conducted in person. Some assessed activities require compulsory attendance.
Late submissionsNo late submissions. A submission after the deadline receives zero credit, unless an approved contingency applies.
Technical problemsTechnical difficulties close to the deadline are generally not grounds for an extension. Submit early and verify your submission.
Midterm Part A absenceA make-up may be arranged with valid supporting documentation and timely notification.
Midterm Part BGenerally no make-up. Exceptional circumstances are handled case by case.
Academic honestyYour submitted work must comply with SUTD academic-integrity requirements.
AI toolsAllowed for learning and development unless explicitly prohibited, but you remain responsible for everything you submit.
Quizzes / examinationsNo AI, external assistance, or communication unless explicitly permitted.
Course questionsUse Ed Discussion for questions that may benefit the class.
AnnouncementsOfficial course announcements are made through eDimension.

Attendance

Lessons are conducted in person and recordings are generally not provided.

You are expected to attend classes, particularly sessions containing:

  • quizzes
  • lab presentations
  • project checkoffs
  • examinations
  • guest or industry sessions marked as compulsory
  • the final project presentation
Compulsory Assessments

If an assessment requires your physical presence, absence without an approved LOA or other accepted contingency may result in forfeiting that assessment component.

For example, attendance at the final Game Project presentation is compulsory. A student who is absent without an approved LOA will not be allowed to present their portion of the project.

Submission Deadlines

Assessment deadlines are strict.

Late submissions for the following will receive zero credit unless an approved contingency applies:

  • Lab submissions
  • Individual Homework
  • Game Project submissions
  • Midterm Examination Part B
  • other assessments with a stated submission deadline
No Late Submissions

A submission received after the stated deadline is considered late.

Late submission = 0 marks.

Please do not plan to submit at the last minute.

The previous course policy likewise applied zero credit to late Lab, Project, Homework and Midterm Game Jam submissions.

Technical Problems

You are responsible for ensuring that your submission is complete and accessible before the deadline.

Examples of issues that normally do not justify a late submission include:

  • slow uploads
  • incorrect files
  • corrupted ZIP files
  • inaccessible repository permissions
  • build/export taking longer than expected
  • Git or GitHub problems immediately before the deadline
  • uploading to the wrong submission entry
  • discovering at the deadline that your executable does not run

For assessments involving an executable build, test the exact package you intend to submit.

tip

Submit early enough that you have time to download or reopen your own submission and verify it.

Medical Certificates and Exceptional Circumstances

If illness or another exceptional circumstance prevents you from completing an assessment, contact the instructor as early as possible and provide the appropriate supporting documentation.

Extensions or make-up arrangements are not automatic.

Midterm Examination

Part A (Theory)

If you are unable to attend Part A (Theory) because of a documented medical or other approved circumstance:

  1. Notify the instructor at least one hour before the examination begins, whenever reasonably possible.
  2. Submit the required supporting documentation.
  3. Do not access the examination materials.
  4. If approved, one make-up examination will be arranged.
danger

If a make-up examination is arranged and you fail to attend it without another approved contingency, you will receive zero marks for Part A.

Access records and attendance records may be used to determine whether examination materials were accessed before a make-up request. The previous policy similarly required advance notification and prohibited accessing the original examination before receiving a make-up.

Part B (Game Jam)

Because Part B is a take-home Game Jam conducted over an extended period, there is generally no make-up assessment.

Exceptional circumstances will be considered case by case.

Contact the instructor as soon as possible if a serious circumstance affects a substantial portion of the assessment period.

Academic Integrity

SUTD's academic-integrity requirements apply to all work in this course.

You must not:

  • submit another person's work as your own
  • copy work from current or previous students
  • share answers during an individual assessment
  • communicate with others during a closed-book quiz or examination
  • obtain or distribute unauthorised assessment materials
  • misrepresent another person's contribution as your own
  • fabricate project, testing, or peer-review evidence

For group assessments, work produced legitimately by members of your group is considered group work.

For individual assessments, the submitted work must represent your own individual work, subject to whatever resources the assessment explicitly permits.

Sources that you quote, paraphrase, adapt, or substantially build upon should be appropriately acknowledged where relevant.

The course has historically required external sources and reused code or writing to be explicitly referenced.

Examinations and Quizzes

Unless explicitly stated otherwise, examinations and quizzes must be completed individually without communication or external assistance.

Use of Generative AI

Generative AI tools may be used in this course as development and learning tools, unless a particular assessment explicitly prohibits them.

Examples include ChatGPT, Claude, Gemini, GitHub Copilot and other code or content generation tools.

Where AI is Generally Allowed

Unless stated otherwise in the assessment instructions, you may use AI to assist with:

  • understanding Unity or C# concepts
  • debugging and testing
  • brainstorming
  • explaining unfamiliar APIs
  • generating small code examples
  • refactoring
  • exploring alternative implementations
  • reviewing your own code
  • generating placeholder content during prototyping

However, you remain fully responsible for the resulting work.

You should be able to:

  • explain the code you submit
  • explain your design decisions
  • modify or debug your implementation
  • identify limitations or errors in AI-generated material
  • justify why the implementation is appropriate for your game
You Own What You Submit

"I used AI to generate it" is not an acceptable explanation for code or design decisions you cannot understand.

If you submit it, you are expected to understand it and answer any questions about your code/work promptly.

Where AI is Not Allowed

AI tools are not permitted during:

  • Midterm Part A (theory)
  • any other assessment explicitly marked as No AI

For the Midterm Game Jam or other individual assessments, follow the instructions released with that assessment. Those instructions take precedence over the general policy on this page.

AI Does Not Replace Attribution

AI assistance does not remove your responsibility to acknowledge external material.

If you directly incorporate substantial third-party code, assets, text, tutorials, libraries, or other resources, cite or acknowledge them where appropriate.

Collaboration

Different assessments permit different levels of collaboration.

AssessmentCollaboration
Game ProjectGroup work
Lab SubmissionIndividual or pair work
Individual HomeworkIndividual
Lab PresentationGroup
**Midterm Part A (Theory) **Individual
**Midterm Part B (Game Jam) **Individual

Always follow the instructions for the specific assessment if they impose additional restrictions.

Group Work

For group assessments, dividing responsibilities among members is expected.

However:

  • all members remain responsible for coordinating the project
  • assigned responsibilities should be documented
  • changes to responsibilities should be agreed upon by the team
  • repository history and the GDD may be used as evidence of contributions

The Game Project uses a separate peer-review multiplier to account for individual contribution.

See the Game Project page for details.

Communication

Ed Discussion

Use Ed Discussion for course-related questions whenever the answer could be useful to other students.

This is particularly encouraged for:

  • Unity problems
  • bugs
  • clarification of lab instructions
  • assessment clarification
  • technical problems that others may also encounter

The anonymous posting option may be used where available.

This also helps instructors avoid answering the same question privately many times. The previous course setup used Ed Discussion specifically so solutions to common problems could benefit the rest of the cohort.

Questions During Assessments

If an assessment requires questions to be asked through a public course channel, do not privately contact individual instructors or TAs for assessment clarification.

This ensures that all students receive the same information.

This is particularly important during the Midterm Game Jam, where questions should be visible to everyone.

eDimension

eDimension is the official channel for course announcements and assessment submissions.

You are responsible for checking:

  • announcements
  • assessment releases
  • deadlines
  • submission links
  • changes to course arrangements

Enable eDimension email or notification settings so that you receive course announcements promptly.

Asking for Help

You are encouraged to ask for help when you are stuck.

For technical or course-content questions, prefer:

  1. Ed Discussion, especially for questions likely to affect multiple students
  2. Class or lab sessions
  3. Scheduled project consultations
  4. Direct contact with the instructors for matters that genuinely need to remain private

Examples of matters that should be discussed privately include:

  • medical circumstances
  • LOA
  • personal circumstances affecting assessment
  • disputes within a project team
  • peer-review concerns
  • academic-integrity matters

Project consultations are available during the designated project weeks and may also be arranged when necessary.

Policy Precedence

note

If the instructions for a specific assessment conflict with a general rule on this page, the assessment-specific instructions take precedence.

Official SUTD policies and approved academic or administrative arrangements take precedence over course-level policies.