Feature Request im only new and im trying to do a chunk mesh but keep getting this error

Assets\Scripts\ChunkMeshCreator.cs(146,12): error CS1002: ; expected
heres my script

public Mesh CreateMeshFromData(int[,,] Data)
{
List<Vector3> Vertices = new List<Vector3>();
List<int> Indices = new List<int>();
Mesh m = new Mesh();

for(int x = 0; x < WorldGenerator.ChunkSize.x; x++)
{
for(int y = 0; y < WorldGenerator.ChunkSize.y; y++)
{
for (int z WorldGenerator.ChunkSize.z; z++)
{
Vector3Int BlockPos = new Vector3Int(x, y, z);
for(int i = 0; i < CheckDirections.Length; i++)
{
Vector3Int BlockToCheck = BlockPos + CheckDirections;

try
{
PLEASE HELP IVE BEEN STUCK FOR FIVE DAYS!!!!!

 

You really shouldn't be stuck on syntax errors for so long.

Post the whole script and use code tags next time please. You can edit your post if you want.

 

Wow seriously?! For a typo?! You need to seriously step up your typo fixing game my friend. This should be 20 seconds tops. You forgot an extremely obvious equal sign but because you didn't use code tags, I can't even tell you which line it's on! You did it right three times, but there are four places like this that need it.

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.

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.

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.

As long as you are monkey-hammer-banging other peoples code in from around the internet, keep this in mind:

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... go back to the top of this post!

 

Everything wrong with this post:

• Post has the tag "Feature Request" and is not a feature request, at all
• Post has a completely pointless poll attached
• Post contains code that is not inside a code block and therefore not formatted.
• The code snippet posted is just half of a method that is suddenly cut off
• The error message indicates a trivial typo. Even though the error contains the line number and column of the error, it's pointless when we have no reference. So we would need to search ourselfs manually for the error which the compiler can spot automatically.
• As others have already pointed out, it's very unlikely to be stuck for 5 days on a typo. When you have a compiler error, nothing will work, at all. So if you really are stuck at solving a typo for 5 days, you probably shouldn't become a programmer
• Finally, now on the 6th day we may put your attention to this line

  for (int z WorldGenerator.ChunkSize.z; z++)

  Maybe you notice something strange.