Question In need of help with learning how to accomplish what I have in mind.

I am fairly new to unity, and game design as a whole. I have been researching and learning the basics of blender and unity for the last few months, and I have successfully made assets and gotten my player walking and all the basic foundations done. I am wanting to have a system similar to Car Mechanic Sim or My Summer Car, where the player can assemble an engine and truck body parts to make a running vehicle to use for other things to do in the game, but I have no idea what i need to do to make something like this work, and I can not find any good threads that explain it. I just want to know how to achieve making the engine parts attach to the engine and body parts to the chassis, and once complete it is a running vehicle for the player to drive. Any help with this would be greatly appreciated, thank you!

 

Tutorials, LOTS of tutorials. You will never do this all at once.

Instead, ask the question "Can I ...?" and keep doing it over and over, like this guy:

Imphenzia: How Did I Learn To Make Games:

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That's how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don't make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there's an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Finally, when you have errors, don't post here... just go fix your errors! Here's how:

Remember: NOBODY here memorizes error codes. That's not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

The complete error message contains everything you need to know to fix the error yourself.

The important parts of the error message are:

- the description of the error itself (google this; you are NEVER the first one!)
- the file it occurred in (critical!)
- the line number and character position (the two numbers in parentheses)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don't have to stop your progress and fiddle around with the forum.

 

If you are determined to achieve a specific goal, it is essential to develop a comprehensive plan. Begin by breaking down the goal into smaller, more manageable tasks. Identify potential obstacles and devise solutions to overcome them. In the field of programming, when the final code is unclear, it can be helpful to write pseudo code. This involves expressing the program’s logic in plain English before translating it into code. This approach can help clarify the program’s structure and facilitate its development.

 

If this is too much for you, then you need to start with much simpler stuff and learn what programming is, how we instruct the machine to do anything, but also why we do it the way we do it. There is a whole mountain in front of you, but don't get intimidated, start small and new things and knowledge will inevitably open up in front of you.

Apart from the driving itself, what you want is fairly simple in the grand scheme of things, and even the driving isn't that hard, but expect it to be a project in itself. In fact, try to consider that in games like My Summer Car, the real features of the game are the map and the driving, along with many interactions with the world and the car itself. It's the user interface and many engine- and shop-interactions that make this game really complicated to implement, but the actual concept of having different parts and assembling them into whole is nothing, really.