7 réponses à ce sujet

[Adaram]

I would love to have some help with this topic.  I have been doing a lot of B2B type stuff as part of my working with Proleric1 on Crown of Creation, and either I am missing something obvious, or, things are really complicated (or both, perhaps).

In a nutshell, Proleric owns the baseline "module", and every so often, he'll release a new cut of the baseline.  Of course, the things I have been working on in the meantime are in my version of the module, however, are not in his new baseline.

I thought that the B2B import would manage all the differences, and I would just be able to take his new baseline and merge the changes into my existing module, but it seems that when I try and do that, I have no end of problems of various natures.  Given that, a backup plan would be to export "my stuff" to a B2B, restore a clean database, re-import the baseline from scratch, then import the B2B of my stuff back into the new baseline.  This is a scary option since I don't feel confident that I won't miss something or other and lose it with the database purge.

All in all, I am looking for guidance on what others are doing to share their modules and their work.  

Does anyone know of an ironclad process that works every time when it comes to this?

Thanks in advance, and sorry for the wall of text!
 

Modifié par Adaram, 18 mars 2010 - 08:57 .

[Proleric]

I think I figured out where we were going wrong.

Before doing a refresh B2B Load, it's necessary to check in all custom resources (except ones being worked on locally, which should be checked out).

On the B2B Load screen, the Import box (first column) should be checked for all custom resources (except those which are checked out, which you can't select).

The Create New box (last column) should NOT be checked.

All of this is documented correctly in the wiki, but I had to work through it a few times to get it right in practice.

@Adaram - sorry you had this frustration - my fault - I've updated my documentation in readiness for the next internal release.

Modifié par Proleric1, 19 mars 2010 - 03:48 .

[Adaram]

If all of this is correctly documented in the wiki, then it's hardly your fault

Like I said in my status update today, it's likely "me"!

I'll have another go with this vital piece of information regarding "checking in" and "checking out" and let you know how it goes!



Thanks

[Adaram]

The Create New box (last column) should NOT be checked.

There are several resources with the names "Stringxxxxxxxx" that seem to be coming from the B2B that have Import and Create New clicked -- and I can't change those, so I assume that those would be exceptions to the above noted rule?

[Adaram]

I did the import the way we described. I updated the readme.txt for our b2b baseline. I was able to jump right into the game with no issues, except I got killed

[Proleric]

Adaram wrote...

The Create New box (last column) should NOT be checked.

There are several resources with the names "Stringxxxxxxxx" that seem to be coming from the B2B that have Import and Create New clicked -- and I can't change those, so I assume that those would be exceptions to the above noted rule?

Strings are a great way to tie yourself in knots in DAO...

As you know, to work around the string id issue, we have two protocols for team members - Create New for writer/designers and Use Theirs for cutscene/VO work.

Unfortunately, you need to conserve the id on standalone strings, because they're referenced by 2DA tables.

So you'll need to do a separate B2B Load on the strings with Use Theirs. My bad.

[Adaram]

...
and what is the impact if I don't do a second load (which I didn't)? Will those strings have been loaded with new StringID's?

So to be clear, next time, I need to do a B2B load with all non-core resources, as discussed, but not the ones with Stringxxxxx. I then need to do a second load with just the Stringxxx tyoe, but instead of "Create New", I "Use theirs".

Modifié par Adaram, 21 mars 2010 - 11:56 .

[Proleric]

That's the right idea.

Loading the strings with Create New does no harm - it just means you have some talk table entries that will never be used for anything (they are orphaned, because nothing refers to them).

Loading the strings again with Use Theirs will duplicate the strings in your talk table, but this time they will have the intended string id, which is referenced by the 2DA table.

In our particular case, the strings are used in the custom character generation.