First, read the Script Merger instruction page carefully and follow its instructions.

When Script Merger loads the files, they will be listed as shown in the image below.

On the left, conflicting mods are listed by file.
On the right, merged mods are listed by file.
If you do not merge, the file of the mod with the highest priority (the mod shown in darker color in the conflict list) will be loaded.
Select the files you want to merge and click the "Create Selected Merge" button.
Depending on the mod, the mod author may instruct you not to merge conflicts, so please check the instructions carefully before merging.
In particular, please be careful as you are often instructed not to merge "Non-Bandled XML" and "Bundled Text".

If manual merging is required, a window similar to the image below will pop up.

In the upper row, the conflict locations of three files, A, B, and C from the left, are displayed.
A is the vanilla file, B and C are conflicting mod files.
The code of the merged file is displayed at the bottom.
If you select "B" and/or "C" from the top toolbar, the code from the selected files will be added to the merged file. (In the image above, both B and C are selected in that order.)
Click the "Go to Next Unsolved Conflict" button to the left of "A" on the toolbar to display the next conflict location.
Once all conflicts have been merged, close the window and save.


How to Choose B or C
It is better to select both B and C to enable all mod functions.
However, if two mods change the exact same part, you will have to choose one.
When doing so, be careful not to break the format of the code. Even if you don't have any coding knowledge, you should be able to see that the code is written according to some rules. Don't break it.

Look at the C code in the image above.
The parts in red are different from vanilla, the parts in yellow are conflicting parts, and the parts in gray are already included in the merged file.
The part between {} is a code block, and the block title is written at the top or left side of the block.
If you do not select C at the end, the title that is supposed to be attached to the gray code block will be lost, so it will deviate from the mod's expectations.
Therefore, I chose the codes in the order of B and C.

If the code is broken no matter how you select it, you may be able to solve the problem by deleting some of the merged code or by copying the conflicting code with "Ctrl + C" and sticking it inside the merged code with "Ctrl + V".


List of Codes to Watch Out for:
{}:

• The part between {} is treated as one block.
  

event:
function:

• If the title of a code block between {} starts with "function" or "event", the block is treated as one section.
• When a section is loaded, the code is loaded in order from the top, and the section ends when "return" is loaded or all the code is loaded.
  

return:

• Finish that section. The code after the next ";" will not be loaded.
  

if():

• Only if the condition in parentheses is met will the code written next be loaded.
  

else:

• Used following an "if" statement. Code written next to "else" will only be loaded if the condition of the "if" statement is not met.
  

var:

• If a line of code within a section begins with "var", that code must be placed at the beginning of the section.
  

//:
/**/: 

• The part to the right of "//" or the part between "/*" and "*/" is commented out and will not be loaded into the game.