A game in which players can fight using the environment based on the elements.
8INF955 - Video games conception and development (UQAC - University of Québec at Chicoutimi)
Gabriel Rassoul - Belkacem Lahouel - Benoît Kessabian - Donatien Rabiller
We mainly use those technologies.
ProjectSettings : Project's settings
Assets : Project's assests
Assets/Materials : Project's materials
Assets/Meshes : Project's meshes
Assets/Prefabs : Project's prefabs
Assets/Scenes : Project's scenes
Assets/Scripts : Project's scripts
Assets/Shaders : Project's shaders
Assets/Standard Assets : Unity's standard assets
Assets/Textures : Project's textures
Assets/Meshes/Grass : Grass's mesh
Assets/Meshes/Projectile : Projectile's mesh
Assets/Meshes/Projectile/Earth : Projectile's mesh for the earth element
Assets/Textures/RockProj_1 : Rocks' textures
Assets/Textures/Smoke : Smoke's texture
You may add an alias for this repository's address: git remote add [alias_name] [repository_address]
Please configure git (at least!) such as described here:
cd ~
vim .gitconfig // or any other text editor
[color]
diff = auto
status = auto
branch = auto
[user]
name = [name]
email = [email]
[alias]
ci = commit
co = checkout
st = status
br = branch
add-commit = !git add && git commit
add-ci = !git add && git commit
[credential]
helper = cache --timeout==3600
A .gitignore file has been added, please use it as intended.
Read this: http://stackoverflow.com/questions/18225126/how-to-use-git-for-unity-source-control
Finally, please use those commit rules, as much as possible, even though this is really annoying:
(1) Language: english
(2) Title: summary of big modifications
(3) Skip a line
(4) Detail of small modifications afterwards.
Please commit one big modification at a time, as much as possible.
(1) Fetch (git pull) from the Github repository.
We use this model: http://nvie.com/posts/a-successful-git-branching-model/
(1) Do not push in master for no good reason.
(2) Work on the current feature you work on, on you own branch.
(3) Only push source code in Github (no binaries, as much as possible!).
(4) Document your methods if needed.
(5) Good code do not need much documentation.