Premium Only Content
 
			Stay Down Dev Log - Part 4 - MAJOR REFACTORING, Game States!
In this HEFTY video, I refactor pretty much all the code I've written so far to take on a more modular approach to organizing the project. I truly keep everything out of the global scope except for one global object. In addition, I implement some game states to manage the pause and run states of Stay Down. This is boring stuff, and there's a lot of brow furrowing, but it had to be done.
What you'll learn in this video:
- Patience (if you watch to the end).
- Game States / State Machine. Games have different states and this video shows one way of managing that.
- A way to organize and structure your application in a very modular way, allowing for private and public members in each module.
- How not to make a successful Rumble video. NO EDITS, BABY!!!
Visit my website: https://pothonprogramming.github.io
- 	
				 57:29 57:29Poth On Programming4 years agoStay Down Dev Log - Part 3 - Fixed Time Step Game Loop, Pausing!7
- 	
				 34:03 34:03Poth On Programming4 years agoStay Down Dev Log - Part 7 - PLATFORM COLLISION!!!26
- 	
				 42:04 42:04Poth On Programming4 years agoStay Down Dev Log - Part 12 - GRAPHICS!26
- 	
				 41:04 41:04Poth On Programming4 years agoStay Down Dev Log - Part 6 - Jump On Platforms!!!7
- 	
				 28:16 28:16Poth On Programming4 years agoStay Down Dev Log - Part 13 - SPIKES!!!10
- 	
				 17:39 17:39Poth On Programming4 years agoStay Down Dev Log - Part 9 - Destructuring Objects21
- 	
				 42:27 42:27Poth On Programming4 years agoStay Down Dev Log - Part 8 - COLLECT ITEMS3
- 	
				 10:58 10:58Poth On Programming4 years agoStay Down Dev Log - Part 5 - Improved Keyboard Controls20
- 	
				 56:52 56:52Poth On Programming4 years agoStay Down Dev Log - Part 14 - Background Graphics!20
- 	
				 35:57 35:57Poth On Programming4 years agoStay Down Dev Log - Part 16 - Improving The Framework40