So I’m heavily involved with the Kaizo Ironmon community. I play mobile (for right now in bad life circumstances) and have gained a pretty good understanding of the files.
I’ve been doing some research; and it exists for Android but if I locked in to some stuff and learned more, how likely do you think it is that I could create an iOS Tracker? (Example pictured if you’re unfamiliar; reads the game file live).

I feel like it IS so possible. Likely with side loading, tho, which of course isn’t accessible for all but I so badly want to make this happen.

Here is the announcement by encounter: https://decomp.dev/

They name AI and the influx of its interactions with the decompilation scene as the primary reason for sunsetting it, listing the following in particular (direct quotes from the article):

• Forking existing decompilation projects to "finish" them with AI. Every project works differently: some may not want to use AI for legal or ethical reasons, and others may be okay with AI, or use AI themselves, but do not want drive-by contributions from folks who have put no effort into making sure the contributions are good. The bottom line is that these kinds of hostile forks put little to no effort into meaningfully contributing to existing projects, tearing apart our community fabric.
• Racing to port games, especially utilizing decompilations that they did not contribute to. Yes, now anyone with an AI subscription can manage to create a port or static recompilation that functions at a basic level. Compared to the decompilation process itself, porting is relatively easy, especially with the established tools written by talented humans. While community members put in the effort to decompile a game, opportunists have frequently raced to release a half-baked, barely-functional port from it.
• Conflating decompilation and ports. For years, decompilation communities attempted to establish that decompilation is primarily for research: we love these games and want to understand how they work, and to uncover the mysteries that the original developers left behind. That's not to say that ports aren't fun too; they're just not the sole reason a decompilation exists. Sloptubers and subreddits like r/decomps have done immense damage here, freely using "decomp" to mean "PC port".

As for the future of the site:

> decomp.dev will continue to track existing projects and serve individual project pages and historical data, but the main index and adding new projects are disabled.

Have you ever looked at your terminal while compiling and went "damn, I wish I could read this all properly", especially when you get a bunch of errors?

Well, no worries! There's a very easy way to do that. All you need to do is redirect the output with some simple commands.

The commands are thus:

make -j 1> log.txt
make -j 2> log.txt
make -j &> log.txt

Now, here's a small explainer for each part of the command.

make -j

I hope you already know what this command does.

1>, 2>, and &>

These are redirect commands. Put simply, they redirect the output of the command before it to the destination in it's right.

> is the actual symbol that redirects to the file, and what you put before it is what dictates what gets redirected.

1 refers to stdout, short for standard output. Anything from 1 will be any "normal" process the compiler spits out.

2 refers to the stderr, short for standard error. Anything from 2 will be any warning and the compiler spits out.

When you compile normally without any redirection commands, the output you see on the terminal is both the stdout and stderr. Hence, well, being called standard.

& normally means pushing a command in the background. For example, make -j & will mean nothing gets printed in the terminal until it's done. However, with the redirection command, what happens is both stdout and stderr both get redirected into log.txt

log.txt

This part of the command simply names which file you want the output being redirected to. If the file doesn't exist yet, it is created with then. Anything inside of it will also be overwritten with the output. You can put any filepath you wish here. For example, if you want the file to appear in your Desktop, you can put /mnt/c/Users/<name>/Desktop/log.txt, assuming you use WSL.

If you want to do this method, I also recommend adding log.txt to your .gitignore so you don't accidentally track the file.

That's all! Hope this helps <3