That's not a bug of the installer,it is you for getting to get the proper vcf path in modelspec.

Or alternatively, since you have used everything else from SYN, use:

<VCF value="../SYN/BT_SYN_VC.amk" />

I made a shun xml workout clothes in bronze armor v1 so that current does not appear too chains off 



<?xml version="1.0" encoding="utf-8"?>

<SSZ>

<SSZ_FORMAT_VERSION value="1.1" />

<MOD_NAME value="Shun Training Clothes Two Chains" />

<MOD_AUTHOR value="Miha8934" />

<MOD_VERSION value="1.1" />

<MOD_GUID value="3490e0f6-dc25-4060-b600-45370b3c25d5" />



<CMS_ENTRY value="SYN" />



<ModelSpec>

<!-- SYN / Andromeda Shun [Shun Training Clothes Two Chains]-->

<BBA0 value="BBA_SYN00" />

<BBA1 value="BBA_SYN01" />

<BBA2 value="BBA_SYN02" />

<BBA3 value="BBA_SYN03" />

<BBA4 value="NULL" />

<BBA5 value="NULL" />

<EMA value="SYN.ema" />

<MENU value="SYN.menu.ema" />

<FCE value="SYN.fce.ema" />

<MATBAS value="SYN.matbas.ema" />

<FMA value="SYN.fma" />

<FDM value="SYN.fdm" />

<FCM value="SYN.fcm" />

<VFX value="VfxSYNEfct.emb" />

<TDB value="TdbSYN.tdb" />

<BPM value="msg_SYN.bpm" />

<VCN value="BT_SYN_VC" />

<SE value="BT_SYN_SE" />

<VCF value="../SYN/BT_SYN_VC.amk" />

<U_D0 value="0x1" />

<U_D4 value="0x1" />

<SCALE value="0.949999988" />

<COSMO value="0x3" />

<F_E0 value="1.0" />

<F_E4 value="0.600000024" />

<F_E8 value="1.0" />

<F_EC value="0.400000006" />

<F_F0 value="3.0" />

<AURA value="0x4" />

</ModelSpec>



<ModelEntry>

<!-- SYN / Andromeda Shun [Shun Training Clothes Two Chains]-->

<CHAR_ID value="0xb" />

<NAME_ID value="0xde" />

<SHORT_NAME_ID value="0x4e" />

<SIGN_NAME_ID value="0x4d" />

<ROBES_NAME_ID value="0x131" />

<ROBES_TYPE value="0" />

</ModelEntry>



<ModelPosEntry>

<!-- SYN / Andromeda Shun [Shun Training Clothes Two Chains]-->

<F_08 value="-0.879999995" />

<F_0C value="-1.09000003" />

<F_10 value="4.0" />

<U_14 value="0x0" />

<F_18 value="0.800000012" />

<F_1C value="-1.09000003" />

<F_20 value="4.0" />

<U_24 value="0x0" />

<U_28 value="0x0" />

<U_2C value="0x40" />

<U_30 value="0x3e" />

<U_34 value="0x3f" />

<U_38 value="0xffffffff" />

<U_3C value="0xffffffff" />

</ModelPosEntry>



<ModelRpdEntry>

<!-- SYN / Andromeda Shun [Shun Training Clothes Two Chains]-->

<NAME value="SYN_00" />

<U_04 value="0x1f" />

<F_08 value="0.239999995" />

<U_0C value="0x0" />

<F_10 value="-0.800000012" />

<U_14 value="0x0" />

<F_18 value="0.0" />

<F_1C value="1.20000005" />

<U_20 value="0xc0000000" />

<U_24 value="0x0" />

<F_28 value="1.20000005" />

<U_2C value="0x0" />

<F_30 value="50.0" />

<U_34 value="0x41" />

<U_38 value="0xab" />

<U_3C value="0x43" />

<U_40 value="0xad" />

<U_44 value="0x45" />

<U_48 value="0xaf" />

<U_4C value="0x46" />

<U_50 value="0xb0" />

<U_54 value="0x47" />

<U_58 value="0xb1" />

<U_5C value="0xffffffff" />

</ModelRpdEntry>



<Slot>

<!-- SYN / Andromeda Shun [Shun Training Clothes Two Chains]-->

<ICON_DATA value="6.0" />

<U_0C value="0x0" />

<SIGN_NAME_ID value="0x50" />

<CIU_0C value="0x4" />

<ROBES_NAME_ID value="0x130" />

<CIU_14 value="0x3" />

<AVATAR_ID value="0x60" />

<CIU2_0C value="0x4" />

<CIU2_10 value="0x0" />

<CATEGORIES value="ANDROMEDA_SHUN, BRONZE_ARMOR" />

</Slot>

</SSZ>

I havent tested but I doubt it. That must be again som more pre baked data, plus it would need also some unlock function hack too since the default state of objects in the game is the locked state.

I think you cannot ask or it is ilegal to ask for original patches\updates if you havent got the original game in this forum.
Just google soldiers soul update 1 and maybe you'll find something.
Good luck, buena suerte tio

There is a limit of 10 character per slots, this is an internal limit in the game that is difficult to break due to the ugly code involved (I don't discard it to do in the future, but not for the moment).

Anyway, you can install the character in other slots. All character will work exactly the same on any slot. Slot themselves are just positions without information attached. You could install your Cygnus mods on Hades and they would work the same, and they would be recognized as Cygnus, the only issue is the BBA refresh thing while selecting the character.

This is the provisional list of features that will come in version 2.0:

- The program will come with an option in a menu to register the .ssz extension with it. After doing that, you will be able to install mods with just a double click on .ssz files.
Status: already implemented

- Modders will be able to customize the name of the characters used below the life bar (aka "battle name"). These are actually two different textures, one for left position, and another for right position.
Status: already implemented

- Modders will be able to customize the name used in the selection screen (there are actually two, one for the selection screen, and another in the list of the galaxian wars, both are textures).
Status: not started

- Modders will be able to specify the "icon". This image is actually used when selecting a character in the galaxian wars, and in the result of galaxian wars (this would actually used in the selection screen... but the game only uses the icon of the first character of the slot).
Status: partially implemented (implemented when selecting a character in the galaxian wars, but not in the result).

- Modders will be able to customize the "robes name" and "sign name". These are actually plain text, they will go in a new optional section of the .xml, called <Text>.
Status: already implemented.

- Modders will be able to customize the "galaxian wars banner" (image and text, the text is a texture too). Also, another name (texture) is used in the final result screen of galaxian wars, modders will be able to customize that one too.
Status: not started. The pre-baked data "CharacterInfo4" has yet to be found.

There is also another feature that is currently only in my mind, but it won't be listed here, because it may not actually make it in the final version.

----
It is worth to mention, that all new features of .ssz format will be optional, and independent from each other. You could use 0, any or all of them, that's modder choice.

As for things that have text (either in a texture or as plain text), modder will be able to put them in the 8 languages that the game supports, but that will be optional too: only the english one will be mandatory.
That will work like this: if the modder only includes a text-texture or plain text in english language, all other languages will use the one from english. If the modder includes textures/text for every language, each language will use its own texture/text. If the modder includes english + some other language(s), but not all of them, then, the included languages will use each one its own version, and the not included languages will use the english one.

The estimated time of arrival is somewhere between the end of next week and first half of the week after.

You also had to delete at least one of the .xml files in the SSSS folder. Deleting SSMINS folder is not enough. One you delete one of the .xml files, at next startup, SSMINS regenerates all of them, since they are all dependent of each other.
The xml files that you have to delete are the ones next to SSSS.exe, not the ones in doc folder of Mods Installer (those are provided for documentation only and are totally unused by the program!)

There are no differences in uninstallation process associated to a particular mod, the process is identical in all of them, and it takes a time proportional to the number of files the mod had (and not the size of the files of the mod, thus, lyra orphee is not a special case here).

I cannot reproduce your issue at all. Uninstalling Lyre Orphee works here.
You mean that it is the installer which crashes, not the game? The above mentioned of keeeping and old .xml file could explain something like that.
The SSMINS folder and the .xml files at SSSS must be synchronized. If you delete one, you must delete the other. If one changes, the other must change too.


Anyway, for the next version, I will make sure that if SSMINS is deleted, the xml files of SSSS are regenerated and viceversa, to avoid human errors. I will provide something to check consistency too. Anyway, in your case, I would try again to remove the xml and SSMINS folders. Both.

Well, those mods are working perfectly here, uninstallation too. Since the beginning you have been reported problems that no else had that have been associated to third party programs, which is why I cannot research this more further, as I cannot fully consider the bug reports as valid.

Only thing I can tell you is to retry the emergency maneuvers again to see if it happens. And if it happens, send me the xml and the SSMINS config folder, to see what happened, as what you describe sounds as if SS Mods Installer couldn't write to one of the xml files. The other possibility is that sssspatcher is not writing the binary compilation of the .xml files.

SS Mods Installer should have full write access to the directory where SSSS.exe is located, and to c:\Users\<UserName>\AppData\Roaming\SSMINS. If something blocks SS Mods Installer from writing to those directories, bad. If a rootkit (which includes antivirus programs) fools the installer into thinking that it wrote correctly to these files but it didn't: even worse.

sssspatcher (or SSSS.exe) should have full write access to the SSSS directory too.