# Error cs 1513

**URL:** https://discussions.unity.com/t/error-cs-1513/1540331
**Category:** C# & .NET
**Tags:** 2022.3-lts, C-Sharp-Compiler, Question
**Created:** [October 21, 2024, 1:22pm UTC](https://discussions.unity.com/t/error-cs-1513/1540331 "2024-10-21T13:22:10Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![unity\_189C4271D404955AB31A](https://avatars.discourse-cdn.com/v4/letter/u/54ee81/32.png) [@unity\_189C4271D404955AB31A](https://discussions.unity.com/u/unity_189C4271D404955AB31A)
#### Post date: [October 21, 2024, 1:22pm UTC](https://discussions.unity.com/t/error-cs-1513/1540331/1 "2024-10-21T13:22:10Z")

</div>

![Screenshot 2024-10-21 181647](https://europe1.discourse-cdn.com/unity/original/4X/e/a/e/eae452b1a9eddda776674ae172a40a05dc1b57f9.png)  
help me to solve this error1513 in unity racing projects

---

<div class="post-metadata">

### Author: ![CodeSmile](https://dub1.discourse-cdn.com/unity/user_avatar/discussions.unity.com/codesmile/32/82968_2.png) [@CodeSmile](https://discussions.unity.com/u/CodeSmile)
#### Post date: [October 21, 2024, 1:46pm UTC](https://discussions.unity.com/t/error-cs-1513/1540331/2 "2024-10-21T13:46:29Z")

</div>

Read the error message. It tells you that the curly braces don’t match. Since this isn’t the case in the code you posted (please post code as text, not images) the problem is elsewhere in the script.

Also, the `pos` and `post` is likely a typo.

---

<div class="post-metadata">

### Author: ![Kurt-Dekker](https://dub1.discourse-cdn.com/unity/user_avatar/discussions.unity.com/kurt-dekker/32/101578_2.png) [@Kurt-Dekker](https://discussions.unity.com/u/Kurt-Dekker)
#### Post date: [October 21, 2024, 1:48pm UTC](https://discussions.unity.com/t/error-cs-1513/1540331/3 "2024-10-21T13:48:40Z")

</div>

> [@unity\_189C4271D404955AB31A](#):
>
> help me to solve

You can fix your own typing mistakes. 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? Are you structuring the syntax correctly? Look for examples!

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.