How to Program in Unity: Hierarchical State Machine Refactor [Built-In Character Controller #5]
ฝัง
- เผยแพร่เมื่อ 13 มิ.ย. 2024
- Learn how to program a Hierarchical State Machine in Unity with this new video break down and tutorial!
Want to learn how to program state machines in Unity? This video will help get you there! Today we'll go over important concepts of the State Pattern and refactor our overly-complex code into a clean hierarchical state machine! With a detailed code walkthrough and guided explanation for every step along the way.
ACCESS PROJECT FILES & SUPPORT THE CHANNEL:
💛 / iheartgamedev
iHeartGameDev Merch:
💛 www.iheartgamedev.com
WANT MORE?
Check out previous videos in this growing series of tutorials:
✅ • Character Controllers
✦ Like the vid? Please consider Subscribing!
bit.ly/2YdIb6j
✦ Missed out on the last episode?
• How to Move Characters...
SOCIAL:
✦ Discord
/ discord
✦ Twitter
/ iheartgamedev
LINKS FROM THE VIDEO:
🤖 Download Jammo for YOUR game:
assetstore.unity.com/packages...
⭐ And Check Out @Mix and Jam !
/ mixandjam
GEAR:
Lumix G7 Camera: amzn.to/3Kks1gZ
Epomaker GK68 Keyboard: amzn.to/3Ke87EB
Samson C01U Pro Mic: amzn.to/33kDdtG
LG 27" Monitor: amzn.to/3qAHFwS
Lepow 15.6" Portable Monitor: amzn.to/3287OtL
Logitech G604 Mouse: amzn.to/3A6jNV4
Audio-Technica ATH-M50X Headphones: amzn.to/3tBaeMT
X-Pen Artist 15.6 Pro Drawing Tablet: amzn.to/3FE5HLI
Apple 15in MacBook Pro Laptop: amzn.to/3AbKdFc
►TIMESTAMPS:
Intro: 0:00
Current Project Recap: 0:38
C# Naming Conventions: 2:10
Whats Wrong?: 4:24
State Machines Concepts PT 1: 5:10
Hierarchical State Machine Benefits: 5:55
State Machine Concepts PT 2: 6:30
State Machine Implementation: 7:54
Setting up Context: 8:58
Setting up Abstract State: 10:55
Concrete State Override Setup: 12:05
State Factory: 12:35
Switching States: 14:34
Concrete States Access Context & Factory: 15:48
Getters And Setters: 17:00
Moving Handle Jump Logic: 19:55
Updating Current State: 20:45
Splitting Handle Gravity Logic: 21:25
Require New Jump Press: 23:08
Hierarchical State Machine: 24:08
Updating Sub States: 27:45
Switching States Correctly: 28:33
Did You Notice?: 29:39
Final Result: 30:06
I did the Unity Junior Programmer course, I'm at the last small game for my portfolio. Saw this pop up and thought oh let me check this out. Now I feel like a Freshman Programmer V_V.
I get the point of doing this though, it's similar to what I do with having parent and children for my enemies in the game: I have the parent that contains the code everything uses and the children that do things specific to that object.
But HSM is a new frontier and your use of getters and setters is... prolific, I'm happy I already knew about them or my head might have exploded. Definitely need to re-watch this or actually go back to the first in this series.
I am shocked you aren't at 100k subs yet. The YT algorithm gods haven't descended on this channel yet I guess.
Thank you for such a kind comment! I am always happy to share what I learn and try my best to convey it in a hopefully understandable manner. I wouldn't understate how far you've probably come since the start of your game dev journey though! You have probably grown so much since you first started with Unity, and will continue to grow as long as you try 🙌 Keep going! Keep learning! And looking forward to seeing what you release in the future!
@@iHeartGameDev Thank you! Really, Thank you!
How was that course? I'm a software developer professionally so I already know how to code, but thought that might be a good place to start with Unity.
@@MrFishstickGamer For rogue upstarts like myself it helps create a portfolio to refer back to. You get very small but complete projects that represent a fundamental element of design.
For me it became a bit too much when they introduced GitHub resources. It's kind of like when you get home and your body decides at the door that you need to pee so you are in a rush: I enjoyed getting each project done but then practice of working Github after gave me enough distress to want to take a break.
If I could start all over I would say starting with Unity Junior Programmer course is best then moving on to YT videos like iHeartGameDev who has a similar but more complex projects.
The most important thing though is time and practice.
This guy is becoming the new Brackeys.
Man. This was hard, but I'm glad you're tackling complex issues like this, I feel like most other youtube tutorial channels are afraid to make videos on topics like this. Also your presentation was top notch. Thanks for taking the time to make this video.
Glad you got through it! Thanks for watching! 😊👍
Don’t worry, watch the video multiple times until it clicks.
I still can't believe the amount of effort you put in on these videos. Cant wait!!
Thank you for the kindness 🙏
Hey all! I'm so excited to share this new tutorial where we go over a player-based hierarchical state machine. Most of the state machine tutorials that I've found have covered AI and have just been single state, so hopefully you find this helpful when making more complex character controllers.
The next video lined up is the first Cinemachine tutorial voted for by the Patrons!
As always, thank you so much for watching and I hope this helps you on your game dev journeys!
Cheers! 🍻
-Nicky
I've recently started making something using Hierarchical State Machines and seems to be working fine but quite excited to see how you'll be handling it to see if what I'm doing can somehow be improved.
Thank you for the tutorial!
For cinemachine, I'd really appreciate it if you covered how to make custom cinemachine modules. When I tried to integrate pausable dialog using cinemachine, it was quite a pain to get it working amre there really weren't any resources about it. And then there was the problem making it reset properly after playmode which I had to give up on.
Yes! Every state machine tutorial is AI and never character controller! It’s very frustrating so thank you for making this.
By video Quality and explanation this channel has great potential grow exponential. Make sure to be consistent other only luck can help with algorithms.
Thanks very much! The growth is pretty consistent so far. I only wish I could increase the frequency of my video output without sacrificing quality.
This is a damn fine tutorial. More people should know about your channel. You're like an advanced Brackey's spiritual successor.
Hey! Thank you so much for the kind words and comparison!
Facts dude facts
This video is certainly a step up in difficulty from the last ones. Feels like it went from algebra straight to rocket science in terms of complexity. Gonna be rewatching this one quite a few times. Thanks for taking the time to make these videos.
Expertly visualized. Expertly explained. To the point, concise & articulate. You value - - our time. Thank you. Subscribed!
Thank you for such a kind comment, Papo!
I am trying to make my first game and I wanted to learn about this state machine topic. The first time that I watched this video I took notes and didn't try coding anything. Going through the video I found things that I didn't quite understand at first but I just continued to try and understand as much as possible. After watching the video I tried coding a state machine for an object that I want in my game and I had the lightbulb moment several times! Everything is starting to make much more sense now that I pushed myself to figure out something that I didn't quite understand yet. Thank you for this video!
Heck ya! Welcome to game dev!!
I thought of and implemented a small refactor that should provide a nice performance boost to the code. When you use the StateFactory, you're creating a new instance of each state to be applied. It clearly works great, but discarding those classes after you don't need them anymore causes some work for Garbage Collection, which can cause issues down the road. So I went back and in the constructor of the factory I create an instance of each state and store them in a dictionary. Then instead of returning a new state, I just fetch the same state from the dictionary. If you do that, and move the initialize substate method to the Enter functions of the states, then everything works the same. You could even go a step further and have the switch state method take in a state enum instead of having different methods for each state.
I'm pretty sure this disqualifies the factory as a factory, but I'm not experienced enough to know the actual name. I should also mention that this ONLY works because the states work entirely off of the data provided by the context. if the states themselves held some sort of data, this would require some extra logic to maintain.
Love these videos, btw! I look forward to the next one!
Wonderful job! I also considered storing those instances! But I wasn’t sure how much garbage making new instances would cause.
That being said, it’s awesome to me that you took the time to refactor the code! Thank you for watching and sharing your own implementation!
Thanks for mentioning this. I'm building a mobile game and I need to keep an eye on garbage collection.
@@anaezesomto8330 A simple or basic example could be if the character can swim, shoot gun, fly etc. then the base states would be onground, swim, shooting, flying and jumping. like left mouse button will fire bullets in shooting state but can dive lower in water while swimming, etc. and you won't have to add bool/flag checks for left mouse button pressed cause the states will handle that. AND MOST IMPORTANT -> ONLY ONE BASE STATE IS ACTIVE IN THIS CASE. you can have multiple active states with some more complex/dimensional state machines. Hope this helps!
I have a few recommendations
1. Make the states inherit from Scriptable objects. This way you can add different configurations for a specific state. If you game have some "buff" system you can have the states take their stats (like movement speed etc) from the scriptable object, and then you can switch the current state in run time to buffed version and vice versa. You don't need the state factory, all the states are pre-configured.
2. create a "unique name" for each state (states that differ in configurations will have the same name you will see later why) and make a dictionary that holds a name and the scriptable object in context. The player will try to switch states using the name of the new state only, and the level above in the hierarchy will hold the dictionary. This is good because you can have more states, like dodging, climbing ladder, dash, fly, swim ... each of those "know" when they need to be active, when they need to be shut, each can hold its own configurations and functions (in the scriptable object)
3. Add events - (mostly applied to shooters) if you want an action (like shooting) to depend on state, make an event to be fired off the base FSM component (the outmost one that is always in the scene) that when a state changes it fires "OnStateChange()" with information of the new state, make the weapon subscribe to it. and then if the weapon can only shoot on certain states you can use
if(state is StateThatEnablesShooting)
canShoot=true
...
4. Separate the input system from the context.
Create a class of InputHandler that will take in the inputs and process them, this way you can put constrains on the input itself before it reaches the controller. Why do you need it?
let's say you want to enter a driving state and you don't want to "hard steer" left and right. You want to simulate a wheel turning and slerp between (0,1) to (0,-1) and you want to reuse the movement (that takes direction from the data) you will need to apply another layer of processing. Another thing is that you might want to change sprint to toggle - first click would enter the state, second exit, you would probably want to pre-process the data outside of the classes (if we are following SOLID we don't want the class to also manage the input types).
Overall very very powerful design. It takes a lot of work to get it to work at first, but the amount of work on expanding that is next to nothing. When comparing it to celeste's controller I wanna see the brave guy that will try to implement some new functionality in there.
Great suggestions ! If you can provide an concrete example with source code, it’ll be very help full.
@@de-souzapatrice1859
Imagine the following architecture for a weapon system.
Each state will inherit from scriptable object. The states will be the following (can be expanded)
Reload, PrimaryFire, SecondaryFire, Scope etc...
PrimaryFire and SecondaryFire will inherit from FireState which will inherit from BaseWeaponState
And then each fire state will run their shooting logic in OnEnterFire, They will exit the fire after the cooldown of the fire rate is over (which can be set up through the inspector) back to an idle state or reload.
The weapon class (which will hold the state machine) will hold the bullet count and anything related to ammunition and will communicate with the base player's inventory.
Then if you want to upgrade the weapon for let's say shoot laser in which u spawn a trigger collider that will inflict damage over time, you can create a new PrimaryFire state, implement its own logic, and put it in the primary fire slot of the StateMachine.
This system allows for upgrades, as you can alter the values of the scriptable objects to create many variants of the weapons offline, and at runtime to swap (for example, for upgrading a weapon that fires projectile to a weapon that shoot hitscan to a weapon that shoot laser beams all you have to do is make different variants of FireState)
it's just an example, I hope it's clear
@@Doronoss Thanks for explanation. Indeed, it a great way to achieve it. I’ll try and may be send you a link for code review. I’ve sent you a connexion request on linkedin.
Dude, you are just amazing...your videos are even better and explain more than Unity's official tutorials...Keep up the good work sir...please dont leave youtube ever...
Thank you so much for the kindness! I don't plan on leaving any time soon!
This video made me sub to your Patreon.
I'm from Brazil so Patreon is kinda expensive to back on, but the effort and quality on this video is incredible, one of the best tutorials on TH-cam.
I love how you're not shy of explaining more complex topics, most Unity tutorials don't really dive into programming, but this tutorial is incredible not only for Unity but for programming overall.
Thank you for this!
Excellent tutorial! Just for the record, you explain genuinely well, with ease, precision and conciseness. Keep up the great work, you'll see your community growing fast for sure!
I needed to see this. Recently wrote a monster state machine like you referenced in the beginning. Now I'm refactoring it and it feels great. You're very good at breaking down each step so I've learnt some basic principles & habits aswell. I can't thank you enough, keep it up. Liked and subed.
I just used this in my game. Amazing stuff, thank you so much! :)
Although, I did add a little to it that I recommend others do, also. For example, this code as it is doesn't run the EnterState or ExitState on the SubState when changing state to another Root State. For example, when going to the Jump State it will call the function from EnterState to Initialize a substate, but that substate's Enter function is never called. EnterState is only ever called on the Sub States when calling SwitchState, like going from the Walk state to the Run state for example.
To implement this just do these basic things.
In the PlayerBaseState script, just add this line of code to the SetSubState function "_currentSubState.EnterState();". This will cause the Enter state to be called. Although you'll get the EnterState being called twice when calling SwitchState from Idle to Walk etc. So to fix this just move the line "newState.EnterState();" to inside the if(_isRootState) conditional.
Full code is such...
protected void SwitchState(PlayerBaseState newState){
// Current State exits
ExitState();
if(_isRootState)
{
// Call exit on substate as we move to new root state
if(_currentSubState != null) _currentSubState.ExitState();
// Call new States enter state
newState.EnterState();
// Switch current state of context
_ctx.CurrentState = newState;
} else if(_currentSuperState != null)
{
// set new substate
_currentSuperState.SetSubState(newState);
}
}
protected void SetSuperState(PlayerBaseState newSuperState){
_currentSuperState = newSuperState;
}
protected void SetSubState(PlayerBaseState newSubState){
_currentSubState = newSubState;
newSubState.SetSuperState(this);
// Call enter state for substate when entering it
_currentSubState.EnterState();
}
Why do we need the extra calls?
Great video, I have had so much trouble with HSM since the beginning of my time in Unity. Your tutorials make a complex topic very digestible. Thanks so much for your time!
This is exactly what i needed, i have been doing C# for years and had a hard time with figuring out how to structure a project so it stayed clean the further i got in, i had this idea in my head that statemachines was the answer but i was unsure of how to implement it in unity, thank you for a very nice in depth tutorial :)
Thank you saved me a lot of time trying to browse videos for an actual working one
I love how this channel videos are very aligned with the games I like to make. Great job, Nicky!
Thanks so much Alex! I hope this helped you out at least a little bit!
Hey man, I just wanted to say a huge thank you for posting this video! After sitting in front of my computer many days and rewatching this video like a bunch of times, I finally was able to implement the hierarchical state I needed thanks to you. Thank you, thank you, thank you! :)
Amazing! All of these design patterns are tough concepts to wrap our heads around so great job pushing through!!
Overall great video.
thumbnail,
Communication,
Diagrams,
Audio Cues,
Flow.
Keep it up man, you'll be the next Brackey's in no time!
The quality on these videos is exceptional. Awesome video thanks a bunch.
Thanks so much Alex!
You are amazing, I just switch to soft softs and I am loving everytNice tutorialng about it. It much easier then my last program.
This is what I've been looking for, thanks. Keep up with the amazing series!
Thank you so much! Happy to hear!
Thanks Nicky! Helped me so much this series.
This is awesome! Definitely refactoring my player and monster controllers now and will mention this video in my next one :)
I can't believe literally no one is talking about how satisfying Nice tutorials voice softs.
Wow, just wow! One of the best Unity tutorial i have ever seen
this channel is just magic, very nice content dude. Really looking forward to all the new content coming
Thank you for the kindness Oscar!
This is one od the best and most usefull tutorials ever Made!
How did it take me so long to find this video?!?! I've been wracking my brain for about 2 months trying to "modularize" my fps controller. Everything I've tried has failed miserably. I'm yet to try this, but 10min into the video I suddenly feel like I might still have a chance
Also, I fkn love Nicky. I've seen a few of your videos before, so much more pleasant to watch than 99% of other game dev/programming tutorials
Thanks so much for the kindness!! Made my night!
Really cool! 🙂
Your channel definitely needs more views!
Thanks so much Alan! Big fan of your work!
I didn't even thought about implementing StateMachine for player character controller. Thanks for video!
This is the best free software Ive seen. Respect.
Thank you! So glad I found this video. My player code just got 10x cleaner
I've written several FSM/HSM implementations, but thought I'd give this architecture a try because it's far less complicated than those I've written. Made a few changes, but the primary is that my OnExit method is an IEnumerator and when switching states, I yield until it's exited. The makes it easier to do things like waiting for an animation to finish before exiting. I also am using ScriptableObjects to configure each state. For example, if you have multiple playable characters, each state can utilize properties of the current character scriptable object.
Coroutines generate garbage each frame, try events/delegates.
Do tell how you get the remaining time for the animation clip from animator/ or what is you implementation for yield WaitUntil? I hope u don't use hard coded values??
@@safwatahmad7672 so the coroutine is only used in the OnExit in order to block a transition until things have completed, and so they're called only once per state transition. As for the animation remaining time, I've tried a number of approaches, but wound up just using animator events on another animation component that proxies via standard C# event actions.
Edit: There are a number of solutions, but I went with one that works well for me. I also cache yielders when possible to reduce garbage.
There are so many comments already so not sure if it's was already mention; But the HandleGravity method should also be included on the groundstate (where it checks if the player is onground or not, like falling off from a stair or so). Thanks for all your vids, it's one of the best explained tutorials I've ever seen. While I'm already an advance programmer, it always nice to learn some different ways on how things could be implemented.
by any ans, but I can make what I envision, and that's the greatest gift to . You are, without a doubt, an expert teacher. You may
This is the exact thing I was looking for!!! Thanks!!!
Ayyyy Thanks for helping get to know the Software! I just downloaded it in hopes of making resetupes and originals. Props to you for
Subscribed. I needed this. Thank you
I will be rewatching this video for months, thanks nick
Thank you for watching! I hope it helps!
Oh my god! Finally I could understand State Machine. Thank you so much, I am very happy with the code refactoring. I came from JAVA world and I made a mess up with my code. Really appreciated
You are most welcome! I’m happy to hear it helped
it worked! thank you so much!!
Oh my gosh. You are amazing. Now I can say that I'm a game developer. Thanks to you.
Thank you man for sharing this stuff
I have watched this video 2 times. The first time i was confused. And this time, i am proud that i can understand this.
This may not look like much, but, i am glad that my 6 month of learning does not waste any of my time.
Great work 👏👏👏
So informative, thanks a lot!
You will definitely become the top 1 who makes cracks
Huge THANKS for this video!!!
This is AWESOME!!! 👍
You're the man mate! Thank you so much.
Respect to your good work, thanks a lot
thanks, it actually let me through so i could download it.
you are the best teacher, bro
As always, awesome job bro! 🤜🤛
Thank you Mark!
I still havent watched the complete video, And I have already liked it
Great job buddy, keep it up!
Great video, thanks I really enjoyed it
Thank you for sharing this tutorial
Incredible video. I always had issues when we have "conditional states" that can be used any time, like Die State, we can die while walking, while jumping, while idle etc. Well, one condition wont hurt. But having greater than one causes issues. I thought i was on Complete FSM level, but seeing Hierarchical made me think why i didnt know this before.
i didnt expect it to work wow thank you so much bro
Always the good content great work
Great tutorial! Thank you :)
You are great bro!
Thank you it works with me
now i am in a good mood
Thank you so much for this!
Can't wait for the next episode
thank you so much. tNice tutorials helped a lot
Great video! Thanks!
the moment we all have been waiting for
THANK YOU SO MUCH FOR THIS VIDEO
You’re welcome :)
This helped a lot thank you
you are welcome!
you are the best dude
ITS REALLY WORKED LOL THANK YOU DUDE
Worked, thx
thanks so much man
First of all, thank you for these wonderful tutorials on the new Input System. I love how much detail you put into each one of your videos.
While completing this portion of the series, I ran in to a similar issue as others mentioned below. Sometimes it feels like isGrounded isn't working and others it seems like the animations just aren't playing. After several placements of Debug.Log, I was able to determine that the "EnterState()" method of each substate was never being called. My solution to this was to add "newSubState.EnterState();" on the PlayerBaseState.cs class in the protected SetSubState() method, after newSubState.SetSuperState(this); so, the SetSubState method looks like this:
protected void SetSubState(PlayerBaseState newSubState)
{
_currentSubState = newSubState;
newSubState.SetSuperState(this);
newSubState.EnterState();
}
Hope someone finds this useful.
I had a similar problem, but when I tried to add "EnterState" to the "SetSubState" Method the state was called twice. So when I would be grounded it would call Idle two times instead of one.
To change it I added :
protected void SwitchState(PlayerState newState)
{
...
if (isRootState)
{
// Switch root state
context.CurrentState = newState;
// This //
if (currentSubState != null)
currentSubState.EnterState();
}
....
}
to the SwitchState Method, this just Enters the subState of the current root-State.
@@akatizu I don't know why, but even with your code, my Enterstate of my substate is still called twice ... :( It's so weird that @iHeartGameDev didn't show us why substates can't use EnterState...
you are amazing dude! thanks so much
finally found thanks to the author
Very helpful..thanks a lot.
drums softing good start learning how to make your own lodies. Good luck bro!
I think using static actions and early exits in update loop for player controller to be a better implementation than state machines especially if you have combat that relies on animation events for animation completion checks, vfx etc. It also structure the code in component pattern rather than state patter. This allows you to enable and disable parts of the character controller on run time without breaking anything or any errors. Basically I was able to make a similar controller but with 0 dependencies so far. I imagine the only dependency in this implementation would be a scriptable object that contains player stats such as run speed, jump height etc.
Very interesting! I will need to look into this type of implementation! Thank you for sharing 🙏
Wow, that sounds interesting. Can you share refs or better some material to read about?
That would be very appreciated!
@@sahsaaryutin Its actually my own custom implementation and ive improved on it since. I'll describe it for you. basically my game has systems like parkour, combat with anim cancle, anim lock etc. I also have casting system where player can cast spells whenever. These advanced mechanics require monobehaviour since you need to access things like anim events, colliders rigidbodies etc. What i did here was make a static class for inputs. it reads inputs and broadcasts them in the form on static actions (look up unity actions). This way my individual compoents like movement , jump, ledge grab etc can subscribe to these actions. since these actions are static you do not need references. now for my player controller intercomunications i use inheritance. basically every script of my controller is derived from base class. and base class contain static protected variables that need to be shared. example, lets say player is not grounded. the base class has a static bool variable isGrounded. this variable is accessable for all chile classes. so in update() of my movement script the first thing is do is if(!isgrounded) return; This way I have 0 references between my controller components . with this implementation say i want to disable jump then iu can just say jump.is active = false and nothing breaks. now lets say enemy needs to know if player is blocking. you can create a new scriptable object that basically holds player status . it contains a bunch of bools like isJumping, isMoving etc and just have one of the controller scripts fill this data out at runtime. This way anything that requires player status (enemies, UI, etc) then get it from this scriptable object and dont need a player references. This also alows you to use multi scene workflow
@@pewpew518 very interesting, and now i have ideas how to improve architecture, thank you! ☺
I am sure that Unity technology will use your videos in Unity Learn one day or they will put them in their TH-cam channel. Explanation is clear and well illustrated. Thank you very much. Please, don't forget Ledge grabbing in your coming videos. Thanks!
Thanks so much Patrice!
Really, really great video. I've used state machines a lot but I needed a little bit of extra knowledge and this was perfect, not only did you have beginner friendly information, for those who don't know state machines you also had information for more intermediate programmers such as myself.
Your videos are to the point but theyre explained well without over flowing people with useless information.
I really appreciate this video and I'm about to go and watch your other videos. Thank you.
Heck yeah! Thanks John! Love hearing that
Best tutorial on state machines, would u mind doing a tutorial on climbing/parkour?
thanks very much :)
it very well! Good Job!
Thanks so much
Casi 4 días con esta clase. Valió cada momento.
Awesome. Happy to hear it helped!
At 13:20, you can add the readonly modifier to _context field. This way _context can only be assigned on the class constructor (or on its declaration).
Awesome! Didn’t know that. Thank you!
This was a great video
Im glad you have the luxury of optimizing with State Machines, I'm having trouble getting the animation to kick in at all. I got run to animate thanks to Jason Weinman's Navmesh animator in the Player object hierarchy. Thanks for your jump script, it helped me crack jumping better than Brackeys' outdated tutorials. Subscribed. You rock dude!! Thanks! Im pretty sure what I did wrong was not implicitly adding a animator component in the Inspector. Clearly My animator is attached to the player, it should be somewhere in the inspector. The problem is since I started not using the animator in an inspector from the beginning, adding it after the fact does not rectify the problem. Its similar to when you make mistakes assigning scripts to the player object instead of the game model. Those errors in organizing are hard to correct, and it is quicker to start over from scratch or at a much earlier build. Gotta love it!!
what a beast XD ty man
Man this video is pure gold for me!! I have made a platformer character controller and was in the process of refactoring it. I was in a dilemma if i want to eventually put all of the controller code in one script, which i know is bad practise but a lot of things depend on each other so it seems a functional way to do that. I have never used a State Machine before but i kinda thought to go that way cause things started to get messy and if i did i needed an option for sub states as the player actions are kinda complicated in that one. I think this might actually work cause in the end you store all the data in one script here. I think this will improve the controller by much and is probably the missing key i needed to complete it and use it in my portfolio.
Awesome to hear that it was helpful 😊 best of luck on your game!
@@iHeartGameDev That was hard to understand i won't lie lol! I managed to transfer my controller to the new system only implementing the movement and jumping mechanics yet. I still need to do Dash, WallSlide/WallJump and i think i am also going to need a Fall state. Since my controller used Rigidbodies, i think i should also make the equivalent of UpdateStates for the FixedUpdate method. It was satisfying to go through this process and actually make em work as intended, but i ll definitely need to watch this a couple more times to make sure i understand everything perfectly. This was invaluable for me thnx a lot for doing these kind of more advanced videos!
Edit: I just saw you have another video implementing the Fall state. The fact that we continuously create new instances of the states was also bugging me and i see you have addressed this too in that video. I was walking my dog this afternoon and i was thinking why dont we use a dictionary to store those states and just get them from there? I now see my thinking was correct as this is how eventually did it. I am also trying to find a proper way to tackle script execution order. I found something on Google that might help. I ll try that too and see how this goes and i ll post it if it works fine.
thanks helpful vid
Needed this ❤️❤️👍
I hope it helps!
Good tutorial!
I love your channel bro! You are a concise teacher. Can you do a tutorial on instantiating a different prefab every time the health meter decreases/ increases every 25%? Can you also do one on playing a different animation each time the health meter decreases/increases every 25% as well?
Thank you in advance
Thank you Brackeys successor