❤️ Support content like this: www.patreon.com/infalliblecode 00:00 Introduction 02:02 Why do beginners use design patterns? 03:41 How were design patterns meant to be used? 04:33 Should you use design patterns in game development? 06:15 How do you write code without using design patterns? 07:27 Join our community of game developers

I remember a thing you said about design patterns in one of your videos, it went something like this: "Design patterns are like solutions to a problem, it's better to have encountered the problem first than going for the solutions before hand", that stuck with me.

@InfallibleCode

3 жыл бұрын

This is spot on! I cover this exact idea in the video 💯

@RonnieBanerjee007

3 жыл бұрын

@@InfallibleCode ay ay sir, almost there.

Did anybody else expected a response like "FUCK YOU I'M USING MVC TO MAKE THE NEXT HIT!"?

@Xershade

2 жыл бұрын

I mean many games use it, just usually they don't build MVC on EC or EC on MVC to do it. Unity already answers the question MVC answers, which is why you usually don't want to touch MVC in unity unless its for a completely separate thing that doesn't build on the EC system the game objects use.

So... this is a tutorial on how to thoughtfully reply to a question on Discord 🤔

@InfallibleCode

3 жыл бұрын

Something like that

Don’t over-engineer for a problem that doesn’t exist. Make it work, then clean it up. Real example: I used a switch statement to decide which function to call on Start for spawning a gameObject. Each function spawned the same gameObject differently, giving it different settings. This worked, but I noticed all these different settings could be encapsulated into individual classes rather than one monolithic spawner class. Thus, I implemented the Strategy Pattern. The pattern itself rose naturally from the code. It was not something I preplanned.

@InfallibleCode

3 жыл бұрын

This is a great example! And I’m gonna have to quote you, couldn’t have said it better myself.

@nexxogen

2 жыл бұрын

The only problem is, the Strategy Pattern is a solution to a specific localized issue within your code. It only requires you to refactor a relatively small portion of your codebase in order to implement it. MVC on the other hand is a way to structure your entire codebase. So if you don't go down that road from the outset, there's no way you're going to be refactoring your entire project when after a few months you realize how "MVC would work great here". Certainly not without significant delays in development. TL;DR With MVC, you don't have the luxury to switch to it after you realize that it would work for your problem. You either start and stick with it, or you don't.

@Xershade

2 жыл бұрын

@@nexxogen The point is you honestly shouldn't need MVC in Unity, it comes with a solution to the question of why you need it already. Unity uses Entity Component which is just a different way to solve the problem you need MVC for. The main thing they're getting at is most devs jump into another system and go "Well I need this because Is use it in my other field." not realising that the problem they're trying to solve is already solved. Not saying you never use MVC in unity but the rare times I've had to it's because I'm dealing with something outside of the EC pattern entirely. What building MVC into unity is doing is basically the same thing as if someone came into ASP.NET or w/e web design language and started to build EC on the MVC based app. They're two solutions to the same problem.

@nexxogen

2 жыл бұрын

@@Xershade The way I see it, just because a specific solution comes with Unity, doesn't mean that you necessarily should use that solution. In my opinion, there's a lot of reasons not to go for a heavily component-based architecture. - You're clogging your scene with a bunch of manager game objects which aren't actual things in your scene, and should be regular C# classes instead. - Every MonoBehaviour brings a bit of extra overhead. The callback methods are invoked through reflection, which has a negative performance impact. - You heavily rely on dragging and dropping things in the inspector which is bug-prone. Renaming inspector variables is very awkward as it's very easy to lose all of your references. - Having a lot of objects in the scene which run the Update method can become a serious problem, so then you have to figure out more awkward solutions like having one Update per scene which then runs a list of all the other objects that need the Update method. - It is very hard to make your components fully autonomous and independent from other components, which is the very idea of EC. - Communicating between different objects is awkward too. You must use FindObjectOfType which is not very performant, or Singletons which are a horrible design pattern for this purpose or a lot of manual dragging and dropping which you will have to redo when you accidentally rename the exposed variables without adding [FormerlySerializedAs] or if you don't want that ugly thing polluting your code base. I'm pretty sure that Unity originally went for this solution because it's relatively simple to use and because a lot of new people can easily get into game development with it, and not because it's a great solution. To anyone more advanced it shows its ugly face quite clearly. I'm not even saying that MVC should be used. I would just want to hear a better reason than "Unity already has something different".

I have mix feelings about this video. I've been work in gaming industries for a while, in my current job we implement code starting with TDD. We make unit testings in a way that was completely decouple from unity behavior or hardcoded dependencies with unity. MVC worked like a charm this way cause we leave all unity logic or implementations on presenters or view (Monobehaviours) , and even worked on projects with MVVM approach (Using scriptable objects). My question is, if you have a project for a game and you know that you have to build the entire system to be flexible enough to scale properly and have a good set of tests, do I need to wait to encounter the problem to then select a design pattern? Isn't that approach stomping on the same rock over and over? And btw, for me it's extremely difficult now to start a project and not thinking in a design patters or the architecture of the game before hand. This is definitely a great topic to cover. Keep up the good work guys.

@Xershade

2 жыл бұрын

Here's a question, why do you need an architecture to handle data, logic, and display, like MVC when unity already has one setup for you. EC (Entity component, the thing Unity uses) is just a different answer to the same question you're trying to solve by using MVC. I would argue EC is just as flexible if not more so than MVC. Building MVC on top of EC is just adding more bloat. The components in EC as supposed to be pretty much self contained modules you add onto things, there are somethings you need sub-componets for, and hence why unity has requirement attributes, but here's the question, why do you need to split a player movement script into three different components for data, logic, and display. They way I tackle it in unity is basically this, what does the component do, if it does more than one thing like movement AND combat, then it needs to be broken up, not just broken up for the sake of breaking it up. Essentially you're stacking a SRP pattern on top of a SRP pattern, and all that does is make the code bloated and complicated. Maybe for larger things like combat there will be a top level component that fires stuff down to specific things like magic, ranged, melee, pets, summons, etc. but that's only so you don't have to debug a 100k line combat module every time you bork your game.

@TheTwyker

2 жыл бұрын

@@Xershade Because then all of your potentially simple components are MonoBehaviours, which adds a lotta bloat and overhead again, which the component might not even need in the first place.

@fifnmarlindemann8404

2 жыл бұрын

@@TheTwyker If the `MonoBehaviour` does not contain Update logic it takes fewer resources. I stumbled upon that point on "performance", too, but later I decided to use components for all until I found a performance issue. It is not until then will I replace components with scriptable objects or C# structs. Unity is a restricting framework, and trying to squeeze out the overhead is not so simple. To be realistic, I decide to go for an easy and fast way. I think we shall wait for DOTS to become mature if performance is really that important.

Welcome Back Charles and Barles. Glad to see yall in my notifications again with entertaining gamedev skits for 2021. It's always good to take breaks now n then to unwind which is understandable. Thanks to finding you guys,Cherno and few others all got me into learning gamedev past 3 years. Havent made anything yet since im apporaching things slowly but one day i'll get there.

Just when I really discovered the channel, you were gone. Great to see you back in action :D

I was starting to worry that 2020 got you too.

@InfallibleCode

3 жыл бұрын

Hah! Me too 😅

@Haapavuo

3 жыл бұрын

RIP 2020!

All these characters Charles plays makes me wonder - are we all just figments of his imagination, created solely for the purpose of demonstrating a concept in a KZread video?

@InfallibleCode

3 жыл бұрын

It's all a simulation. In 40 or 50 years I'll unplug and see if I got the high score 😝

There's always something to learn from your content, even if it's a familiar topic. Great to see you back ❤️

@InfallibleCode

3 жыл бұрын

Thanks for the kind words - It’s great to be back!

Thanks for putting the notification sound at the start of the video - had me searching around for where it came from on my laptop!

OMG this is happening! I almost quit Game Dev, but not anymore!! Welcome back!! ❤

@InfallibleCode

3 жыл бұрын

I’m glad you didn’t quit!

It looks that we started this year with the right foot. Nice video guys, there's always something to learn from you! :D

When the video started, I expected it to explain why you SHOULDN'T USE MVC in Unity, as "Barles" wrote "you really shouldn't, it's bad practice" in the Discord chat. But the video didn't argue for that at all. What it actually claimed was "you shouldn't start building your game by following any particular pattern (not just MVC) until the need for a pattern arises". This is not an argument against using MVC in Unity. This is an argument against blindly using patterns in general from the get go. Now because MVC is a way to structure code, I don't think it's really possible for you to just decide you're going to switch your entire project structure to MVC in the middle of development. You're either going to do it from the start (minus the rapid prototype phase, of course), or you aren't going to ever do it. So it seems that, when it comes to MVC, you simply don't have the option to implement it at a later development stage, certainly not without significant delays, just because after 3 months of development you realized how "this problem could be solved by using MVC". So the question still remains, why is MVC a bad pattern to use in Unity?

Working in a big game studio, we use MVC for UI features of the game (menus, widgets) but we just do Model / ViewController. Nice to see you back :) and good video.

Love the pet sneaking in on Charles' side of the video. :)

@InfallibleCode

3 жыл бұрын

Haha yup that’s Boots and he loves to have around while I’m filming 😸

That was the best discord server ad I've seen. This video literally got people to join your server lmao.

It's pigeon *hole or holed :) Great video! I'm currently experiencing the paralysis-by-analysis effect, literally just told my wife that last night. Thanks for the advice and encouragement!

@InfallibleCode

3 жыл бұрын

Hah good catch! And glad to help :D

@YasnaKo

2 жыл бұрын

Paralysis-by-analysis - geniunly!

I really love your style, it's just amazing. I'll catch up with your community on the Discord server

@InfallibleCode

3 жыл бұрын

I really appreciate that! Welcome to the community :D

yesssss you’re back!

@InfallibleCode

3 жыл бұрын

Yaas!

@TheComfy

3 жыл бұрын

HAHAHAAA COMFY HERE LMAO

@n8dev

3 жыл бұрын

@@TheComfy YES COMFY

@TheComfy

3 жыл бұрын

@@n8dev OHMYGODD

@n8dev

3 жыл бұрын

@@TheComfy IKR

Oh man, the serious thumbnail gaze. You'd look right at home on a Fast and Furious 9 poster.

@InfallibleCode

3 жыл бұрын

That's what happens when you live your life a quarter mile at a time 😎

Using at first design patterns to solve all your problems normally it ends with an over-architecture solution even a really complex code when it only needs to do 2 + 2. To write good code since the beginning only think in design principles like SOLID, KISS, DRY... etc. With this in mind the next level is when your code smells too complicated, so the time of design patterns comes. Nice video!!

I always wondered why every time I try to implement MVC in my apps it makes them clusterfuck. Your channel is a gold mine.

This format of having a narrative context for the video is very good. Also, your acting skills are improving! GJ!

You've just might be filled the last blank part in my head to take a couple steps further. I've been and still am learning a lot about game development and I've recently found myself in advanced level docs and tutorials but I've made a little mistake that I did not really care about basics and fundementals when I was trying to become a developer at collage and after. At one point I decided to become a game developer I just jumped into it and made a lot of games by learning what I needed to know to write required features and today I'm writing editor feautures for our art people to easily do what they need to do whenever I find time from my actual tasks going on. Many packages that I use are sometimes not enough for what I need them for so now I can easily read and edit most of them. But because of that mistake I started feel the gap in between my knowledge, It really says that I just need to simply learn and practice these and I now feel confident so I know that it won't be as hard as I thought. Thank's for not being lazy to enlighten your colleagues, I might just start take a look at unity community forums sometimes to share whatever I know..

There they are!! Nice to see you 2 back ;D

@InfallibleCode

3 жыл бұрын

WE are so glad to be back ;P

Just jump into coding isn't the way either. From the mere mention of it you were able to say that MVC was not an appropriate pattern for a game. Why? Because it isn't. And you know that not because you developed a "UI heavy strategy game", but because you understand the pattern at some level. However, the reason is not "it is for web apps". There are plenty strategy games implemented over MVC platforms,

@hayabusa1x

3 жыл бұрын

Exactly my thoughts. I was expecting at least a top level explanation of what a game engine needs to do and why MVC isn't a good fit.

@Schodemeiss

3 жыл бұрын

Also, the biggest issue with this video... MVC is NOT a design pattern in the first place. It's an architectural pattern.

@hayabusa1x

3 жыл бұрын

@@Schodemeiss Never thought of that. What's the difference?

@Schodemeiss

3 жыл бұрын

​@@hayabusa1x en.wikipedia.org/wiki/Architectural_pattern en.wikipedia.org/wiki/Software_design_pattern refactoring.guru/design-patterns/csharp Very broadly speaking, AP's are how you might design a system for your code from a very high-level. IE, Do you need Models, Controllers, Views, Presenters, etc. It might even define if you need a Message Bus or might even speak to availability or SLA's. MVC, MVP, MVVM and the like are often more considered as part of a larger framework. They tend not to solve "logic" or domains issues. Think of MVC as one way of separating the concerns of your system. There are many others, including Unity's approach, which is based around Components on Entities. You might even called this ECS. DP's (again, broadly speaking) tend to be aimed at towards solving issues in code with regards to your actual business / domain logic; usually in a way that other developers might recognise. A common one is the "Factory" pattern, which you pass the responsibility of creating an object to a separate class, so you're other class can just focus on the business logic. You might use many DPs inside your code, with that code being part of the overall architectural pattern. You'll notice that MVC is NOT an example on refactoring.guru/design-patterns/csharp (or indeed on many Design Pattern catalogue websites). However, that site is a great reference for lots of different patterns that a developer might use in C#. But as Charles advises, learning them all upfront or trying to apply them to everything is like having the answer already, but you don't know the question yet. Which isn't a productive way to write code. DP's will find there way to you when you need them; usually once you begin refactoring after a furious code writing session.

@JuanPablodelaTorre

3 жыл бұрын

@@Schodemeiss Yeah, the way it is implemented in MVC platforms, like CodeIgniter or Django, it is more of an architectural pattern (considering it is multi-tier and all). But it can be implemented more specifically as a design pattern for UI applications. That's the case with React and the way every component is a small MVC on its own.

So cool to see you'r coming back !! Good video :)

@InfallibleCode

3 жыл бұрын

Thank you! It really is great to be back

I love you man! thank you, Charles and Barles

This was really important for me to see, I've been in this paralysis of trying to learn design patterns and best practices for my game, because the second i start writing the code i know it is incorrect. But the quote from the OG design patterns book is so important. Thank you! I can already feel my productivity rising, im just going to start writing!

Sounds like a great topic to start off the new year!

@InfallibleCode

3 жыл бұрын

I think so too!

Do you use some kind of software that automatically translates what you write? I was looking at your fingers, and the text written should have been along the lines of "asdfjkl;asdfjkla;sdfjkl;asdfjkl;". :) Seriously, nice to see you back! You've been missed!

The title of the video is a little bit misleading, it is mostly about why not to use MVC, rather than what Design Patterns are used in Game Development. The most common ones I've seen are Singleton and Observer patterns. Is there a video in the channel covering specific use cases or examples where they are used? I know there are plenty of content even from Unity GDC covering some of those, but maybe Charles explains it better. Edit, just found a couple: kzread.info/dash/bejne/n6SBkqVvodi3mtY.html Charles explaining Singleton kzread.info/dash/bejne/rIx7qNisZceYfs4.html Events discussion with Json. kzread.info/dash/bejne/eWWWxplugpSWnZc.html State

This is all well and good but alot of the times when your a beginner you write a shed ton of confusing stuff, then realise its not working and things fall apart. Whereas if you know the sort of structure to solve a problem to certain scenarios beforehand its alot better in the long haul. I tried to make a certain game type for ages until i did some reading up on design patterns and i came across something that was a perfect fit, had already been previously solved and made everything a lot smoother in the long run.

Your video are so chill and wholesome.

I can' t be the only one who heard the discord pings and instantly look around to see which server they were coming from 😂

I think you captured it well, design patterns aren't blueprints. Apply them if they provide the functionality your solution needs. For example adopting Extenject and an inversion of control pattern to improve code testability. No matter how much time you spend perfecting your design, the product is going to shift under you as time goes on. Games also live very different software lives compared to a web app or backend service (with some exceptions for games as a service) and that impacts the value (and cost) of these patterns.

You are the light in our darkness of knowledge... I did not know any of these... Good work... Your video style is also unique.

@InfallibleCode

3 жыл бұрын

Thank you so much 😀

Welcome back dude!

@InfallibleCode

3 жыл бұрын

Thank you! 😄

As always, great work

@InfallibleCode

3 жыл бұрын

Appreciate it 🙏🏻

i needed this, liked and subbed ;))

Really great video as always, been researching the same topic, so glad you posted this. Not a big fan of the format as it was a bit tedious watching it on the phone and pausing constantly to read the convo. But that may just be me :)

@InfallibleCode

3 жыл бұрын

I appreciate the feedback! I won’t be doing discord convos for every video - gonna see if I can try a different format for each one to mix things up 😄

I love how my next video recommendation is :"Improve your Unity Code with MVC/MVP Architectual.." XD

So... How would you approach the heavy UI based game? I'm almost considering moving to the new UXML system with bindings as my current solution with callbacks looks so clunky.

The SpicyCatGames comment at 0:15 is dealing with gimbal lock, cuz using euler rotation instead of quaternion rotation

Nobody can refuse a tutorial with narrative!!!!!😤😤😤

I learned how to code with unity ,6 years later i heard about design patterns for the first time , and reviewing my code i saw I'm already using most of them without even knowing them , so this make's sense ,

for me I learn the design pattern on the highest difficulty situation , in my project I only use the simplest form of the pattern.

Two words: Welcome back!

@InfallibleCode

3 жыл бұрын

Two more words: Thank you! :D

Nice video. Def a good thing to be mindful of. Are there situation where you find yourself implementing similar features over and over in game dev though where certain decisions repeat enough to be considered some sort of design pattern? I think talking about those situations would be a helpful next step to this conversation. Like, the whole book Game Programming Patterns by Robert Nystrom... what do you think of the premise of that book?

Me: constantly checking my discord because of the pings in the video 😂 All seriousness, I had no idea what MVC was, but know I do. Nice info! Thanks for the video!

I felt watching drama instead of tutorial👍

Design Patterns can be extremely useful as well as understanding Anti-Patterns. Heck, I've been using design patterns of some sorts since I was programming basic on a PET and much more so with OOP. Game programming doesn't change that. However, ever since the GoF published their series of books, I've found it both a blessing and curse. It certainly helped communicate techniques more efficiently, but you nailed it saying that programmers all to often use it as a blueprint or infallable set of rules to write code. A similar pattern exist where people cut and paste code without understanding it especially in the context of their program. Good on you for briefly covering this topic in an entertaining and memorable way.

coming from web dev, was gonna use mvc too

I was hoping you would share some game dev design patterns...

I have the exact same Watchmen book! :D

Gonna be useful

@InfallibleCode

3 жыл бұрын

I hope so!

MVC is deemed as an architectural pattern more than a design one. Many game-dev companies do use it, or derivatives like the MVVM, for UI ("widgets"). And now that there's a new UI system being developed for Unity, it may be room for MVVM.

yeah, I am also trying to create levels in my code .... similar to mvc but never good enough. It is difficult for me to think in "Unity" style.

Good video. Can totally relate to design patterns being overkill in a project. I was making a Qbert clone and was just learning about design patterns and polytheism. And so as an experiment, I tried to make the game without traditional decisions or looping (i.e. no ifs, cases, for, or while loops). The simple act of jumping became a logic nightmare. A case of while you CAN do it, you SHOULDN'T do it for the simple stuff.

The thing with the discord chat ads flavor but unfortunately is barley readable on mobile and also forces to actually watch the video instead of, as I would prefer, just listen to it.

I don't really get it what the disasing partee is but i don't worry from that because i known haw to handle my project now

Hi, I have a problem with my unity project. I tried to create a WebGL build and everything seems to work as intended except for sound. There is none. I was looking around but found nothing helpful...

so why we should not use mvc for ui in games?

oh what would we do without Barles? ....Neat Video though

@InfallibleCode

3 жыл бұрын

I’d miss him dearly 😅

Arigatou senpai❤️✨🙌

I was the only one who checked his discord messages when in the video msg popped? :D

are you using dvorak as your keyboard layout

What's funny is that I just used MVC for my UI for an online rpg game in Unity. So far it's been working well in keeping me and my code organized. I have been coding professionally in Unity for about 5 years. I use this pattern because I had to access data from a SQL database that gets populated and reported from a unity headless server project and some php code. Fundamentally I wanted to not only separate concerns from my UI and my Data but to also keep information within small. but make it so that if this become a larger project with a larger team that it would be easier to maintain code and work within specific files.

@pp3k07

2 жыл бұрын

How did it work out for you? Would you still reccoment MVC? I'm considering it and so far not seeing what's wrong with the pattern.

@DavonAllen92

2 жыл бұрын

​@@pp3k07 So I would say that it depends on your exact needs. For me I used it firstly because I wanted to learn MVC and secondly I wanted to separate my data, my logic, and my visual game objects (view) from each other so that I could keep each thing separate which would make things easier for me to develop. I also learned that it probably overkill to do this with non UI objects. Some things it did do for me for me was that it forced me to really think about class responsibility and when classes needed to. It also forced a structure to follow which helped me push forward when I needed to make something like a new UI menu or a modal window. It is slower than just coding up a prototype and seeing it working. when combining it with inversion of control it was kind of neat.

I checked my discord 20 times during this video.

@InfallibleCode

3 жыл бұрын

Haha I checked mine like 100 times while editing xD

‘Hey! Can you make a video on how to do this thing?’ ‘Better. I’ll make a video on how I won’t make a video on how to do this thing.’ ‘Okay great.’

Now I know what to do for the next Unity dev job offer that says "you have to know how to implement MVC". Especially because I'm mostly self-taught and come from a mechanical engineering background.

@Xershade

2 жыл бұрын

I'd ask them in the interview, why are you paying me to solve a problem that the engine itself solves?

How did Barles know Charles was reading a book???

Watchmen! My man!

This is my biggest problem using Unity. I am a web dev. All my games come to mesh when I start to code, and all the ways that I have tried to make manageable projects have failed. End I stop to make a game when I can't find anything anymore. This happens every time.

Awesome stuff, thank you. *Pigeonhole is actually one word

So I should ditch my design patterns in game dev book?

6:30 Is this when you spend forever writing your code because you constantly think of cleaner ways of implementing code? If so, I have this terribly. I'm such a slow programmer at my software development job.

Can someone give me a complete rundown on architectural engineering? I am planning to construct a swing set.

@InfallibleCode

3 жыл бұрын

A swing set should be easy. Just get a civil engineering degree, take a few udemy courses, and then buy all of the materials and get to work without any sort of planning or forethought😅

Nice keyboard. May I know brand name please?

Don't we wish we all had mirror self genius?

pigeon HOLD?

This was so deadpan, I was expecting a punchline at the end x.x I still cannot tell if this is a joke or not lol. I'll just throw in my 2 cents...design patterns are important because they are solutions to common problems that are agnostic of framework/language. So of course people should be using design patterns! Game engines are built ontop of those patterns and it is very beneficial to understand and use them in game development. Coding with only confidence and waiting for a pattern to just "emerge" is a good way to become a spaghetti sous chef.

@cileth

3 жыл бұрын

@@bezoro2008 I mean I agree in some sense, but disagree that simply writing "simple straight forward code" is always a good way forward. You gotta understand, all of unity is coded with design patterns in mind providing the developers with an abstracted SDK for devs to use. Like the whole component architecture is already an implemented design pattern called the composite pattern. If it weren't setup that way (along with almost all other systems provided by unity) code would be much harder to maintain. Yes you can get away with simple straightforward code...because those systems are in place and you have the ability to maintain straightforward code using them. But say you needed to implement a custom input system. It would be advisable to implement a design pattern like the command pattern to make it easier to implement, extend, and maintain. Coding just to code and get things done will only get you so far. If you don't code with extensibility in mind it's going to be very painful to refactor later. Especially if multiple people are working on the same project. Of course, some things might never need to be refactored and a simple implementation works fine.

Keyboard?

I love how you think "beginners think about what design patterns to use". :D Most beginner questions I run into is: "Hey, I wanna make GTA27, give me code?"

@InfallibleCode

3 жыл бұрын

Haha yeah well there are beginners that dream big and beginners who put in the work. The latter group usually finds design patterns and naturally leans on them a little too much to solve their problems

@nGAGE0nline

3 жыл бұрын

​@@InfallibleCode I certainly agree with your video. I often find myself thinking far too much how to fit my code into a ceratin pattern before I just make it work first. Usually having to scrap it and then take the latter approach :D

Aaaand.... just like that, Barles became my psychiatrist.

Hol up, is it "pigeon hold" or "pigeon holed"?

@InfallibleCode

3 жыл бұрын

That was a typo - It’s pigeon holed >

Gud video

twist plot: they are only one person.

Pigeon hold? Isn't it pigeonhole?

I was legit going through discord trying to figure out was messaging me.. LOL (edit) : i was on another tab

Can't read the discord lines in my phone too small break my eyes

I think the biggest thing I see is people are mainly not getting, MVC is nice but Unity is already built on EC (Entity-Component) you don't want to break the components down any further. Combat component should be self contained so if its extended or removed all things it does are removed. Basically people are breaking down something that deals with the issue (combat for example) and breaking it down into sub components that don't need to be broken down. Maybe you have sub components for combat that are like Melee, Ranges, Magic, Summoning, etc as if something doesn't have those styles it doesn't need them, but just breaking down into logic, display, and data for no other reason just adds bloat and complications. Basically the problem MVC addresses is already solved in unity, we're using EC to handle data, logic, and display. The question now is what should each component be responsible for. You obviously don't want a combat controller holding inventory data and functions as what if you have an entity that needs items but doesn't fight, like a shop keeper, and don't want EVERY npc with a bag to be attacked by the player. So yeah it's like they said in the video its more people are looking for an answer to a question that's already been solved. Unity handles the data, logic, and display parts already so why do you need MVC built on top of EC is the real question. EC and MVC are basically the same layer in your application, they both handle the same question so you can't and probably shouldn't have both at the same time. (That is to say don't build EC on MVC or MVC on EC. You can have an MVC bit and an EC bit but don't build them on top of each other. They're two completely different answers to the same question.)

I came for information not a short story.

I am very happy that I only wasted 5 mins 19 secs of my life to this video including this comment

"How to use MVC in unity?" My dumbass: oh wow, he's trying to make a game like Marvel vs Capcom. That's dope

what a slow intro, rip in peace adhd people

@InfallibleCode

3 жыл бұрын

Appreciate the feedback!

I do not like the switch to the over the shoulder mid typing. If you are going to make typing part of the lesson, I need to be able to read it while you are typing it and not breaking mid sentence over and over again.