Ok, before I start adding guides on how to add this or that I need to explain something that's simplifies all my modding and development. That being the way I handle my .tre files themselves...
First we know that SWGEMU as it is today uses some 53 different .tre files to load data into the Core3 server and well... work properly. Thing is, it doesn't HAVE to be 53 different .tre's. I think anyone who's done any server work at all gets tired of bouncing around from .tre to .tre looking for the latest version of a particular object or file. Since the .tre files are loaded in a specific order, it can be assumed that newer assets overwrite older assets. knowing this you can consolidate the .tre files into easier to work with files. All my development is based upon consolidated .tre files using this method:
first, pull up your swgemu_live.cfg file AND your core3 conf file. Both will show the proper order in which the client and core load the 53 different .tre files. I used the Core3 list.
1) in treexplorer open the first .tre file (should be bottom.tre). Select all the folders and choose export. For me I exported to a folder call alltres.
2) once the export is done, open up the next .tre file in the list.
a. select all the files / nodes, export to the same alltres directory, and if prompted overwrite.
b. rinse / repeat until you've added ALL the .tre files to your alltres directory, always overwriting.
3) so now you'll want to repack all this data in to one single .tre file right? well kind of. I'm not sure if it's a size limitation or what but the trepacker app won't pack more than about 2gb of data or 127K data items (those are the maxes I've run into). So you'll need to split your alltres directory in two, I made my split at the object folder, but use your best judgement to get the files as close to equal as possible both in size and item counts. Could take some trial and error.
4) Once you get your folders split, repack them into .tre files (will take awhile) and you're done. you should now have two .tre files that contain all the needed data using all the latest assets and info. This works perfectly with the core and client, although load times are increased on slower machines so be aware. Make backups of your swgemu_live.cfg and core3 conf, change each config file to use the two new .tre files and you're good to go.
5) swgemu_live example:
maxSearchPriority is always total number of files to load. searchTree_00_x= always begins with zero and counts up to the newest file.
[SharedFile]
maxSearchPriority=3
searchTree_00_2=mytre.tre
searchTree_00_1=alltre02.tre
searchTree_00_0=alltre01.tre
Now that you've gotten this far it's time for the next step which is optional if you're using the Core strait up with 14.1 with no new expansion content. However, if you want to use the Expansion content this is by far the easiest way to implement it:
1) First yo need to obtain the last sku0_data.TOC (clarify file name) that SOE released. I don't have the file handy ATM so I'll edit to clarify date/time stamps and such.
2) using the same procedure outlined above for my alltre's, Open the .toc file using treexplorer and export the entire contents to a folder, I used fulltoc.
3) once the export is complete you'll need to organize your fulltoc directory into useable chunks of data. So for instance the appearance folder alone contains more files than trepacker will work with so you need to divide it up. Same with some of the other data groups as well. I ended up needing to make 6 sub folders (fulltoc01-fulltoc06) in order to keep the data groups small enough for trepacker to work without stack overflows.
4) pack each of the sub folders into their own .tre file.
5) modify your swgemu_live.cfg & core3 conf files to load the new .tre files in addition to the 14.1 consolidated .tre files we made above, here is the order I use. BE AWARE THAT THE 14.1 ASSETS ARE WHAT THE CORE NEEDS, so you must set your order such that the 14.1 assets overwrite the TOC assets. Otherwise it's buggy central.
Here's my order:
[SharedFile]
maxSearchPriority=9
searchTree_00_8=mytre.tre
searchTree_00_7=alltre02.tre
searchTree_00_6=alltre01.tre
searchTree_00_5=fulltoc06.tre
searchTree_00_4=fulltoc05.tre
searchTree_00_3=fulltoc04.tre
searchTree_00_2=fulltoc03.tre
searchTree_00_1=fulltoc02.tre
searchTree_00_0=fulltoc01.tre
Use this load order for the core too.
Now, if you've managed to consolidate the assets as I have you can add objects at will, only adding what you need to change / modify to your own personal .tre file (mytre.tre in this example). If you don't need to modify an asset for it work properly, then there's no reason to include it in it's own .tre file. let it load it from the consolidated asset data.
And there you have it. Hopefully this helps some to understand how my other guides and mods work.
-Duff
First we know that SWGEMU as it is today uses some 53 different .tre files to load data into the Core3 server and well... work properly. Thing is, it doesn't HAVE to be 53 different .tre's. I think anyone who's done any server work at all gets tired of bouncing around from .tre to .tre looking for the latest version of a particular object or file. Since the .tre files are loaded in a specific order, it can be assumed that newer assets overwrite older assets. knowing this you can consolidate the .tre files into easier to work with files. All my development is based upon consolidated .tre files using this method:
first, pull up your swgemu_live.cfg file AND your core3 conf file. Both will show the proper order in which the client and core load the 53 different .tre files. I used the Core3 list.
1) in treexplorer open the first .tre file (should be bottom.tre). Select all the folders and choose export. For me I exported to a folder call alltres.
2) once the export is done, open up the next .tre file in the list.
a. select all the files / nodes, export to the same alltres directory, and if prompted overwrite.
b. rinse / repeat until you've added ALL the .tre files to your alltres directory, always overwriting.
3) so now you'll want to repack all this data in to one single .tre file right? well kind of. I'm not sure if it's a size limitation or what but the trepacker app won't pack more than about 2gb of data or 127K data items (those are the maxes I've run into). So you'll need to split your alltres directory in two, I made my split at the object folder, but use your best judgement to get the files as close to equal as possible both in size and item counts. Could take some trial and error.
4) Once you get your folders split, repack them into .tre files (will take awhile) and you're done. you should now have two .tre files that contain all the needed data using all the latest assets and info. This works perfectly with the core and client, although load times are increased on slower machines so be aware. Make backups of your swgemu_live.cfg and core3 conf, change each config file to use the two new .tre files and you're good to go.
5) swgemu_live example:
maxSearchPriority is always total number of files to load. searchTree_00_x= always begins with zero and counts up to the newest file.
[SharedFile]
maxSearchPriority=3
searchTree_00_2=mytre.tre
searchTree_00_1=alltre02.tre
searchTree_00_0=alltre01.tre
Now that you've gotten this far it's time for the next step which is optional if you're using the Core strait up with 14.1 with no new expansion content. However, if you want to use the Expansion content this is by far the easiest way to implement it:
1) First yo need to obtain the last sku0_data.TOC (clarify file name) that SOE released. I don't have the file handy ATM so I'll edit to clarify date/time stamps and such.
2) using the same procedure outlined above for my alltre's, Open the .toc file using treexplorer and export the entire contents to a folder, I used fulltoc.
3) once the export is complete you'll need to organize your fulltoc directory into useable chunks of data. So for instance the appearance folder alone contains more files than trepacker will work with so you need to divide it up. Same with some of the other data groups as well. I ended up needing to make 6 sub folders (fulltoc01-fulltoc06) in order to keep the data groups small enough for trepacker to work without stack overflows.
4) pack each of the sub folders into their own .tre file.
5) modify your swgemu_live.cfg & core3 conf files to load the new .tre files in addition to the 14.1 consolidated .tre files we made above, here is the order I use. BE AWARE THAT THE 14.1 ASSETS ARE WHAT THE CORE NEEDS, so you must set your order such that the 14.1 assets overwrite the TOC assets. Otherwise it's buggy central.
Here's my order:
[SharedFile]
maxSearchPriority=9
searchTree_00_8=mytre.tre
searchTree_00_7=alltre02.tre
searchTree_00_6=alltre01.tre
searchTree_00_5=fulltoc06.tre
searchTree_00_4=fulltoc05.tre
searchTree_00_3=fulltoc04.tre
searchTree_00_2=fulltoc03.tre
searchTree_00_1=fulltoc02.tre
searchTree_00_0=fulltoc01.tre
Use this load order for the core too.
Now, if you've managed to consolidate the assets as I have you can add objects at will, only adding what you need to change / modify to your own personal .tre file (mytre.tre in this example). If you don't need to modify an asset for it work properly, then there's no reason to include it in it's own .tre file. let it load it from the consolidated asset data.
And there you have it. Hopefully this helps some to understand how my other guides and mods work.
-Duff