Скачать или смотреть Tomb Raider 2016 Basic Code Structure Unity Project

Generally, I enjoy developing appealing mechanics. However, this time I wanted to create a project that contains bad mechanics and visuals but nice and clean code.

You can think of the project as the basic code structure of TombRaider 2016. I started developing it inspired by that game.

I have always been curious and envious of the title of "principal architect" because I struggle to write maintainable code and manage complex behaviors, as well as present new features gradually to the player. I often got stuck somewhere later in the project.

What makes this project different from other projects, videos, articles, tutorials etc., is the focus on understanding software engineering concepts such as MVC architecture, SOLID principles, DI etc. with real and complex scenarios. Because well understaning of many concepts in software requires large project. And I can prove that project itself tells us what these concepts even though we do not know them.

My main purpose is not dive deeply these concepst with acadamic language. I just want to explain them in simple language with a large, meaningful project

In order to keep this post simple, you can find a lot of additional information on github and in the video.

I also touched on some points where I violated MVC or had bad code implementation in youtube video. The video is 1 hour and 15 minutes long and consists of the following parts; Intruduction, Area, Campsite, Weapon, Enemy, Player, Save System, Input, MVC, Violating MVC, SOLID, DI, Power of UniRx, Working with Non-Monobehaviour classes, ...Ability(Testability, Maintainability...) and Final Thoughts.

Github link: https://github.com/bunszr/Tomb-Raider...
LinkedIn link:   / bunyaminsezer98  

00:00 Intruduction
00:55 Areas
09:46 Campsite
20:16 Weapon
29:57 Enemy
35:36 Player
38:24 Save System
40:38 Input
41:36 MVC
45:24 Violating MVC
48:45 SOLID - SRP
50:09 SOLID - OCP
53:36 SOLID - DIP
57:38 SOLID - LSP
59:44 SOLID - ISP
01:03:13 DI
01:07:23 Power of UniRx
01:09:00 Working with Non-Monobehaviour classes
01:10:26 ...Ability (Testability, Maintainability...)
01:14:14 Final Thoughts