Neo-Mind
Community Contributors
- Messages
- 713
- Points
- 0
- Location
- The Mysterious Subcontinent
- Discord
- _Neo_ #7539
- Github
- Neo-Mind
- Emulator
UPDATE:
The CORE (Client Object & Related Entities) part have been shifted to CORE.dll and NEMO has been updated to 2.5 (along with some patch fixes of-course)
NEMO now supports CLI & GUI modes (Credits to nanakiwurtz for the CLI idea).
To use as GUI:
Just start without any arguments like before - There is a 1-2 second flashing console when opening (care of Windows
), but you can ignore that.
You might notice Test Patches button is missing now. This is because its going to be implemented as a seperate companion tool alongside NEMO
(which will use CORE.dll as well) later on.
To use as CLI (Console):
All debug and error statements will be reported to the console it is run from
NEMO.exe -inputs <input value list file> -patches <patch list file> -inclient <input exe file> -outclient <output exe file>
[*]The <input value list file> is a csv file with the variables used in Patches assigned to values you want.
For ease of use I have created InputsListTemplate.txt file in Input folder which contains all currently used variables commented out.
You just need to change the values you want and uncomment the line
[*]The <patch list file> follows the format of the .log file that is used in profiles & what is saved in PatchList.log when patch is applied in GUI mode.
Essentially what is needed is a list of Patch IDs - one per each line (refer _patchlist.qs inside Patches folder to see the IDs).
[*]The <output exe file> is optional. If not provided the <input exe file> suffixed with _patched.exe and used.
Let me know if there is any confusion or suggestions.
I am also thinking of merging the two list files in Profiles as well as for the Console in future. Any thoughts?
The CORE (Client Object & Related Entities) part have been shifted to CORE.dll and NEMO has been updated to 2.5 (along with some patch fixes of-course)
NEMO now supports CLI & GUI modes (Credits to nanakiwurtz for the CLI idea).
To use as GUI:
Just start without any arguments like before - There is a 1-2 second flashing console when opening (care of Windows
You might notice Test Patches button is missing now. This is because its going to be implemented as a seperate companion tool alongside NEMO
(which will use CORE.dll as well) later on.
To use as CLI (Console):
All debug and error statements will be reported to the console it is run from
NEMO.exe -inputs <input value list file> -patches <patch list file> -inclient <input exe file> -outclient <output exe file>
[*]The <input value list file> is a csv file with the variables used in Patches assigned to values you want.
For ease of use I have created InputsListTemplate.txt file in Input folder which contains all currently used variables commented out.
You just need to change the values you want and uncomment the line
[*]The <patch list file> follows the format of the .log file that is used in profiles & what is saved in PatchList.log when patch is applied in GUI mode.
Essentially what is needed is a list of Patch IDs - one per each line (refer _patchlist.qs inside Patches folder to see the IDs).
[*]The <output exe file> is optional. If not provided the <input exe file> suffixed with _patched.exe and used.
Let me know if there is any confusion or suggestions.
I am also thinking of merging the two list files in Profiles as well as for the Console in future. Any thoughts?
Last edited by a moderator: