Resolved Assets/scripts/PauseMenu.cs(49,14): error CS0117: 'Time' does not contain a definition for 'timescal

Hi. i need help with this error Assets/scripts/PauseMenu.cs(49,14): error CS0117: 'Time' does not contain a definition for 'timescale'

Code (CSharp):

1.  
2. using System.Collections;
3. using System.Collections.Generic;
4. using UnityEngine;
5. using UnityEngine.SceneManagement;
6.  
7. public class PauseMenu : MonoBehaviour
8. {
9.     public GameObject pauseMenu;
10.     public bool isPaused;
11.  
12.     // Start is called before the first frame update
13.     void Start()
14.     {
15.         pauseMenu.SetActive(false);
16.     }
17.  
18.     // Update is called once per frame
19.     void Update()
20.     {
21.         if(Input.GetKeyDown(KeyCode.Escape))
22.         {
23.             if(isPaused)
24.             {
25.                 ResumeGame();
26.             }
27.             else
28.             {
29.                 PauseGame();
30.             }
31.         }
32.     }
33.  
34.     public void PauseGame()
35.     {
36.         pauseMenu.SetActive(true);
37.         Time.timeScale = 0f;
38.         isPaused = true;
39.     }
40.  
41.     public void ResumeGame()
42.     {
43.         pauseMenu.SetActive(false);
44.         Time.timeScale = 1f;
45.         isPaused = false;
46.     }
47.  
48.     public void GoToMainMenu()
49.     {
50.         Time.timescale = 1f;
51.         SceneManager.LoadScene("MainMenu");
52.     }
53. }
54.  

please help its putting my game on hold

 

Any time you see

; expected

, means you forgot to put one in. check your line 50

 

What code editor are you using, for one...? There's been a lot of people posting simple errors, that the code editor should be showing you right away with the red line stuff.

I would suggest Visual Studio, as it quickly shows me simple errors like that, and also won't even let me hit play, and constantly shows errors within Unity's console. I'm just confused on how you got that far, to actually do a play test.

 

You're just making typos. Here's how to fix your typos:

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.

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! See above.

 

im using visual studio on mac

 

how much more can it do than tell you the line number and the character position?

 

I've got a new error now
Assets/scripts/PauseMenu.cs(47,12): error CS1520: Method must have a return type

 

Fixed it now i have Assets/scripts/PauseMenu.cs(49,14): error CS0117: 'Time' does not contain a definition for 'timescale'

 

What's the difference between line 44 and line 50?

 

the key issue is lack of attention to detail here.. and so far every error has been spot on accurate

 

https://docs.unity3d.com/ScriptReference/Time-timeScale.html

 

Just to make it crystal clear: C# is a case sensitive language. So the casing of words matters.

timescale

and

timeScale

are NOT the same things. For the compiler they are just as different as "Apple" and "Orange". There is no such thing as 90% correct code. The compiler does not guess what you may wanted to do. You tell him what you want he does it. If you're not precise he will complain.