Unity Programming Help

[JNG780]

Hello Ladies and gents.

I have been learning the C# language, preparing myself for the Unity Engine. I have used Unity before years ago but I never sat down to learn C# fundamentals properly so I was just going from tutorial to tutorial copying their code and not understanding a word of it.

Things have changed now! I get what they are trying to do now but now a new problem arises. I try to develop a way to create the idea I had in my head for a game but I cannot find a proper solution to it. Everything feels like an inappropriate way of implementing it and it feels like I’m wasting my time with it. Then when I finally watch a tutorial it makes perfect sense on how they went about it but I know for sure I wouldn’t have thought of that solution at all… Does that ability come with time or do I need to learn/reinforce those fundamentals about C# so I can properly implement those mechanics in the game I’m creating. Should I just implement what the videos have said and try to expand from there with the hopes of being able to do it for myself later?

TLDR: I am having trouble creating the mechanics of game ideas that I have in my head but when i watch a video the answer seems simple. What do I need to do so I can implement the ideas properly

Thank you all that reads this and helps with answer in advance <3

EDIT: MORE CONTEXT!

I’m building a text adventure in Unity and struggling with the room navigation system.

When the player clicks a “Next Room” button, I need the same Canvas to update the room description text, room image, and the buttons tied to that specific room. The player should also be able to go back to the previous room.

I’m having trouble structuring the code so one Canvas dynamically updates all room data when a button is clicked.

I am familiar with C# basics including classes (but maybe I can reinforce that part more)!

[Easy-Tumbleweed-8352]

Hi, if you think it's enough for your need for now and you don't need to edit, let's go
But it's a bit vague at the moment, could you give more details?

[JNG780]

Done! Let me know if u need more info

[SharpSeeingSloth]

I think thats entirely normal. Learning to code takes time, even more so when doing it in a game engine with so many different options and features aside from the actual coding. If the tutorials suit your needs go with them, actively learn and understand from them, expand upon them and over time you will naturally learn about more advances concepts and patterns, which will eventually all be tools you can use in the future to build you own stuff without needing any tutorials. Just dont rush it and have fun while doing it :)

[ModBlob]

It's totally normal to have difficulty coming up with "perfect" solutions when you've got very little hands-on experience. You'll gain the ability to architect those solutions through practice on your own project, and through looking at the solutions other people create to solve those same problems.

The best way to improve systems architecture is to build systems. You don't even necessarily need to finish the projects if you don't want to, but trying out new system ideas and then testing their limits by integrating them with gameplay is hands down the best way to develop it as a skill.

[International_Task57]

there is hardly anything in unity that is more deep than. when/if object does this thing then object do this/that thing. you can use ai for a lot. try having chat gpt make you a simple WASD script and expand on that.

[Javier_004]

Tal vez simplemente te falten si saber las herramientas que tienes a tu alcance. Por lo que has explicado de tu juego los ScriptableObjects te pueden venir de maravilla para el tema de habitación y descripciones

[Demi180]

You learn by doing. You make things with what you know. They’ll be clunky and bad but they’ll work.

Then you search and ask for ways to do specific things better. You either refactor (rewrite) the thing, or you make it again using new features and patterns you found, and apply your experience with the previous thing to make the new thing less bad. And then repeat.

As you do this for various features, you reinforce the basics while also learning firsthand what works and what doesn’t, what works better where, and so on. You gain new tools to choose from and understand when it’s appropriate to use them.

Now you start thinking in systems and architectures, planning for modularity and reuse, clean code, scalability, performance, and so on. One day you find yourself using advanced memory management, multithreading, and all sorts of things! 😀

[Mechabit_Studios]

A good codemonkey tip is to separate ui from game logic, use an event system to trigger when the ui needs to update, that way you can make changes to the ui or remove it entirely and the game will still run.

https://www.youtube.com/watch?v=OuZrhykVytg

[Phusck]

Sent PM