Home

General knowledge

Prior to diving in, consider checking out one of Unity's tutorials.

---

Notable Pages

Scriptable Object Event System

Enemy Hook and Stats System

---

Script Documentation

General Scripts

• Object Pooler
• Poolable Object
• Projectile
• Spawn Point
• Trigger

Generic Character Scripts

• Character Health
• Character Health UI
• Character Level
• Character Loot

Enemy Scripts

• Enemy Attack Melee
• Enemy Attack Ranged
• Enemy Experience
• Enemy Hook
• Enemy Movement
• Enemy Scale By Level
• Enemy Stats System
• Enemy Targeting

Player Scripts

• Player Hook
• Player Inventory
• Player Movement Controller
• Player Level
• Player Scale By Level
• Player Stats System
• Player Hook

UI Scripts

• UI Inventory Slot
• UI Inventory Panel
• UI Upgrade Slot
• UI Upgrade Panel

---

Singular Responsibility!

Most beginners make the mistake of shoving too much functionality into an individual script. While you could technically get your game working with a few giant scripts, continuing to develop and extend that code requires an impressive mental fortitude and perseverance. If your script handles 15 different things about a player, when you need to change 1 of them you have to worry about all of them! This is where most beginners find themselves starting a new game development project every other day as they can't possibly keep up with the complexity.

You can avoid code monoliths by coding with SOLID design principles in mind. Specifically in this case, the single responsibility principle. Every script should only be responsible for one functionality. It is at your discretion as to what degree "singular responsibility" means since technically you could have a script "responsible for the player" that does 100 different things. However, you could also technically break a script down into parts that are too small to reasonably manage as well. This is something that is learned over time, so don't sweat it. Try your best and learn from past frustrations and others.