Pack File Manager 2.4.1 - Compatability Features added

**univec** · March 31, 2012, 09:04 PM

Originally Posted by madpluck

you should never edit the files directly, you should always extract the tables from the files, and make your own mod. that's what the PFM is really for. if you do that you should not have these problems, and can always just remove the mod to get your normal files back. i have changed almost everything in unit_stats_land before; when my game crashes as a result it is because i have made a critical mistake. if you upload a mod on here with just the unit_stats_land file, and tell me what you've edited, i will look at the file for you.

I've made the necessary changes in Patch 17 instead. There seems to be no problems so far. Thank you for the explanation, as I thought PFM is a tool to change the primary files. I'd have to do that next time.

Originally Posted by DaFranker

Is it me, or is the source code publicly available on sourceforge only for 1.7.5?

Here's a fix: Rename patch15.pack, patch16.pack and patch17.pack, to patch15.bak, patch16.bak and patch17.bak. Then go on steam, find Shogun 2, right click it, choose "Properties", "Local Files", "Verify Integrity of Game Cache". This will redownload the patch files, and might take a while.

Then, in the future, whenever you try to change the tables or mod something, remember to MAKE A NEW PACK FILE AND NEVER EVER CHANGE THE PATCH FILES DIRECTLY. This will save you hours of frustration, agony, and peer ridicule and snickering.

*Sigh* Sadly I should've understood this before. I make changes and always have a copy of the files in another place, but I guess I never really understood the necessity of creating a separate mod when editing the original will do. Need to change that way of thinking.

Thanks everyone!

**DaFranker** · March 31, 2012, 10:39 PM

Originally Posted by univec

*Sigh* Sadly I should've understood this before. I make changes and always have a copy of the files in another place, but I guess I never really understood the necessity of creating a separate mod when editing the original will do. Need to change that way of thinking.

Thanks everyone!

While it might "do", it'll often produce undesired or unexpected results, as was the case with the patch15 pack issue earlier. It also makes keeping track of what you've changed and where much harder as you accumulate more and more personal mini/sub -mods, like I do.

**univec** · March 31, 2012, 10:58 PM

Originally Posted by DaFranker

While it might "do", it'll often produce undesired or unexpected results, as was the case with the patch15 pack issue earlier. It also makes keeping track of what you've changed and where much harder as you accumulate more and more personal mini/sub -mods, like I do.

That's very true.. Thanks for the valuable input..

**THANGDACLAC** · March 31, 2012, 11:07 PM

Hi daniu! look at gun_type_to_projectiles_tables > gun_type_to_projectiles - version 1, may be some errors with it? thanks! (patch17).

**DaFranker** · April 01, 2012, 12:37 AM

Originally Posted by THANGDACLAC

Hi daniu! look at gun_type_to_projectiles_tables > gun_type_to_projectiles - version 1, may be some errors with it? thanks! (patch17).

Fixed schema for gun_type_to_projectiles:
http://dl.dropbox.com/u/17271099/schema.xml

**Akaie** · April 01, 2012, 12:58 AM

I actually like this over the old setup. It's easier to amalgamate additional work, and as you convey, it takes no more than a second or two to delete before importing

.

Originally Posted by daniu

You mean, delete all entries before importing? I can do that, but I found adding to be more flexible.
Clearing the table doesn't exactly take a lot of work from the user either; select top left cell, press Ctrl-A, press Delete.

**daniu** · April 01, 2012, 01:06 AM

Originally Posted by DaFranker

Is it me, or is the source code publicly available on sourceforge only for 1.7.5?

No, I work directly on the svn repository on SF, it must be there somewhere.
Of course it's possible I keep checking in with the wrong branch checked out

I pretty much set it up as suggested in the READMEs I found for SVN, using trunk as well as branches and tags. I use tags for the releases, if you checkout svn.code.sf.net/p/packfilemanager/code/tags/release-2.0.5, that should give you the actual 2.0.5. Of course, trunk is (a bit) more recent.

Originally Posted by DaFranker

Fixed schema for gun_type_to_projectiles:
http://dl.dropbox.com/u/17271099/schema.xml

Thanks for the effort. Sadly I have already been working on adding some more fkey references for other tables (agents, buildings, cai), so I can't give you full credit for schema_9.zip

Are you using the decoder tool by any chance? I'm actually quite proud of it, it makes analysing tables so much easier (you probably wouldn't know if you never tried it without...). It's in a pretty rough state though since I've basically been the only one using it up to now so I never worked out the quirks it still has.

Originally Posted by Anton III

I actually like this over the old setup. It's easier to amalgamate additional work, and as you convey, it takes no more than a second or two to delete before importing

.

I'll keep it this way then if Yarkis can't find some people to support him

**DaFranker** · April 01, 2012, 02:01 AM

Originally Posted by daniu

No, I work directly on the svn repository on SF, it must be there somewhere.
Of course it's possible I keep checking in with the wrong branch checked out

I pretty much set it up as suggested in the READMEs I found for SVN, using trunk as well as branches and tags. I use tags for the releases, if you checkout svn.code.sf.net/p/packfilemanager/code/tags/release-2.0.5, that should give you the actual 2.0.5. Of course, trunk is (a bit) more recent.

Hmm, I wasn't checking out any branches or tags, since read-only access only lets us see the bottom-level default trunk dir and we have no access or visibility to anything top-level. I wasn't even sure whether there were branches or tags in the first place!

The only link sourceforge gives me is svn.code.sf.net/p/packfilemanager/code/trunk

That's also the only way to see any of the code, because the page seems bugged and doesn't allow anything else. Even the standard "browse code in browser" option is nowhere to be found. As for what's in the trunk, if I try to compile it I get a 1.7.5 Beta version. Going back up to /code/tags/ in the SVN gives me releases up to 1.7.5 but stops there. Maybe a "hidden" flag somewhere?

As far as I can tell, the 2.0.5 source isn't anywhere (publicly visible, that is) on that SF project.

EDIT: Actually, trying to grab anything from /code/tags/release-2.0.5 or placing trunk anywhere in there or removing "tags" or any other combination I've thought of just returns url-not-found errors.

Originally Posted by daniu

Thanks for the effort. Sadly I have already been working on adding some more fkey references for other tables (agents, buildings, cai), so I can't give you full credit for schema_9.zip

No problem there, glad to help. I've got a few more changes, mostly to largely-irrelevant tables that I just happened to click on and saw that the solution to fix was quite easy. I've updated my dropbox schema with the more recent fixes I got (same link as before).

Originally Posted by daniu

Are you using the decoder tool by any chance? I'm actually quite proud of it, it makes analysing tables so much easier (you probably wouldn't know if you never tried it without...). It's in a pretty rough state though since I've basically been the only one using it up to now so I never worked out the quirks it still has.

Yes, I'm using it, though sometimes if I'm stuck I'll take out the file in a hex editor in raw mode and copy bits and parts to virtual tables in notepad++ to better visualize possible patterns. Particularly useful for those "Is this two ints and a bool and then three floats, or four bools, an int, a string and an optstring?" situations, since because I've already determined where rows start I can compare all the rows visually to see what kind of value would be valid there.

The DecodeTool very handy indeed, though a few particular features like substitution, insertion and gridview come to mind as to the kind of things that would help it really shine. Then again, not really necessary since db changes are rarely as big and complex as this patch and don't come all too often.

**daniu** · April 01, 2012, 02:48 AM

Originally Posted by DaFranker

The only link sourceforge gives me is svn.code.sf.net/p/packfilemanager/code/trunk
That's also the only way to see any of the code, because the page seems bugged and doesn't allow anything else. Even the standard "browse code in browser" option is nowhere to be found.

The project was recently migrated to a new backend and I'm pretty sure something went wrong.
I opened a ticket with SF about this.
Try https://packfilemanager.svn.sourcefo...emanager/trunk
it's what I'm working on now, I'm not sure if it can be checked out by unregistered users.

Tfeatures like substitution, insertion and gridview come to mind

Yes they do don't they?
Well I was too lazy for the GridView.
There is a substitution between bool and optstring at least (it's the most common and annoying mistake made). Select the field type on the left, and use the "bool <-> optstring" menu item.
Insertion works the same way. Select a field type on the left, and if you click one of the "Set" buttons, the gets inserted at the cursor position.

**Yarkis de Bodemloze** · April 01, 2012, 02:51 AM

I tried to decode taxes_effects_jct_tables with the inbuild tool. I got that far (see below) but not any further. Maybe somebody (*points to the guys two posts above him*) can help?

Code:

<table name='taxes_effects_jct_tables'>
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
	<field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
	<field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
	<field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
	<field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
  </table>

As far as the tsv import function is concerned...I yield...for now...

**Radious** · April 01, 2012, 04:05 AM

What about character_experience_skill_tiers and character_skill_level_to_effects_junctions tables? These are important to change how fast generals/agents level up and how many points they get per level.

**daniu** · April 01, 2012, 05:06 AM

Originally Posted by Yarkis de Bodemloze

I tried to decode taxes_effects_jct_tables with the inbuild tool. I got that far (see below) but not any further. Maybe somebody (*points to the guys two posts above him*) can help?

Spoiler Alert, click show to read:

Code:

<table name='taxes_effects_jct_tables'>
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='boolean' />
    <field name='unknown' type='string' />
    <field name='unknown' type='string' />
    <field name='unknown' type='float' />
  </table>

Been working on the tables for quite some time now, mostly adding references. Missed that table.
It's:

Code:

<table name='taxes_effects_jct_tables'>
    <field fkey='taxes_keys_tables.Tax Effect ID' name='Tax Effect IDRef' type='string' pk='true' />
    <field fkey='effects_tables.Effect ID' name='Effect_IDRef' type='string' pk='true' />
    <field fkey='cdir_campaign_junctions_tables.Campaign' name='Campaign Ref' type='optstring' version_start='1' />
    <field name='unknown' type='optstring' version_start='1' />
    <field name='unknown' type='optstring' version_start='1' />
    <field name='Magnitude' type='float' />
  </table>

You were close though

Originally Posted by Radious

What about character_experience_skill_tiers and character_skill_level_to_effects_junctions tables? These are important to change how fast generals/agents level up and how many points they get per level.

Yeah those I had already.
Uploaded schema_10.zip, update if you want them.

I'm putting quite some time into finding the references between the tables.
Do you even want those?

**Radious** · April 01, 2012, 06:37 AM

Excelent Schema 10 can open those perfectly. Many thanks good Sir. References are always handy so if its not too much work then sure, put everything you can :-)

**Akaie** · April 01, 2012, 08:51 AM

I noticed something weird about the way PFM was showing me the new agent_uniforms table, so I told it to show me another string as such:

Code:

  <table name='agent_uniforms_tables'>
    <field name='Agent ID' type='string' pk='true' />
    <field name='Uniform' type='string' pk='true' />
    <field name='Modern Agent ID' type='string' pk='true' />
  </table>

Like this, it makes much more sense. After having a good look, I concluded that this has something to do with a modernization mechanic of FotS, as the left and right columns are both unit_variant references. That also explains all the "n/a" entries and the unit_variant references for the Sengoku daimyo, which reference the same unit parts as their left side counterpart.

**DaFranker** · April 01, 2012, 09:04 AM

Originally Posted by daniu

The project was recently migrated to a new backend and I'm pretty sure something went wrong.
I opened a ticket with SF about this.
Try https://packfilemanager.svn.sourcefo...emanager/trunk
it's what I'm working on now, I'm not sure if it can be checked out by unregistered users.

Yes, this works. Doesn't seem to be any problem with a checkout.

And yeah, something probably went wrong. That's not even close to the filepath it tells us the code should be.

...not used to lightweight projects like this. I was expecting to post this, go do something else, come back much later with the checkout download finally done after half an hour. It got finished while I was writing the above.

As far as features go, I'd really like a better explorer-like integrating in the pack file tree on the left. Stuff like shortcuts (F2 to rename comes to mind) and drag-and-drop refoldering would be immense timesavers. Also, better handling (read: more 'Excel-like' with inserts and copy multiple and better clipboard handling with working shortcuts

) for the main DBFileEditorControl panel would be pretty helpful. These two "features" are pretty much what convinced me to take a look at the source and see if I can help.

While just porting over the DBEditor editor (there's a tongue-twister in the making in there) seems like a good idea at first, IMO it'd be much more trouble than just adding from it the missing bits.

**THANGDACLAC** · April 01, 2012, 09:11 AM

Originally Posted by DaFranker

Fixed schema for gun_type_to_projectiles:
http://dl.dropbox.com/u/17271099/schema.xml

Thanks DaFranker and daniu!!!

**daniu** · April 01, 2012, 09:37 AM

Originally Posted by Anton III

I noticed something weird about the way PFM was showing me the new agent_uniforms table, so I told it to show me another string as such:

Indeed. I could have sworn I came across that before and had fixed it... ah well.
schema_11.zip uploaded with this change and some more references I found. I stop the reference hunting now, so this should be the last update for some time if nothing groundbreaking is found.

Originally Posted by DaFranker

As far as features go, I'd really like a better explorer-like integrating in the pack file tree on the left. Stuff like shortcuts (F2 to rename comes to mind) and drag-and-drop refoldering would be immense timesavers. Also, better handling (read: more 'Excel-like' with inserts and copy multiple and better clipboard handling with working shortcuts

) for the main DBFileEditorControl panel would be pretty helpful. These two "features" are pretty much what convinced me to take a look at the source and see if I can help.

I hope you don't plan on starting sending me any code I'll then manually have to integrate into SVN...

If you want to help that's great but please do so by registering at sourceforge and having me add you to the project.
It may be lightweight but it is a project that requires more management than you'd expect, and we do actually have a development process.

I don't think F2 will be of huge impact, and neither will d&d within PFM. Files are rarely renamed and even rarer moved within the structure (the game does expect them in a certain place after all).
I won't put much work into editing capabilities either, export to CSV works fine after all, no need to reinvent the wheel.

While just porting over the DBEditor editor (there's a tongue-twister in the making in there) seems like a good idea at first, IMO it'd be much more trouble than just adding from it the missing bits.

Indeed. Not least because the DBE works on the old Common API, I rewrote it almost completely.

**DaFranker** · April 01, 2012, 09:59 AM

Originally Posted by daniu

I hope you don't plan on starting sending me any code I'll then manually have to integrate into SVN...

If you want to help that's great but please do so by registering at sourceforge and having me add you to the project.
It may be lightweight but it is a project that requires more management than you'd expect, and we do actually have a development process.

Haha. At worst I'd have posted a diff patchfile if it's just small changes that are easy to integrate and probably won't break anything. Otherwise, I usually ask if/how people want to get my code. Most of my changes to any tool are really just for personal use, but I share and try to help because it's fun and feels good to do so.

Originally Posted by daniu

I don't think F2 will be of huge impact, and neither will d&d within PFM. Files are rarely renamed and even rarer moved within the structure (the game does expect them in a certain place after all).
I won't put much work into editing capabilities either, export to CSV works fine after all, no need to reinvent the wheel.

Sure, you can say that, but what if I told you I've had to rename and recreate several dozen db folder trees (that's 'trees', obviously each tree has more than one folder) for small modular pack files either for custom mods or for testing just in the past 24 hours? Granted, that's mostly because of the recent patch, but still.

Then again, "Export all to TSV" and "Add all from directory and auto-import-from-TSV" would pretty much cancel/fix all of that.

**daniu** · April 01, 2012, 10:22 AM

Originally Posted by DaFranker

what if I told you I've had to rename and recreate several dozen db folder trees (that's 'trees', obviously each tree has more than one folder) for small modular pack files either for custom mods or for testing just in the past 24 hours?

Then I'd ask you why you didn't just export them all, used Windows and available tools to rename the files, and then re-import

Seriously though, if you want to put in some spare time helping develop PFM for fun, knock yourself out. Registering at SF is free and has everything we need pretty much (well the svn server mostly

and a bug tracker to keep an overview of changes).

**DaFranker** · April 01, 2012, 10:59 AM

Originally Posted by daniu

Then I'd ask you why you didn't just export them all, used Windows and available tools to rename the files, and then re-import

Seriously though, if you want to put in some spare time helping develop PFM for fun, knock yourself out. Registering at SF is free and has everything we need pretty much (well the svn server mostly

and a bug tracker to keep an overview of changes).

Well, the reason I didn't is that I was running scripts on the data, which required TSV formats for me to edit. From there, exporting the DB files as-is (instead of export-to-TSV) from patch17, deleting the folders I didn't want and then re-importing that in a new pack, then deleting all table entries and importing TSVs one by one, was what I'd have had to do to do what you suggest above.

Considering that the import-directory uses the crappy windows-Folder-select form that can't navigate anything worth

, starts you up at Desktop and doesn't give you anything like an address bar, and that my working files are usually nested in steam\steamapps\common\total war shogun 2\data\modding\wip\currentmod\db\... that's a hell of a lot of sloowww clicking and mouse-aiming, whereas copy-pasting the folder address is so much faster.

So yeah, at that point, it was possibly about even or only marginally slower, but a hell of a lot less annoying and frustratingly cumbersome, to just make empty dirs manually in PFM and import DB from TSV. I guess it's mostly a question of finding the right process that works for you, which I haven't done yet.

One of these days I'm going to learn, implant OLE hooks into PFM, and have my entire modding be done for me through VB scripting (for col in gridview, if col.resize(1,1).value = "upkeep", for cell in col, cell.value = cell.value / 2, gg mod for half upkeep done). Plus, script-based modding would be inherently module-compatible if the user is willing to execute the script themselves on whichever mods they want it to apply to!

Yeah, lots of wishful thinking and saw-toothed cancer-curing canaries in there.

Thread: Pack File Manager 2.4.1 - Compatability Features added

Thread Tools

Search Thread

Display

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Re: Pack File Manager 2.0.5

Posting Permissions