Quote:
|
Originally Posted by scrapser
Can you provide a list of all files that make up this tool? I saw the loglist file and one other but wonder what causes the "Error 76" message.
|
There are the loglist.txt and the Modconflict.txt.
JTxE work with ini-files which are located in the ini_Mods folder.
The ini files should contain a target line --> Targetfile=Data\Menu\menu_1024_768.ini
the chapter line --> [IMG]file:///C:/DOKUME%7E1/user/LOKALE%7E1/Temp/moz-screenshot.jpg[/IMG][G3F I248]
the targetline --> Zone=
and in the same line the new text --> 256 764 350 94 0 1 0x3F000000 0.365 0.025 0x3F2A0000 0 0 100 -900
behind this you could put a infotext --> ;1. Message Box position
the infotext should begin with a ; as remarkseparator ( SH4 does not take care of the text behind the separator)
putting remarks lines between the commands will not be writen from JTxE in the targetfile. Therefore i put the remaks behind the new text. This will also help to easy identify the new values in the targetfile.
How JTxE works:
JTxE searches first in the loglist.txt for duplicates of the chapter and targetline.
Getting a hit it informs you that the new mod conflicts with an older mod and ask for install permission, otherwise it install the new mod directly.
After installing, JTxE writes the modded lines in the loglist.txt with the name and date of the mod.
In case of a modconflict JTxE writes the conflict in the modconflict.txt.
The Modconflict.txt is shown in the JTxE window to show the user the conflicting mods. In case of SH4 Problems the user can see where the conflict occurs and can deinstall the conflicting mod.
the ini file in the ini_mods directory is backuped and replaced with the original values of the targetfile. It gets the ending .used. With this file JTxE knows the real values for a proper reinstalling of the Mod.
-- The first time JTxE changes a file it backups this file (menu_1024_768.ini.bak) This will helps to bring manually the original targetfile back.
I hope this helps to understand the logic behind JTxE.