Post by eternity on Jan 15, 2016 19:23:48 GMT
Download version 2.32: here.
Requeriments of SS Mods Installer:
- Windows Vista or higher. (or a system that emulates it/virtualize it). This is actually a requeriment of sssspatcher, which cannot currently work properly in Windows XP due to the use of a convenient api function that was introduced in Vista. If there is really demand for it, I may give support to XP, but at the moment it is like that.
- An original version of the game that is updated (last version was released around 7 December, more or less).
Now, let me clarify this point for a moment, in concrete, the "original" part. The versions "that are forbidden to talk on the site" (don't talk about that) may make use of hacks and patches that interfere with the ones of sssspatcher. In concrete, things related with false steam_api.dll or with injectors, could interfere with sssspatcher and make it crash at any point.
What you do in your home is up to you, but if you use one of these versions, don't report bugs, specially crashes, because the bug reports won't be valid, as it wouldn't be possible to distinguish crashes that happen due to my mistakes or due to that incompatibility.
And now that that point is clarified, don't bring this topic into the thread again.
Recommendations:
- It is only a recommendation, not a requirement. But it would probably be a good idea to revert to your original resource.cpk. You could always still install your existing replacer mods in the resource folder next to SSSS.exe (if that folder doesn't exist, it will be created by SS Mods Installer).
Usage:
The first time you run SS Mods Installer, it will auto install the last version of sssspatcher, (which is bundled inside the .exe). If you had the now obsolete old version of sssspatcher (the one that is in its own thread), it will auto update it.
In most cases, the program will be able to do that automatically, but if it cannot, it will prompt you to locate the SSSS.exe file of the game.
Installing and uninstalling mods is pretty straight forward. To install, just select File->Install, and open a file with .ssz extension. To uninstall, right click on the mod in the list, and select Uninstall.
Update process is similar to install, the only difference is that you won't be prompted to select the character slot, because it will be assumed that it will remain the same (if you want to change the slot of an installed mod, you'll have to uninstall it, and install it again).
If what you want is to create a .ssz file from a replacer mod, that has its own tutorial here.
Considerations:
SS Mods installer is not compatible with sscharactertool2 or the old .cms hacks. And in fact, the cms_model_spec.cms file will be wiped out by sssspatcher.
Modders can include directly any specific value (like aura, cosmo, or the other entries of ModelSpec) directly in their mods. But if the user wants to change the aura/cosmo of vanilla character because they still use replacer mods or whatever reasons, or even change the aura/cosmo of new character mods because they didn't like what the author chose, there is a new guide, that is almost identical to the previous one.
You may notice that the directory where SSSS.exe is, has a lot of .xml files once you run SS Mods Installer. These xml are used by both, SS Mods Installer and sssspatcher. SS Mods Installer write changes to these files. And then sssspatcher (the "invisible code tha runs along the game"), compiles these files to binary format, and save them in resource folder (except for the .slf.xml which goes directly in ram), it does that automatically when you run the game.
Let me give you a warning about editing these .xml files by hand. If you edit things like AURA and COSMO, like in the previous guide, you will be fine (if you use valid values, that's it). But don't ever try to do things like this:
- Adding your own entries to any of the files.
- Changing anything that has the words "id" or "idx" in its name.
- Changing anything in the .slf.xml file. Stay out of that file, it is not for humans beings
- Don't copy your old .cms.xml (the one generated by sscharactertool2) there.
- Don't do backups of these files and then expect them to work when restoring them, because SS Mods Installer would be left at inconsistent state. (at any rate you would need to also backup the SS Mods Installer configuration files, which are in AppData/Roaming/SSMINS)
Not following these advices can and will likely lead to one or more of the following:
- sssspatcher crash
- Game crash
- SS Mods Installer crash
- SS Mods Installer unable to install new mods or to uninstall existing one (e.g. left in an incosistent state)
- Game unpredictable behaviour (which may include random crashes).
All these .xml files work all together and they are more complex that what you may really think, specially, the .slf.xml file. A small mistake in one, and the rest will be affected too. At any rate, if you don't follow these advices, don't report any bugs.
Emergency maneuvers:
If for whatever reason, SS Mods Installer/sssspatcher is in an "incosistent state", either because you violated the warnings in the consideration section or because of a bug in the program, follow this procedure to wipe all of the mods at once.
Delete one of the .xml files that is in the folder where SSSS.exe is. Deleting one is enough (any one).
Go to this folder: c:\Users\<YOUR USER NAME>\AppData\Roaming. You will find a folder called SSMINS. Delete it.
(tip: this folder can be easier located by putting "%APPDATA%" in the search box of the start menu)
Next time you run SS Mods Installer, all xml files will be re-generated as in vanilla state, and you will see no mods. The files of your mod are still there in resource folder, though, but there is nothing that uses them, so it shouldn't be a problem (this is unless the mod author did something he shouldn't, like replacing a vanilla file, but that's anoother topic... for those cases I would wipe the resource folder too)
If you want to also remove sssspatcher, to fully leave the game at vanilla state, delete the file steam_api.dll, and after that, rename the .dll steam_api_real.dll as steam_api.dll.
-----
Known issues:
This is a list of the known issues so far.
- There are no options for characters to have their own avatar. This is not an issue, but a feature not implemented yet. It is planned to be implemented.
- When you install a character in a slot of a character that has different BBA, there is a small display issue when switching between characters (bba name is not refreshed). Selecting the character or moving out and in the slot again fixes the issue.
- In the galaxian wars, a new character will appear with the Seiya first armor banner image. And when a new character wins the galaxian wars, Saori won't say her line. This is the result of some pre-baked data not patched. It will be addressed in a future version.
- New characters don't work in online. Well, I haven't even tested, but I don't even need to. It is not technically possible for other client to recognize the new characters you have installed. You may give a try with someone that installed mods in EXACTLY same order (same resource folder, same xml, and same ssmins config), but there may be server reject code too. As I said, it is not technically possible to fix this.
-----
(TODO: add section about sssspatcher.ini file)
Requeriments of SS Mods Installer:
- Windows Vista or higher. (or a system that emulates it/virtualize it). This is actually a requeriment of sssspatcher, which cannot currently work properly in Windows XP due to the use of a convenient api function that was introduced in Vista. If there is really demand for it, I may give support to XP, but at the moment it is like that.
- An original version of the game that is updated (last version was released around 7 December, more or less).
Now, let me clarify this point for a moment, in concrete, the "original" part. The versions "that are forbidden to talk on the site" (don't talk about that) may make use of hacks and patches that interfere with the ones of sssspatcher. In concrete, things related with false steam_api.dll or with injectors, could interfere with sssspatcher and make it crash at any point.
What you do in your home is up to you, but if you use one of these versions, don't report bugs, specially crashes, because the bug reports won't be valid, as it wouldn't be possible to distinguish crashes that happen due to my mistakes or due to that incompatibility.
And now that that point is clarified, don't bring this topic into the thread again.
Recommendations:
- It is only a recommendation, not a requirement. But it would probably be a good idea to revert to your original resource.cpk. You could always still install your existing replacer mods in the resource folder next to SSSS.exe (if that folder doesn't exist, it will be created by SS Mods Installer).
Usage:
The first time you run SS Mods Installer, it will auto install the last version of sssspatcher, (which is bundled inside the .exe). If you had the now obsolete old version of sssspatcher (the one that is in its own thread), it will auto update it.
In most cases, the program will be able to do that automatically, but if it cannot, it will prompt you to locate the SSSS.exe file of the game.
Installing and uninstalling mods is pretty straight forward. To install, just select File->Install, and open a file with .ssz extension. To uninstall, right click on the mod in the list, and select Uninstall.
Update process is similar to install, the only difference is that you won't be prompted to select the character slot, because it will be assumed that it will remain the same (if you want to change the slot of an installed mod, you'll have to uninstall it, and install it again).
If what you want is to create a .ssz file from a replacer mod, that has its own tutorial here.
Considerations:
SS Mods installer is not compatible with sscharactertool2 or the old .cms hacks. And in fact, the cms_model_spec.cms file will be wiped out by sssspatcher.
Modders can include directly any specific value (like aura, cosmo, or the other entries of ModelSpec) directly in their mods. But if the user wants to change the aura/cosmo of vanilla character because they still use replacer mods or whatever reasons, or even change the aura/cosmo of new character mods because they didn't like what the author chose, there is a new guide, that is almost identical to the previous one.
You may notice that the directory where SSSS.exe is, has a lot of .xml files once you run SS Mods Installer. These xml are used by both, SS Mods Installer and sssspatcher. SS Mods Installer write changes to these files. And then sssspatcher (the "invisible code tha runs along the game"), compiles these files to binary format, and save them in resource folder (except for the .slf.xml which goes directly in ram), it does that automatically when you run the game.
Let me give you a warning about editing these .xml files by hand. If you edit things like AURA and COSMO, like in the previous guide, you will be fine (if you use valid values, that's it). But don't ever try to do things like this:
- Adding your own entries to any of the files.
- Changing anything that has the words "id" or "idx" in its name.
- Changing anything in the .slf.xml file. Stay out of that file, it is not for humans beings
- Don't copy your old .cms.xml (the one generated by sscharactertool2) there.
- Don't do backups of these files and then expect them to work when restoring them, because SS Mods Installer would be left at inconsistent state. (at any rate you would need to also backup the SS Mods Installer configuration files, which are in AppData/Roaming/SSMINS)
Not following these advices can and will likely lead to one or more of the following:
- sssspatcher crash
- Game crash
- SS Mods Installer crash
- SS Mods Installer unable to install new mods or to uninstall existing one (e.g. left in an incosistent state)
- Game unpredictable behaviour (which may include random crashes).
All these .xml files work all together and they are more complex that what you may really think, specially, the .slf.xml file. A small mistake in one, and the rest will be affected too. At any rate, if you don't follow these advices, don't report any bugs.
Emergency maneuvers:
If for whatever reason, SS Mods Installer/sssspatcher is in an "incosistent state", either because you violated the warnings in the consideration section or because of a bug in the program, follow this procedure to wipe all of the mods at once.
Delete one of the .xml files that is in the folder where SSSS.exe is. Deleting one is enough (any one).
Go to this folder: c:\Users\<YOUR USER NAME>\AppData\Roaming. You will find a folder called SSMINS. Delete it.
(tip: this folder can be easier located by putting "%APPDATA%" in the search box of the start menu)
Next time you run SS Mods Installer, all xml files will be re-generated as in vanilla state, and you will see no mods. The files of your mod are still there in resource folder, though, but there is nothing that uses them, so it shouldn't be a problem (this is unless the mod author did something he shouldn't, like replacing a vanilla file, but that's anoother topic... for those cases I would wipe the resource folder too)
If you want to also remove sssspatcher, to fully leave the game at vanilla state, delete the file steam_api.dll, and after that, rename the .dll steam_api_real.dll as steam_api.dll.
-----
Known issues:
This is a list of the known issues so far.
- There are no options for characters to have their own avatar. This is not an issue, but a feature not implemented yet. It is planned to be implemented.
- When you install a character in a slot of a character that has different BBA, there is a small display issue when switching between characters (bba name is not refreshed). Selecting the character or moving out and in the slot again fixes the issue.
- In the galaxian wars, a new character will appear with the Seiya first armor banner image. And when a new character wins the galaxian wars, Saori won't say her line. This is the result of some pre-baked data not patched. It will be addressed in a future version.
- New characters don't work in online. Well, I haven't even tested, but I don't even need to. It is not technically possible for other client to recognize the new characters you have installed. You may give a try with someone that installed mods in EXACTLY same order (same resource folder, same xml, and same ssmins config), but there may be server reject code too. As I said, it is not technically possible to fix this.
-----
(TODO: add section about sssspatcher.ini file)
