Builder to builder - Revision history

Sunjammer: Added to my "To Do" list

2011-12-28T19:41:51Z

Added to my "To Do" list

Proleric1: /* Importing database resources */

2011-04-16T16:59:19Z

‎Importing database resources

Proleric1: /* Importing database resources */

2011-04-16T16:58:52Z

‎Importing database resources

Proleric1: /* Importing database resources */

2011-04-16T16:56:32Z

‎Importing database resources

Proleric1: /* Importing database resources */

2011-04-16T16:56:04Z

‎Importing database resources

Proleric1: /* Importing database resources */

2011-04-16T16:53:36Z

‎Importing database resources

Kelamor: Add languages bar

2011-02-14T23:46:16Z

Add languages bar

Proleric1: /* Importing database resources */

2010-03-13T07:28:45Z

‎Importing database resources

Proleric1: /* Importing database resources */

2010-03-12T00:12:19Z

‎Importing database resources

Proleric1: /* Importing database resources */

2010-02-17T14:22:41Z

‎Importing database resources

← Older revision		Revision as of 19:41, 28 December 2011
Line 1:		Line 1:
		+	{{ToDoListItem\|Sunjammer}}
	{{Infobox module}}		{{Infobox module}}
	"Builder to builder" is a general term for the process of exchanging game resource information between builders, for example between several people who are collaborating on building a module. See [[builder to player]] for the process of packaging up finished works to distribute to players.		"Builder to builder" is a general term for the process of exchanging game resource information between builders, for example between several people who are collaborating on building a module. See [[builder to player]] for the process of packaging up finished works to distribute to players.

@@ Line 37: / Line 37: @@
 == Importing database resources ==
-See also [[Builder to builder#Copying a Module]].
+See also [[Builder to builder#Copying a Module | Copying a Module]].
 Importing resources is done via the "Builder to Builder Load" command under the "Tools" menu (there's also a B2B create command here, the same that can be reached via the palette right-click menu):

@@ Line 37: / Line 37: @@
 == Importing database resources ==
-See also [[Copying a Module]].
+See also [[Builder to builder#Copying a Module]].
 Importing resources is done via the "Builder to Builder Load" command under the "Tools" menu (there's also a B2B create command here, the same that can be reached via the palette right-click menu):

@@ Line 37: / Line 37: @@
 == Importing database resources ==
-See also [[Importing a Module]].
+See also [[Copying a Module]].
 Importing resources is done via the "Builder to Builder Load" command under the "Tools" menu (there's also a B2B create command here, the same that can be reached via the palette right-click menu):

← Older revision		Revision as of 16:56, 16 April 2011
Line 36:		Line 36:

	== Importing database resources ==		== Importing database resources ==
		+
		+	See also [[Importing a Module]].

	Importing resources is done via the "Builder to Builder Load" command under the "Tools" menu (there's also a B2B create command here, the same that can be reached via the palette right-click menu):		Importing resources is done via the "Builder to Builder Load" command under the "Tools" menu (there's also a B2B create command here, the same that can be reached via the palette right-click menu):

← Older revision		Revision as of 16:53, 16 April 2011
Line 62:		Line 62:

	Resources with the same name that already exist in the destination database and that are checked out by other users aren't editable, so the "checked out" column will warn you of any resources that the import process will be unable to update. This is unlikely to be a concern when only a single user (yourself) has access to your database but may become significant in a more sophisticated multi-user collaborative environment.		Resources with the same name that already exist in the destination database and that are checked out by other users aren't editable, so the "checked out" column will warn you of any resources that the import process will be unable to update. This is unlikely to be a concern when only a single user (yourself) has access to your database but may become significant in a more sophisticated multi-user collaborative environment.
		+
		+	== Copying a Module ==
		+
		+	You might want to copy a module to a new machine, a new data base, or another builder's data base.
		+
		+	Builder-to-Builder Create is a good way to backup your resources for transfer or recovery.
		+
		+	When you want to make a copy, create a new module in the target data base, entering the resource name and Name property manually.
		+
		+	If you have VO, you'll want to ensure string ids don't change during load (otherwise you'll have to rename all the VO files).
		+
		+	If you know what string range was defined for the original module, change the new module to the same range.
		+
		+	If you've lost the original module and have no independent record of the string range, you need to ensure that all the strings in the .dadbdata file are in range. Temporarily, you can set the start of the range to 1, and the end of the range to a very high value.
		+
		+	Now do the Builder-to-Builder Load, with the Use Theirs option for string ids.
		+
		+	If you have a temporary string id range, examine the new module in the String Editor to discover the lowest and highest string id values. Set the range start to the lowest, range next to one higher than the highest, and range end as high as you like.
		+
		+	Finally, change the other module properties, such as the start area / waypoint and the module script. That has to happen last, because you select from the resources you just loaded.

	== Sharing a live database ==		== Sharing a live database ==

@@ Line 76: / Line 76: @@
 Though this is fully possible in principle with the existing toolset, the specifics for how to accomplish this outside the BioWare intranet haven't been tested yet so we don't have documentation for it yet.
 [[Category:Database]]
 [[category:modules]]

@@ Line 46: / Line 46: @@
 [[File:B2B load panel 973.png|center|]]
 You can choose to import or not to import specific resources from this panel with the leftmost checkbox. Note that if you only import some of the files you may break dependencies. However, many of the dependencies in any significant export are likely to be core resources that you already have in your database and it's wise to avoid re-importing such resources unless you have a specific reason to.
-You have the option to assign new string ids, or retain the original string ids, which allows you to maintain integrity of reference to the talk table. There seems to be a [[Bug:_Builder_to_Builder_Load_may_not_reproduce_resource_detail_correctly | bug]] with "Use Theirs".
+You have the option to assign new string ids, or retain the original string ids, which allows you to maintain integrity of reference to the talk table. There seems to be a [[Bug:_Builder_to_Builder_Load_may_not_reproduce_resource_detail_correctly | bug]] with "Use Theirs". See [[String ID]] for a discussion of sharing issues.
 ResRefID is the identifier that the resource had in the database it was exported from. ResRefIDs must be unique within any given database, so these numbers will be reassigned automatically during the import process.

← Older revision		Revision as of 14:22, 17 February 2010
Line 46:		Line 46:

	[[File:B2B load panel 973.png\|center\|]]		[[File:B2B load panel 973.png\|center\|]]
		+
		+	[[Bug : Builder to Builder Load may not reproduce resource detail correctly]]

	You can choose to import or not to import specific resources from this panel with the leftmost checkbox. Note that if you only import some of the files you may break dependencies. However, many of the dependencies in any significant export are likely to be core resources that you already have in your database and it's wise to avoid re-importing such resources unless you have a specific reason to.		You can choose to import or not to import specific resources from this panel with the leftmost checkbox. Note that if you only import some of the files you may break dependencies. However, many of the dependencies in any significant export are likely to be core resources that you already have in your database and it's wise to avoid re-importing such resources unless you have a specific reason to.