XTool 2020 (Plugins)

[infovs]

Originally Posted by Cesar82

If someone can explain the differences between the 4 types of use of {:options} with arc.exe please share the information.
Thanks!

{option} in arc.ini will pass parameters as is, {options} will add - (minus) sign to parameters..so if your command line contains, for example,
arc create -mxtool+srep:m3f+lolz
you are in fact passing srep -m3f
Sad is that this is not explained anywhere, had to test it on my own to figure it out.
So your arc.ini should probably should contain
-mzlib+ue4:{option}
but in command line it should be (without quotes!)
-mxtool_ue4:m1:k0x115EE4......

With all that said, I'm not sure if your command line will work (can't test it) because this + sign in xtool combining codecs syntax is conflicting with arc syntax of combining codecs so there is a chance it can fail because of that. Change to, for example, & sign with ResourceEditor and try it with that if it fails.

Also, not sure if 0x is needed or optional before key, would like to know preferred way - with or without 0x , Razor12911?

[Cesar82]

Originally Posted by infovs

{option} win arc.ini will pass parameters as is, {options} will add - (minus) sign to parameters..so if your command line contains, for example,
arc create -mxtool+srep:m3f+lolz
you are in fact passing srep -m3f
Sad is that this is not explained anywhere, had to test it on my own to figure it out.
So your arc.ini should probably should contain
-mzlib+ue4:{option}
but in command line it should be (without quotes!)
-mxtool_ue4:m1:k0x115EE4......

With all that said, I'm not sure if your command line will work (can't test it) because this + sign in xtool combining codecs syntax is conflicting with arc syntax of combining codecs so there is a chance it can fail because of that. Change to, for example, & sign with ResourceEditor and try it with that if it fails.

Also, not sure if 0x is needed or optional before key, would like to know preferred way - with or without 0x , Razor12911?

as I already mentioned above if using ":" before "{option}" does not work (-mzlib+ue4:{option}). It only works if you use {: option}.
I will not pass the "+" character on the command line as parrametter.
The 0x character is optional for the ureal plugin, but for the uedt tool I think it is necessary to use 0x. As DiskSpan_GUI uses the same code for both (unreal plugin and uedt) so I always decided to enter 0x on the command line.
With quotes in the method it works perfectly, in the input directory -dp"directory" it is necessary to remove "" from the end if it is in quotes.

[infovs]

Originally Posted by Cesar82

as I already mentioned above if using ":" before "{option}" does not work (-mzlib+ue4:{option}). It only works if you use {: option}.
I will not pass the "+" character on the command line as parrametter.
The 0x character is optional for the ureal plugin, but for the uedt tool I think it is necessary to use 0x. As DiskSpan_GUI uses the same code for both (unreal plugin and uedt) so I always decided to enter 0x on the command line.
With quotes in the method it works perfectly, in the input directory -dp"directory" it is necessary to remove "" from the end if it is in quotes.

As I mentioned - I was not testing this, just saying..depending on program sometimes {:option} is needed, sometimes :{option} will work.
As for quotes, I meant "no quotes for -m parameter". Of course you need quotes with -dp etc. So your command line should be

arc.exe a -ep1 -r -ed -s; -w.\temp -mxtool_ue4:m1:k115EE4F8C625C792F37A503308048E79726E512F0BF8D2AD7C4C87BC5947CBA7 data1.arc "pack\*"

Yes, it is possible it works with " after -m but I think it is not preferred syntax.
And arc.ini probably should be (or maybe :{option} or {option})

[External compressor:xtool_ue4]
header    = 0
packcmd   = xtool.exe precomp -mzlib+ue4{:option} -d1 -c128mb -t100p --dbase - - <stdin> <stdout>
unpackcmd = xtool.exe decode -t100p - - <stdin> <stdout>

Syntax is correct, if it is not working it is because of how xtool/arc handles + sign in arc.ini so unless you change combining codecs sign with ResourceEditor it will never work correctly.