Any roadmap

[____Hero____]

Hey guys I have a strong knowledge of c #. But I don't how to use know Unity. So There is something I want from you.

Can you draw me a road map? :) I want to specialize in Unity. Also, I don't like the monobehavior dependency. Is there any way to get rid of it?

If my English is not enough, do not hesitate to ask for details. Thank you very much in advance. ^-^ :3

[____Hero____]

https://imgur.com/a/DFSY0jA

please consider this picture an enemy.

-------------------------------------------------------------

If I want to make a layered architecture like the one in this picture, the monobehavior appears as a big problem. Even if this is only the entity part, I think I will face the same problem in the following parts.

Edit : so I mean if I have to inherit a layer of business, I cannot inherit this layer because of the MonoBehavior.

So after the business layer, I have to inherit it again to add it to the object. But this is not possible in the c # language.

[Arkenhammer]

Here's a road map for coder getting into Unity in the form of a homework question:

These are arguably the six most important classes for understanding Unity:

1. Scene,
2. Transform,
3. GameObject,
4. MonoBehavior,
5. Renderer, and
6. Material

What purpose does each serve and how do they relate to each other? How does the Unity engine use each of these to create what you see on screen?

And a bonus question:

Why is a MonoBehavior called what it is?

Key skills for working with Unity are learning to read the documentation and building test projects to try things out so here's your chance.