Tips

Just some tips on tools and stuff.

Building the ROM

To make the ROM file, you will need a c-compiler, python3, as well as other build-tools. The easiest way to set this up is using the guide from the decompilation project. Please follow those instructions, including installing the whole decompilation project. Then download this project using git clone https://github.com/krkpdf/pokemon-emerald-latin.

My project looks like this: Project Folder |_ pokemon-master-translated (renamed pokeemerald folder) |_ text-translated (renamed pokemon-emerald-latin folder)

You can change the folders around and their names, but then you will have to change the scripts too.

To quickly open WSL1 up in the Windows mount (/mnt/c), run the command wsl. From there change directories (cd) into the project directory and run ./make.sh.

Syntax

Only lines in the form [line number]: "..." ... are considered, so you are free to write comments however you want. Also, only the part in the quotations is copied, so you can also write whatever after the quotations, even before, but then they are not counted by the calc_progress script. As long as you have the line number and a part in quotation, all is good (I think). The line numbers refer to the original line number from the decompilation. As of right now, text has to have the exact same amount of lines as the original, so be careful about that.

Editor

I use Obsidian (https://obsidian.md/) for organizing and finding the stuff. I can just open the progress.md file and jump to wherever really quickly. As for plugins, I am using Advanced Tables, Hover Editor (absolutely amazing), and Unitade (for reading txt and json files). I also made this style sheet to make the progress.md file a lot more legible and for adding guidelines to the text files.

.markdown-source-view.mod-cm6 .cm-contentContainer::before {
	content: "";
  	position: fixed;
  	top: 0;
  	bottom: 0;
  	left: 489px; /* Adjust as needed */
	width: 30px;
  	border-left: 1px dashed gray; /* Change color and width as desired */
  	border-right: 1px dotted gray; /* Change color and width as desired */
}


/* remove formatting and set font to single size monospace */
.markdown-source-view:not(.is-live-preview) * {
	background: unset !important;
	color: unset !important;
	font-size: 1rem !important;
	font-weight: unset !important;
	font-family: monospace !important;
}

/* in case themes uses ::after div formatting for borders and so on */
.markdown-source-view:not(.is-live-preview) *::after {
	border: unset !important;
}



h1, .markdown-rendered h1,
h2, .markdown-rendered h2,
h3, .markdown-rendered h3,
h4, .markdown-rendered h4,
h5, .markdown-rendered h5,
h6, .markdown-rendered h6 {
	margin-top: 10px;
	margin-bottom: 0px;	
}


.markdown-rendered ul, .markdown-rendered ol,
p, .markdown-rendered p {
	margin-block-start: 0px;
	margin-block-end: 10px;

	margin-top: 0px;
	margin-bottom: 10px;
}


.h_1, .h_2, .h_3, .h_4, .h_5, .h_6 {
   	margin-left: 35px;	
	margin-bottom: 20px;
	# border-left: 1px solid gray;
}

CMD

The command findstr /s /i /c:"[text to be searched]" *.* is incredibly useful for finding where in-game text comes from.

/m ........... Prints only the file name if a file contains a match.
/s ........... Searches the current directory and all subdirectories.
/i ........... Ignores the case of the characters when searching for the string.
/c:<string> .. Uses the specified text as a literal search string.