In general you need to study the existing code, learn from it and do some work to get it to work on the new version. How much work will large depends on what type of cheat and how much has changed. Normally it is significantly easier than starting from scratch and especially so if you still have the original version of the game where the code is working to see it in action.
Read this document to learn about how to read code.
https://github.com/Atmosphere-NX/Atmosphere/blob/master/docs/features/cheats.md
If the code look like the following code (memory pointer with a fairly long chain) there is a good chance you can use the rebase feature of EdiZon SE to help find the new code. (This is the only kind that you can update the code with no knowledge of how to find the code yourself. Other code you need the ability to find code to update it.) Take a look at this post.
https://gbatemp.net/threads/se-tool...ing-needs-in-one-package.575131/#post-9227741
580F0000 0312DBD8
580F1000 000000B8
580F1000 00000000
580F1000 00000060
580F1000 00000110
580F1000 00000028
780F0000 00000124
640F0000 00000000 000003EB
For the following old code:
[Inf Health]
580F0000 061DF318
580F1000 000000B8
580F1000 000001E8
780F0000 00000018
680F0000 43C80000 43C80000
[Inf Hunger Gauge]
580F0000 061DF318
580F1000 000000B8
580F1000 00000280
780F0000 00000018
640F0000 00000000 451C4000
[Inf Thirst Gauge]
580F0000 061DF318
580F1000 000000B8
580F1000 00000438
780F0000 0000001C
640F0000 00000000 00000000
[Inf Fatigue Gauge]
580F0000 061DF318
580F1000 000000B8
580F1000 00000238
780F0000 00000088
640F0000 00000000 00000000
[Inf Cold Gauge]
580F0000 061DF318
580F1000 000000B8
580F1000 00000258
780F0000 00000020
640F0000 00000000 00000000
If you follow the process you will get the following code. You have to test the code to see if it works. All except Thirst look OK. That is the limit of the method. To fix Thirst you have to work it the normal way.
The first step is to find one value. Hunger is the obvious choice as they give you the number. There is one consideration. They don't show you all the decimal points. So you have to use range search. Once you find it you can rebase the code as I described in the other post.
In this example the old code saves you the effort of looking for Health, Fatigue and Cold. Having these also provide a good clue on how to look for Thirst. Thirst start from 0 and 100 is max. Now looking at the graphic provide information on what range to search for. After finding the value use pointer searcher to find the pointer. No narrow down is needed as the old code give good clue which one is the correct one.
The Long Dark
TID: 01007A700A87C000
BID: 2395934D93A4BF44
[Inf Health]
580F0000 06283398
580F1000 000000B8
580F1000 000001E8
780F0000 00000018
680F0000 43C80000 43C80000
[Inf Hunger Gauge]
580F0000 06283398
580F1000 000000B8
580F1000 00000280
780F0000 00000018
640F0000 00000000 451C4000
[Inf Thirst Gauge but this one look like broken]
580F0000 06283398
580F1000 000000B8
580F1000 00000438
780F0000 0000001C
640F0000 00000000 00000000
[Inf Thirst Gauge found the old fashion way]
580F0000 06283398
580F1000 000000B8
580F1000 00000450
780F0000 0000001C
640F0000 00000000 00000000
[Inf Fatigue Gauge]
580F0000 06283398
580F1000 000000B8
580F1000 00000238
780F0000 00000088
640F0000 00000000 00000000
[Inf Cold Gauge]
580F0000 06283398
580F1000 000000B8
580F1000 00000258
780F0000 00000020
640F0000 00000000 00000000