Відео

My biggest problem with interfaces in Unity is that it is not serializable out of the box. I do love using interfaces, but that single limitation makes me almost never use it inside Unity (only interfaces from System itself).

This was a good video. As someone who has been using Unity as a game designer since 2016 and is self-taugh in coding, this video helped me understand the underlying system under the Action type that I've been using for years :D

Wtf is this. Just make games people

Subbed.

It would be useful for you to add a link to that GDC talk to the description of this video.

Book , на універзітї

Couple of additional tips for aspiring developers here. 1. Avoid walls of text as much as possible. It is the worst way to transfer the complexity of game design information. Text should only be used to specify things that cannot be properly explained otherwise. 2. Try to separate things into different design documents also. A system should not be detailed in a level design document, for example. Nobody wants to have to find how an AI should behave through the design document of dungeon number 6. It's all about defining through encapsulation and teaching multi-faceted elements of a game in the fastest way possible. 3. Use a variety of design document format. Some things are more easily explained through specific design document formats. Here's a short non-exhaustive list: - Storyboard - Mind map - One pager - Flowchart - greyboxing

soo there's no hotkey to just hold, click the object and free move it like in blender?

I've found Miro quite handy to organize our thoughts for a game we're making. It's pretty good since there isn't the limit of paper space and you can technically fit the whole thing on "one page". Very handy for art references and music as we can collaborate some sort of "mood board" together. Plus, if we ever need to add someone to the team we can just invite them.

Crucial for all game devs. This video tought me alot 😀

Great video! Could you please go into more details with an example in another video? Like a video focused on Game Design as well as writing an effective GDD with a full example from start to finish (One-Page example).

Yknow, this is something i always wanted to know how to do. My one and only attempt was a long word document that i organized really well. And i didn't know if this was the best way of doing it. The one page rule is really interesting! Thanks for the new perspective

the timing couldnt have been better

It sounds good, and seems to simplify, but it's not as easy as it sounds. It's like when first learning how to build a resume or a business plan. Dozens of templates, dozens of advice, dozens of opinions. Which leaves you with too many possible decisions. Until that day when it clicks, that you put whatever the heck you want because you're a pro in your industry and know what matters, and then you min max, the minimum effort for maximum impact. You express it adamantly, as a statement of fact. No begging, no fluff, no buzzword salad. As a real pro. This means. You'll probably write it. Struggle with execution. Start other intermediate projects. Rewrite. Write for something else. Pivot. Give up. Start over. Each step, side stepping but learning. Then. If you trust the process of learning from the struggles, you'll find yourself knowledgeable in the many hats. Your iterative changes didn't seem to be much further. But now twenty or thirty iterations along, they add up. Two steps forward, one and a half back. I thought I learned this, I did it before, but now I'm having to do it again, and that again, but I remember that. The process. The grind. The set backs. The determination. If you have grit, then you'll eventually accomplish it.

he sounds like GMTK

I'm making my game in the most ADHD way possible. Introducing one bug at a time 🎉

Shallow video not a must watch

Thanks for motivating me to do it for real this time. I used the example from PirateSoftware, but it's too big and I prefer the focus the one pager provides.

Thanks for the video. Fully agree. Apple has got this free app called Freeform. I Used it to design my first Inverter system. I was easy for me to keep a one page document with an overview of my project without having to create folders and files about everything. Freeform also allows you to drop images, videos, links, pdfs etc. onto the one page. It is still a very easy one page document I could open and study with the added benefit of containing complex details. PS. Also, look at a program called Simple Mind Pro that has a more mindmap approach to it.

Checked out various tutorials about this topic but my negative iq couldn't quite fully grasp the concept. Now after watching this video I can confidently say that I REALLY regret not knowing about this sooner. I'm 2-3 months in on a project and this could've made my life so much easier. I'm not sure if refactoring my previous progress is worth it so I guess i'll try implementing events going forward

Very cool idea for a video. Thanks for the epic knowledge.

This is the most simplest explanation of a Game Design Document I have seen till date.

😮 am the first one to put a like

This is super interesting!

Extreeeeeeeeeeeeemely useful as always. Million thanks

Very good explanations (and video quality) 🙃

I've ran into problems trying to use regular c# constructors in Unity to do anything other than getting or setting variables. I think they get called multiple times for Serialised structs and classes, so that can cause problems of stuff happening more than once. So Unity expects you to use Start / Awake / OnEnable, but it's annoying because if you're making new c# classes that don't inherit monobehaviour, then Start / Awake and OnEnable are not available.

Also helpful to know (though not mentioned in the video) is the fact that Start() can be a coroutine - just change void to IEnumerator. This has come in handy quite a few times for me: private IEnumerator Start() { // Do something right when Start() is called yield return new WaitForSeconds(0.5f); // Do something a some time later.... }

Hi, i'm a game dev instructor, thanks for spreading out this information for everyone, that's the main cause of lots of errors on games and a lot of people still don't know about that. Mainly by users of the Singleton Pattern or really any script that depends on the initialization of another object.

The first time I saw an error in your videos! (typo in the word SPHERECAST) So you are not a machine 😅 I love your content! Your ways of explaining, showing and suggesting are the best since @Brackeys left the scene 😊 Edit: typo 😇

interesting tip, have everything active at first and then deactivate the ones you don't need, just to get Awake out of the way. I guess if we have a lot of objects with scripts on them, it might boost performance at the start

Thanks.

Which one of these would be best to rotate my character's vertical axis of rotation to a slope?

Finally an explanation I can understand, good job.

Thank you so much, this is brilliant. Going to need to watch this a few more times to really absorb it all. Subbed.

You are the goat at explaining. Why did NO ONE else said, that i can use Action without the event keyword to allow invokation from the other classes... It was such a pain in the ass

Thanks for the great and detailed explanation.

8:26 how did you do this? Have the brackets engulf the line by shortcut?

I'm surprised you didn't make any mention to the methods explained on your 'Connecting scripts on the same object in Unity' video where you had a class that stored the actions an object could execute and other components subscribe to them. I think that way of doing things is perfectly explained in that video, but I would have liked you to talk more in depth about when to implement that style of method over the ones described on this video. Either way, brilliant information and lovely explaination. Thank you so much and keep them coming!!

Hey man, this is a really great video that touches a topic that we struggle at work too! Just a quick question, at 4:04 you mentioned that Ground Check could be implemented via Inheritance, would it be better to make Ground Check as an Interface instead? Just figured that an interface is more modular. Thanks in advance ! :D

How to hit Mesh Collider which is not convex?

hey i'd be interested in a video about attributes in unity. ive seen some but dont completely know how to use them, create them, and most built in ones.

"How do you use lerp in your projects?" Me: "the wrong way" Hope not to do so, anymore.

I separate feature and architecture, any code will have some specific cuisine, so brstvto contain what's unique in single places. For example, move is a feature, it takes input modifier and position and output back new position, it shouldn't know about anything else, the manager is the one responsible for linking input type, position and controller results to the move element, that keep bug seeking into two type, feature implementation bug, or architecture communication bug, it help refactoring because you either rewrite features or rewrite architecture, even when both need rewrite it's a clear separation of concern. In practice it makes your code more modular, but modularity is only as good as how many utils class your code depends on 😂 the math class sipping everywhere is inevitable.

Inheritance… in modern oop… that’s gonna lead to disasters untold. I’m not much of a Unity dev but can’t you just make a global function that can be referenced that checks for the entity state?

Legend. I just have one specific question... I've setup the Scriptable Objects Game Events system on my game, but sometimes I want so that when an event is triggered, a value is returned from the subscribers, but I don't see with clarity how that could work? I've thought about using Funcs, because it can return a value, but how to I merge the concepts of Funcs and Scriptable Objects Game Events in a clean way? Thanks!

I've personally been exploring a composition architecture to go along with how Unity already does game objects and components. Unity Events help keep components ignorant, but I fear I'm going to end up over-using them...

This was clean, simple to follow, useful. Thanks.

I submit that anyone who thinks an entire game's worth of code should go into one script, doesn't yet know enough about what they're doing. This is why we have principles and guidelines and architectural patterns.

just started learning unity and your vids are a breath of fresh air, easy to follow and very helpful!