Відео

Oof, “very bad presentation” - a bit harsh, but point taken 👍 thanks for the pointers!

​@@DrowsyFoxDev I thought that it was really helpful. Got it working, and added a GetType() reference in the output, so that you get both the class, and the specific object where the log is called from. One thing that I'd like to fix is that, currently, when clicking on the log message, it sends you to the Log method you made in this video. Ideally, it would send you to the place in the code where the method was called from. The information is there (You can scroll to where the call was made in the console, and double-click it), but when you double click the main log entry, it takes you to this Log method. I even disabled the method in the stack trace, so that the messages were uncluttered, but it would be nice to have that smooth, double-click, go to the place where the method was called, workflow. Any idea how to achieve this? Anyway, thanks for the video. Like I said, it was really helpful!

in the chapters

😳I don’t think I wrote any chapters, but I see the one you are talking about 😶

Hey Chris! I’m actually using Rider as my IDE, not VS - it seems to be just a native feature to it. There is probably some sort of plug-in for VS that can do the same thing, but unfortunately I’m not familiar with VS at all 😞 If you do find it, please let me know what it’s called!

Hey! Unfortunately, the built in console does not seem to support emojis (bummer! I tried it actually before the video) I ended up using Unicode characters instead (like the basic smiley face and exclamation mark) I believe other console assets ditch the built in logging window in favor of their own implementation, and that’s how they can get emojis into their logs. I wish it was native to unity’s console though!

Once again, sorry for letting you guess, but that's not what I meant. What I meant is that you're putting a functionality that only makes sense in specific local context (colors the string only when you put that string into elements which support html color markup), globally into a string type, everywhere. Now all your strings, everywhere in the project, have this function, which has a very global, generic-sounding name, but which only makes sense in very few specific places, and for all other places, it gives what we could call "bad/broken output". That's the wrong usage of extension methods. Since you're extending the type itself, you should use it only for functionality that makes sense *for the type itself*, regardless of context, as opposed to only for a specific combination of the type+some specific place where it can be used. That's what I meant. It's wrong from the architectural/structural point of view.

@@MidnightSt thanks for the explanation! I summed up our other convo and edited my pinned comment so it’s easier to find! Cheers!

Ayo! Can you elaborate on why exactly it’s bad? It’s convenient and provides a way to color both TMP strings as well as console strings Would love to know the downsides!

And for future purposes, would have been nice if you just explained why it’s wrong instead of hinting at it and expecting the other side to know “why that’s an extremely dumb and bad thing to do”, not very nice wording

You are correct, the method is vulnerable to html injections as is. So thank you for pointing it out (though it felt condescending & in the form of a riddle, I would have appreciated you simply pointing it out!) To improve this extension & fix the vulnerability, we could take a Color argument instead of a raw string and convert it to html hex color using ColorUtility.ToHtmlStringRGBA I’ll try to be more careful in the future - but mistakes do happen 🙂 Cheers!

@@DrowsyFoxDev "You are correct, the method is vulnerable to html injections as is." no, that's not what I meant. First, sorry for how I wrote the comment. At that moment, it was kinda condescending, I was in a bad mood, I apologise for that. What I meant is that you're putting a functionality that only makes sense in specific local context (colors the string only when you put that string into elements which support html color markup), globally into a string type, everywhere. Now all your strings, everywhere in the project, have this function, which has a very global, generic-sounding name, but which only makes sense in very few specific places, and for all other places, it gives what we could call "bad/broken output". That's the wrong usage of extension methods. Since you're extending the type itself, you should use it only for functionality that makes sense *for the type itself*, regardless of context, as opposed to only for a specific combination of the type+some specific place where it can be used. That's what I meant. It's wrong from the architectural/structural point of view. Again, I apologise for how I commented, and how I let you guess what I meant, I was in a bad mood. However, I appreciate that you took the time to think about it this much.

@@DrowsyFoxDev anyways, you just got a subscriber, large part by how you handled my ...suboptimally... written comment. :)

Ayo! Private would mean only you, and anyone you give explicit permission to in project settings, can access the project and its source files Public would mean anyone can access it or look it up - they can submit a PR, fork the project, clone it, etc which I believe you can control more in depth in project settings Hope it helps clear it up a little bit!

​@@DrowsyFoxDev This helps a lot already, thank you!

There is an Odin attribute being used called “OnValueChanged” that monitors the value bellow it and triggers the function given to it once it does There is a link to Odin in the description, it is a paid plugin - but you can often find it on a sale! You can check out the source of this project to see what other attributes I’m using, though the rest are just for cosmetic reasons I believe Cheers!

@@DrowsyFoxDev got it. thanks!!

Scriptable objects can be super useful for inventory systems! I might make a tutorial about it soon 😉

Glad you think so! ❤️🦊

You are too kind 🙏 thank you and hope you enjoy the videos to come! 🦊

To keep it short, I’d make a scriptable object per each kind of ground like steps_wood steps_metal and then attach these to the respective ground - then when a player steps over it and is in active moment, play the sound on loop and stop the sound when the player isn’t on that ground, or not actively moving Good luck! 🙌🦊

@@DrowsyFoxDev I'm a bit new to that, but I'll try to figure it out.

@@FyresGames feel free to join the discord and ask for help! I’ll do my best to help out, link in the description 🙌 I might make a tutorial in the future if time permits/there Is demand 😛

For now you can use the gist I linked in the description to start using this tool, in the future I’d love to release these as packages but that requires a lot of time effort & research I’m kinda tight on at the moment 😅😅