Talk:Modifying resources - Revision history

Eshme at 04:21, 25 January 2010

2010-01-25T04:21:44Z

Axe Murderer at 01:38, 25 October 2009

2009-10-25T01:38:28Z

Axe Murderer: question posed - no changes made to page content it looks fine

2009-10-25T01:37:44Z

question posed - no changes made to page content it looks fine

New page

Nothing wrong with this page but reading it made me wonder. In NWN when you updated instances from the palette blueprint, every field in the instances found and updated was changed to match the blueprint. In many situations that fact annihilated the utility of having the update instances feature available. Unless changes made to the blueprint were extensive or there were only a couple of instances in the module it wasn't worth it to use the update feature because you always had to go through the whole module editing all the instances anyway after the fact in order to reset all those deviant attributes, like Name or Tag, that were changed after placement or dependent on location or something and just got wiped out by the update.

So my question is, when you use this feature in DA are there any options to decide which properties are & are not to be pushed to the instances? If not, I'd like to suggest that feature for a future patch. Maybe a list of check boxes, one for each blueprint property or category of related properties, you can select from before the instances get changed.

← Older revision		Revision as of 04:21, 25 January 2010
Line 4:		Line 4:

	-- Axe Murderer 18:38 PST, 24 Oct 2009		-- Axe Murderer 18:38 PST, 24 Oct 2009
		+
		+	----
		+
		+	I assume this is useful information, however isnt this information a bit lost all alone out here ? Its like its standing naked in a desert and nobody cares lol. Not like i can sort this into a category [[User:Eshme\|Eshme]] 04:21, 25 January 2010 (UTC)
		+	----

← Older revision		Revision as of 01:38, 25 October 2009
Line 2:		Line 2:

	So my question is, when you use this feature in DA are there any options to decide which properties are & are not to be pushed to the instances? If not, I'd like to suggest that feature for a future patch. Maybe a list of check boxes, one for each blueprint property or category of related properties, you can select from before the instances get changed.		So my question is, when you use this feature in DA are there any options to decide which properties are & are not to be pushed to the instances? If not, I'd like to suggest that feature for a future patch. Maybe a list of check boxes, one for each blueprint property or category of related properties, you can select from before the instances get changed.
		+
		+	-- Axe Murderer 18:38 PST, 24 Oct 2009