Satania, a Quest of Destruction

Ok so I am pretty new to unity but I figured I would make one of these and see what people think. Sorry for my grammar in advance ima get my point across but im not worried abt proper grammar rn so I am making a game called satania and it is based off of an anime i am making atm ik that sounds like another S***ty game paired with a S***ty anime but hear me out so in he game the main character Rizzutu ( Riz - oo- too ) is a demigod of sorts and was created by the deities of heaven to be a mortal with the powers of a deity but still killable bc he is mortal n all and he is eventually tasked with killing the current demon king to stop hell from taking over the overworld and destroying heaven a lot more happens but I don't want to spoil everything I am posting this on here to get feedback on the games premise please lmk what you think

 

Get busy with tutorials... LOTS of tutorials. You have a lot of catching up to do.

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.

 

thank you very much i appreciate the advice

 

hey how are you going to make an anime wtf?

 

I'm pasting a summary of my experience with guides. I went through dozens of tutorials from Youtube, but finally I landed on the official Unity platform (in my opinion, not very intuitive at the beginning).

In conclusion, it is best to familiarize yourself with the tools and how to use them first, then you will not waste time searching for the basics. After 13 weeks (4-5 hr a week), you will be ready for more advanced topics and understand other guides faster.

1. Beginner Scripting: https://learn.unity.com/project/beginner-gameplay-scripting
   
2. Intermediate Scripting: https://learn.unity.com/project/intermediate-gameplay-scripting
   
3. Junior Programmer Pathway: https://learn.unity.com/pathway/junior-programmer
   
4. Manual: https://docs.unity3d.com/Manual/index.html (not to read it all, but to use it)

 

im going to write the script and either learn to animate or hire animators

 

i have the knowledge of coding i got the basics down so i think ill be pretty good thank you for your help

 

you know how much money that costs? 100k $ for a season

if you have 100k$ to spend why do you ask questions on the unity forum

 

bc its more fun that way

 

ok buddy

 

just you wait eventually i will release all of it and if I do it right it will be a 12/10