Thread: Change scoring system Tetris

GDB Documentation

Basically, run the code in the debugger (don't forget to compile with the -g flag).
If you believe score_function is involved, then set a breakpoint (b score_function) to test your idea.

You might want to look at where score_function is called from, which should be the code which locates a completed row.

The debugger is advantageous since
- you don't need to edit the code to observe behaviour
- you can examine all the program data
- you can examine the call stack to figure out where things are called from
- you can change data on the fly to test ideas about how things might work differently.

Or you can go for the crude approach of sprinkling debug prints through the code.

Code:

static void score_function (engine_t *engine)
{
   printf("DEBUG: score_function called\n");
   /// rest of code
}

> I try to learn some coding.
...
> Can you just write it for me, please

You can't learn how to cook from just reading the menus at a restaurant.

> But I am totally new to coding, so I have no idea how to work with the debugger.
Fine, don't use a debugger. Just spread some print statements around and see what happens.

To be honest, if you're that new to coding, you need to hone your skills on much smaller programs.

I've told you all you need to know to start answering your own questions.

You make a prediction, you make a test printf() to test your analysis and you observe the results.

If your result matches your expectation, you move on.
If it doesn't, you try again.