Hello There, Guest! Login Register


Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Tool] Wimoh's Holocron
#1
Rainbow 
About

This is a tool I began years ago while looking into SWG files, to learn both programming and SWG files architecture.


Features

You can edit, check and create tre/toc archives. This was meant to be much more but Sytner and Timbad are already on a good track with their tools so for good sake the features are frozen about the archives only and not the assets themselves and most probably will never be.

I did not have time to implement the command line interface though. If anyone is interested, please do tell. I may make a command line only build to make the overall program much smaller.

The tool is meant to be very accurate and fast. You can introduce virtually any error in an archive and it should be caught. I also took great care not to corrupt data if it crashes or if an error occur during an edition. It should be trivial extracting or packing hundreds of thousands of files.


 
Reply
#2
You forgot to add your Qt5Widgets.dll. Sad

Tried mine, didn't work then though.

So can you add files to tre's then? Or am I misunderstanding you?
 
Reply
#3
(2015-03-26, 11:22 PM)Timbab Wrote: You forgot to add your Qt5Widgets.dll. Sad

Tried mine, didn't work then though.

So can you add files to tre's then? Or am I misunderstanding you?

I updated with the missing dll.

You can add from files or from archives records (or the combination of two) to existing archives or create a new one and fill it.
 
Reply
#4
Working now.

How'd you get the beta compression algo?

Interesting tool though, bit confusing at first. :p

Hmm, seems to have a problem reading my custom .toc files (for my file history), it says Crc32 order is broken, it does work on SIE and TreE though. Also you have a typo in "Crc32 order is broken is file". It ends up showing files as Invalid and "Name size is incoherent".

Applies to custom tocs for v5 .tre's, too.
 
Reply
#5
(2015-03-27, 02:31 PM)Timbab Wrote: Working now.

How'd you get the beta compression algo?

Interesting tool though, bit confusing at first. :p

Hmm, seems to have a problem reading my custom .toc files (for my file history), it says Crc32 order is broken, it does work on SIE and TreE though. Also you have a typo in "Crc32 order is broken is file". It ends up showing files as Invalid and "Name size is incoherent".

Applies to custom tocs for v5 .tre's, too.

I reversed the beta compression algorithm myself, that was quite painful and interesting. In fact, I reversed it weeks before it was announced on this website by Uli I think. I have someone we both know who could say so but who cares.

If the tool report an error and the client can load your files, I will be interested to know every details. Otherwise the error reported is what is broken in your file. You may load broken files but the various warnings and errors will tell you what is preventing the archives to be loaded by the client.
 
Reply
#6
Oh, you did? Cause I remember digging hard at that time because it was mentioned to me and then after I found it and Uli wrote it, it seemed like a first for everyone. Regardless though, props of you cracking it, it sure wasn't straight forward. Smile

I'll try to do some checks on the tocs later if it can help ya out!
 
Reply
#7
(2015-03-27, 04:42 PM)Timbab Wrote: Oh, you did? Cause I remember digging hard at that time because it was mentioned to me and then after I found it and Uli wrote it, it seemed like a first for everyone. Regardless though, props of you cracking it, it sure wasn't straight forward. Smile

I'll try to do some checks on the tocs later if it can help ya out!

I was pretty amazed when you guys found out the algorithm too. I was sure nobody would find out so I kept it secret to release the tool with new fancy features.

What are you saying?
1) the tool has broken a toc file after a write operation and reports it when you load it again;
2) you put a toc file of yours in the tool, the tool reports the file broken and you can load the file into the client;
3) you put a toc file of yours in the tool, the tool reports the file broken and you can't load the into the client;
4) you put an official toc file in the tool, the tool reports the file broken and you can load the file into the client;
5) you put an official toc file in the tool, the tool reports the file broken and you can't load the file into the client;

Thanks for the feedback, don't hesitate to e-mail me your toc file and the log file associated with it if you think something is wrong.
 
Reply
#8
(2015-03-27, 06:32 PM)Wimoh-X Wrote:
(2015-03-27, 04:42 PM)Timbab Wrote: Oh, you did? Cause I remember digging hard at that time because it was mentioned to me and then after I found it and Uli wrote it, it seemed like a first for everyone. Regardless though, props of you cracking it, it sure wasn't straight forward. Smile

I'll try to do some checks on the tocs later if it can help ya out!

I was pretty amazed when you guys found out the algorithm too. I was sure nobody would find out so I kept it secret to release the tool with new fancy features.

Since its now known, do you want to say what the algorithm is from then let everyone know.
[Image: 2156b479.gif]
 
Reply
#9
(2015-03-27, 06:36 PM)Uli Wrote:
(2015-03-27, 06:32 PM)Wimoh-X Wrote:
(2015-03-27, 04:42 PM)Timbab Wrote: Oh, you did? Cause I remember digging hard at that time because it was mentioned to me and then after I found it and Uli wrote it, it seemed like a first for everyone. Regardless though, props of you cracking it, it sure wasn't straight forward. Smile

I'll try to do some checks on the tocs later if it can help ya out!

I was pretty amazed when you guys found out the algorithm too. I was sure nobody would find out so I kept it secret to release the tool with new fancy features.

Since its now known, do you want to say what the algorithm is from then let everyone know.

I reversed it. I have no idea how it is called. I did a lot of research once I had the algorithm but I was unable to identify it. I think it's simple enough to be home made and they moved later to deflate, probably for performance reasons.
 
Reply
#10
Updated to v1.0.1. Detailed patch notes included.

- Fixed the compatibility issue with other tools
- Added more info in actions tool-tips
 
Reply
  



Forum Jump:


Browsing: 1 Guest(s)