Collaborative Unity Project for HEV subject : A Classroom Endeavor!

View releases . Report Bug . Request Feature

BRANCH MAIN

BRANCH DEV

Table Of Contents

• About the Project
• Contributors roles
• Built With
• Getting Started
• Roadmap
• Contributing

About The Project

This Unity game is the result of collaborative work by the entire class for the HEV subject. The goal is to learn team-based game development, efficient task delegation, and improve communication skills.

Contributors roles

Rozdělení týmu

NÁZEV TÝMU	LTD	ČLENOVÉ
MANAGEMENT	ADAM DOLEŽAL	VLADIMIR VORŠILKA
3D MODELING	HONZA ADAM	JŮZL, PROCHÁZKA
2D GRAPHIC UI	MICHAL BÍLEK	ALEŠ MRÁZEK
PRG1	PETR POLÁK	BUROCK, FLORIÁN, KŘÍSTEK, BONDAR
PRG2	MARTIN JEŘÁBEK	VOSTROVSKÝ, PROCHÁZKA, SVĚTELSKÝ, MÁKA, POŠVIC
MERGE MASTER	MARTIN REICHELT	JEN MARCYN
AUDIO	VANĚČEK	TOMÁŠ KRÁL
GAME/WORLD/LEVEL DESIGN	MICHAL NOVÁK	PAVEL ŠOTOLA

Built With

Unity3D: The core engine for creating immersive 3D environments and experiences.
Blender: Used for 3D modeling, animation, and rendering.
[Other frameworks, plugins, and addons that will be used]

Getting Started

To get started read our guide: Guide

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

We encourage all contributors to follow our guidelines to ensure a smooth and efficient development process. Below you will find specific guides for Team Leaders (TLDs) and team members:

• Team Leader Guide
• Team Member Guide

---

Remember to use camelCase

---

Merge Request

• New feature (ID FROM ISSUES!)

  • Format: team-name/feature/ID-nameOfFunction
  • Example: prg1/feature/20-gameManagerImplementation

• Bug fix (ID FROM ISSUES!)

  • Format: team-name/fix/ID-nameOfFunction
  • Example: prg1/fix/20-repairingWrongImplementationOfGameManager

---

Only for management

• Update (branch rebase, MR, doc edit, typo fix, etc.)
  • Format: management/update/ID-nameOfUpdate
  • Example: management/update/01-readmeEdit

---

Commit (USE EVERYWHERE ISSUE ID!)

It is important to properly describe what you did in the commit!

Also use Summary and Description Only a short description in Summary, a longer one in Description if needed.

• New feature

  • Format: feat: ID/description
  • Example: feat: 03/binding for keyboard

• Bug fix

  • Format: fix: ID/description
  • Example: fix: 14/forward move binding

• Code refactoring

  • Format: refactor: ID/description
  • Example: refactor: 15/new binding method

• Performance optimization

  • Format: perf: ID/description
  • Example: perf: 38/debug and change perfomance of method