Unite 2016 - Overthrowing the MonoBehaviour Tyranny in a Glorious Scriptable Object Revolution 

How did you create the "table of contents" links? I can see from hovering over the links that each URL link consist of "URL" = Xseconds so this can be made by calculating the time in seconds and then adding that additional seconds identifier at the end, is there an easier way to generate this?

zjjackson101 any time you say two numbers separated by a semi colon 13:37 it creates a link to the video your comment is on

People who time code RU-vid videos are saints.

@@grahamnelson203 People who make soundtrack videos and don't set times for the songs are monsters.

same tbh - Matt

I know. I've tried getting into gaming since i'm spoiled by old masterpieces like Rayman 2 and 3 and Resident Evil 4 and Psychonauts. Creative, long, intriguing, FUN and really immersive with it's themes and solid gameplay. But when I play Risk Of Rain 2 or LoL I keep ending up saying. SCREW THIS i'm gonna go -play Minecraft- work on making real games instead. And then I end up sitting in a Krita animation/drawing, Blender modeling/rigging/drawing texture or programming and learning new things about Unity. Or I look up WW1 and 2 guns and stuff and just think: "WHY ISN'T ANY OF THIS IN COD OR BATTLEFIELD?!"

Same

@@magnusm4 because world war is boring. All world war games died in months.

100% agree. I enjoy being a creator not a consumer 😀

Check out my two live sessions: Text Adventure Part 1 and Pluggable AI. Both use the delegate pattern described here with ScriptableObjects. - Matt

nipponese ah, great to know

Me too!

If there was an item named "Scriptable object" in create menu, most users would've known about it.

Do you have good recent talks about Scriptable Object usage and patterns ? I'm really interested in that feature

There is Text Adventure tutorial on both Unity RU-vid and Unity Learn that uses a lot of scriptable objects, which is where it told to check this talk out.

Yes. He is very good!

Yeah, this solves so many problems that I ran into when I was learning unity and game programming a decade ago. Especially back when using unity in version 4 or 5.x before the multi scene paradigm. you'd have to have an init scene with your singletons that call dontdestroyonload and persist through your project, so in order to test anything you had to start from that init scene

@@unitydev457 The moment I saw "Use dontDestroyOnLoad" being referenced as a solution to keeping Singletons around from scene-to-scene in the official documentation, it was a bad code smell all over. It felt like a hack, but an officially required one. It's useful for niche things, but I don't use it for anything important.

where can one find this t-shirt?

@@SimpleManGames 😔not working

yo! you can't switch object ( SO is object ) example you define the enum is SOkey : ScriptableObject , use it as enum, create some in the project. you can store the whole enum you just created in a dictionary dict then, any script wanna use the enum just call Get(SOkey key) { if(!key) return null; return dict(key); } with this you just use the enum and get what you want using a dictionary, not switch. hope my workaround is good, if you think of better ways can share with me, thanks.

the point of SO is to get away from enums and switch statements.

anyone have functioning version of this?

It works by building a Custom Editor and using EditorGUILayout.MinMaxSlider.

For anyone looking for a workaround, I like using two normal ranges for that. First one is the default value, second one is the deviation from the selected value. You don't get that total minimum and maximum though, like if you shouldn't go below 0, yet you could put 0 in the default value and 1 in deviation and end up in -1 so you need to clamp the values in your code. But yeah the ranged float is really nice.

It is

It's *mostly* the same, but I streamlined some parts, and added a little more detail in others based on feedback from the Europe talk. If you've already seen the Europe talk and grokked it, you probably won't get a ton of new stuff from this one.

Richard Fine I ended up watching this first, then struggling to watch the Europe talk afterwards, since I had already seen this. Thanks for opening our eyes to Scriptable objects. Now all I have to do is come up with my own MVVM implementation using these ;)

It's the github link labelled "Get the Assets Here" in the description

@@sulfurasmr6365 Thank you, for several things. Completely forgot this talk and rewatched it, good gems. And why didn't I see the link last time? who knows =)

In general, the Abstract class = Interface, but have some advanced in Unity university (at current moment "till version 2021") - *it can be simply serialized* (if it derived from Monobehaviour or from ScirptableObject is doing automatically). Therefore, it can be very simple showing in Inspector (you can write amazing & useful Custom Editor & Properties Drawer). And also the variable (field) which storing this reference automatically saved (updated) in Inspector. If you try did the same for the interface, it's more hard and have some limitation (can find some examples on unity forums). Interface have some advances vs Abstract Class (in c#) in very hard object oriented structures, but it is not demands very often in gamedev in Unity. And you can create a collection of separate abstract classes for each variant of a different combination of different interfaces (AbsC1 : ScirptableObject , Inteface1, Inteface3 ; AbsC2 : ScirptableObject , Inteface2, Inteface3 and so on). If in future of UNITY (may be) the interface became serializable, may be in this case the it use in this case became more appropriate. But what did, in this Example, *Richard Fine & Co (Custom Editor & Properties Drawer) it is AMAZING work for real production environment* (when you have a big team - separated Game Devs & Game Designers). If you work on very simple project (and you didn't separated the Game Devs & Game Designers) you can more prefer doesn't spear time on useful interface for "Game Designers" and doing more in C# plain code, but it will hard to support & modernization in future (the same as with documentation the code)

@@denisgoodman4492 Thanks, that all makes sense. I forgot about the serialization issue because I use Odin, which serializes interface refs no problem. Another advantage of interfaces is you can inherit from multiple interfaces but not multiple abstract classes. One example for why this is useful is because it allows one SO to contain all enemy data, including its sprite, sfx, etc, for example, in a single asset. The audio manager can then reference it also with other ISFXProviders, a UI element can receive any ISpriteProvider whether it's an EnemyData or BuildingData, etc.

@@travlake I am not using Odin, but this asset completely rebuilds the inspector, in which case it can be useful if you need to serialize the interface. As I said, you can create a complex abstract class and put all the required interfaces in it. Maybe not as elegant as with interfaces + Odin , but you can save some money :) ... Ultimately, the choice of a particular method is a matter of taste :) ... Thank you for information regarding Odin, i put it in my notes.

it's diffenitly bad solution. Never do that. All components must be precashed

What makes you think that?

I remember each scriptable object is about 5kb if I am right. However, I never actually tested how it would increase the actual build size (if in Resources), just during Editor.

They should be exactly the same size as MonoBehaviours (they're literally the exact same class on the C++ side of the engine). Shouldn't be anywhere close to 5kb unless your class definition is very big...

I did several tests, and made a conclusion that when compiled into the build, expect: - a large-sized monobehavior to *shrink* by x12 - a scriptable object to shrink by x40 times than its size in the project panel This means all of our c# code becomes a lot, lot smaller once compiled :D

I mean, С++ is one of the main reasons why many developers still don't use UE, even despite its recent achievements.

not even remotely similar.

in very general terms - it can be simply and quickly store on disk (in Unity the serializable objects, use to tune game, automatically stored its state). You can write simple game did write not any line of code, simply drag&drop different objects and tune its parameters (all these parameters it's a serializable objects).

All of your variables, jump height, attack speed and so on all have a spot in your computer's memory when you press "run". So, in your "PlayerScript" you could set jumpHeight to 1, but what if you want the jump height to increase when you get a power up? And even more importantly, what if you want to exit out the game , come back and STILL have that jump height have the boost? Well, every time you press "Run" your jump height is going to be what ever you set it as in your code! Unless we find a way to give the illusion of "remembering" our jumpHeight. Luckily your computer has a hard drive or a solid state drive! So what we can do, is we can "save" that jump height value to some sort of file in a folder somewhere on our hard drive and then whenever we want to know what the jump height is in game, we'll just check that file (and conversely, save to it as well). Serialization lets us do exactly that, remember when I said that your jumpHeight has a spot in your computers memory? Well every single time you press "Run" your computer might be giving it a different address....and addresses are how our programs know which variable is which so we can't just give the file all the memory addresses, and not only that but there's not just one type of int, there's bigger ints and smaller ints types! So there has to be some sort of standard that everyone adopts, and that standard is called Serialization, serialization lets us take our jumpHeight, and turn it into bytes (the building blocks of computer data) and store it away in some file that we can take from whenever we want that data.

Hi, he said the "hide" flag, to stop the garbage collector clearing it up. Hope that helps you :)

In case you didn't figured out yet, they are just custom-made structures, with Editor code to tweak them in the Inspector. See for example : bitbucket.org/richardfine/scriptableobjectdemo/src/9a60686609a42fea4d00f5d20ffeb7ae9bc56eb9/Assets/ScriptableObject/Audio/RangedFloat.cs and for the editor : bitbucket.org/richardfine/scriptableobjectdemo/src/9a60686609a42fea4d00f5d20ffeb7ae9bc56eb9/Assets/ScriptableObject/Audio/Editor/RangedFloatDrawer.cs

Hola. Qué querés saber? Tal vez te pueda ayudar en algo. Pero es muy importante que aprendas Inglés si vas a programar/hacer juegos

Matías Pierdoménico claro q si bro es muy importante, el pero es q soy medio wey para el inglés 😭 , y sigo todavía con mi proyecto será en 3d si gustas t paso mi Facebook José Raúl Cordazar broadius y muchas gracias bro por brindarme d tu tiempo

Buenisima tu iniciativa : ). Aparte de los tutoriales de Unity en su página, recomiendo a lo mejor también utilizar algo que básicamente funciona "out of the box". Hay un Engine en el asset store para hacer "infinite runners" y juego de plataformas muy fácilmente. "Corgi Engine" se llama. Hay también add-ons para él.

Alejandro Martinez-Chacín gracias ya ando en eso, de echo me encuentro modelando los objetos que quiero en blender y de hay los paso a unity, llevo muy poco pero lo terminaré jeje