I did made a few changes to my blueprints, and looked for the Update instance button to update all the instance of my module which have 250 areas.
I tried the various tools/Technique around to update: Merge/All area, the powerbar, but not update all my areas.
I was wondering if you guys any clue on how this could be done, or if any wiz out there to pull out a plug in to do so.
Im confidant that it could be a nice tool for everyone, I unfortunately do not have the skill to do it myself.
Cheers,
WK
Update All Instance
Comenzado por
The_Witch_King
, dic 18 2010 12:40
Volver arriba
#2
Escrito 20 diciembre 2010 - 12:18
SkywingvL
-
- Members
- 351 mensajes
Hello,
I've written a program to do this (all data present in an object instance that is also present in its corresponding template is replaced with the data from the template), given a list of templates and object types (creature, placeable, etc) to update. The program is a standalone command line tool and will only work on directory mode modules.
Please catch me on irc at irc.nwn2source.net / #nwn2cr and I'll provide a copy of the program for you to test out. If it works for you, I'll post it here and include it as a sample in the next NWN2 Datafile Accessor library release.
I've written a program to do this (all data present in an object instance that is also present in its corresponding template is replaced with the data from the template), given a list of templates and object types (creature, placeable, etc) to update. The program is a standalone command line tool and will only work on directory mode modules.
Please catch me on irc at irc.nwn2source.net / #nwn2cr and I'll provide a copy of the program for you to test out. If it works for you, I'll post it here and include it as a sample in the next NWN2 Datafile Accessor library release.
Editado por SkywingvL, 20 diciembre 2010 - 12:20 .
#3
Escrito 27 diciembre 2010 - 09:16
The_Witch_King
-
- Members
- 6 mensajes
Awesome! Will try to catch you on Irc.
Oh, and happy holidays to all! ;-)
Oh, and happy holidays to all! ;-)
#4
Escrito 28 diciembre 2010 - 02:56
painofdungeoneternal
-
- Members
- 1.799 mensajes
Yes this is very ground breaking piece of work - wish i had this a year ago.
#5
Escrito 28 diciembre 2010 - 06:14
The_Witch_King
-
- Members
- 6 mensajes
just awesome!! works well!
Could "store" be added to the potential object type?
Could "store" be added to the potential object type?
#6
Escrito 29 diciembre 2010 - 03:46
SkywingvL
-
- Members
- 351 mensajes
This is the first release of the update module instances tool (now includes support for updating store objects too):
http://www.nynaeve.n...odTemplates.zip
The included readme has this to say about how to use it:
Getting started and general overview
====================================
This program performs a bulk update of placed instances in a module, copying
data from blueprints back to instances. It is intended to be used to make bulk
changes to large numbers of placed objects when you have since edited the
original blueprint. The program is designed to receive a list of object
type(s) and blueprint name(s) of placed objects that are to be updated in the
module. All areas are updated, and the process should only take a few seconds
to complete.
When an object instance is updated, all data in the blueprint replaces the
data in the object instance. Data that is present in the object instance but
not the blueprint (i.e. position information) is kept as-is. GFF lists are
replaced and not merged (for example, creature inventories).
To update object instances in your module, follow these steps:
1) Make a back-up copy of your module, in case you need to revert your changes.
2) Find the location of your NWN2 install directory (typically under
C:\\Program Files\\Atari\\Neverwinter Nights 2).
3) Find the location of your NWN2 home directory (typically under your user
documents directory, such as
C:\\Users\\<username>\\Documents\\Neverwinter Nights 2).
4) Save your module as a directory mode module under the Modules directory in
your chosen NWN2 home directory.
5) Close the toolset (if it is open). You should not have the module loaded
into the toolset when you run the program, or the toolset will overwrite any
changes made on the next save.
6) Open a command prompt (Start->Run->cmd.exe), then change to the directory
where UpdateModTemplates.exe resides (with cd "directory name").
7) Run the UpdateModTemplates program with the chosen object type and blueprint
names. For exampe, if you have a module named "My Module", and you want to
update the blueprints for all creatures with blueprint c_ancom_badger1, you
might use a command line similar to the following:
UpdateModTemplates -home "%userprofile%\\My Documents\\Neverwinter Nights 2" -installdir "%ProgramFiles%\\Atari\\Neverwinter Nights 2" -module "My Module" -template c_ancom_badger1 -objecttype creature
Note that any argument with spaces must be enclosed in double quotes. You
may specify any number of templates and object types to update at the same
time.
The -module argument should only have the name of the module directory given
and not the whole path to it.
Command line arguments listing
==============================
Running the program with no arguments will display the valid command line usage
for the program:
UpdateModTemplates
This program copies data from the specified template(s) to placed object
instances of the given object type(s) within a directory mode module.
Only directory mode modules are supported!
Optionally, a list of GFF fields may be excluded from updating via the
usage of the -excludefield parameter (for example,
-excludefield ModelScale). Use a GFF editor to pick the fields to
exclude (if desired).
Usage: UpdateModTemplates -home <homedir> -installdir <installdir>
-module <module resource name> [-nwn1]
-template <first template name to update>
[-template <additional template name N...>]
-objecttype <first object type to match>
[-objecttype <additional object type N...>]
[-excludefield <exclude field 1...>]
Legal object types are:
tree
waypoint
placedeffect
placeable
door
item
environmentobject
light
creature
trigger
sound
staticcamera
store
Advanced usage
==============
To edit a NWN1 module (instead of a NWN2 module), supply the -nwn1 argument.
To restrict the copying of fields from blueprints, use the -excludefield <name>
argument. This argument (which may be repeated any number of times) will cause
the program to not copy a specific field from the blueprint. You can use a GFF
viewer or editor program to discover field names -- BioWare's GFF Editor
program can be used to this end.
Support
=======
Visit the NWN2 Community Relations channel at irc.nwn2source.net / #nwn2cr for
assistance, should you get stuck.
http://www.nynaeve.n...odTemplates.zip
The included readme has this to say about how to use it:
Getting started and general overview
====================================
This program performs a bulk update of placed instances in a module, copying
data from blueprints back to instances. It is intended to be used to make bulk
changes to large numbers of placed objects when you have since edited the
original blueprint. The program is designed to receive a list of object
type(s) and blueprint name(s) of placed objects that are to be updated in the
module. All areas are updated, and the process should only take a few seconds
to complete.
When an object instance is updated, all data in the blueprint replaces the
data in the object instance. Data that is present in the object instance but
not the blueprint (i.e. position information) is kept as-is. GFF lists are
replaced and not merged (for example, creature inventories).
To update object instances in your module, follow these steps:
1) Make a back-up copy of your module, in case you need to revert your changes.
2) Find the location of your NWN2 install directory (typically under
C:\\Program Files\\Atari\\Neverwinter Nights 2).
3) Find the location of your NWN2 home directory (typically under your user
documents directory, such as
C:\\Users\\<username>\\Documents\\Neverwinter Nights 2).
4) Save your module as a directory mode module under the Modules directory in
your chosen NWN2 home directory.
5) Close the toolset (if it is open). You should not have the module loaded
into the toolset when you run the program, or the toolset will overwrite any
changes made on the next save.
6) Open a command prompt (Start->Run->cmd.exe), then change to the directory
where UpdateModTemplates.exe resides (with cd "directory name").
7) Run the UpdateModTemplates program with the chosen object type and blueprint
names. For exampe, if you have a module named "My Module", and you want to
update the blueprints for all creatures with blueprint c_ancom_badger1, you
might use a command line similar to the following:
UpdateModTemplates -home "%userprofile%\\My Documents\\Neverwinter Nights 2" -installdir "%ProgramFiles%\\Atari\\Neverwinter Nights 2" -module "My Module" -template c_ancom_badger1 -objecttype creature
Note that any argument with spaces must be enclosed in double quotes. You
may specify any number of templates and object types to update at the same
time.
The -module argument should only have the name of the module directory given
and not the whole path to it.
Command line arguments listing
==============================
Running the program with no arguments will display the valid command line usage
for the program:
UpdateModTemplates
This program copies data from the specified template(s) to placed object
instances of the given object type(s) within a directory mode module.
Only directory mode modules are supported!
Optionally, a list of GFF fields may be excluded from updating via the
usage of the -excludefield parameter (for example,
-excludefield ModelScale). Use a GFF editor to pick the fields to
exclude (if desired).
Usage: UpdateModTemplates -home <homedir> -installdir <installdir>
-module <module resource name> [-nwn1]
-template <first template name to update>
[-template <additional template name N...>]
-objecttype <first object type to match>
[-objecttype <additional object type N...>]
[-excludefield <exclude field 1...>]
Legal object types are:
tree
waypoint
placedeffect
placeable
door
item
environmentobject
light
creature
trigger
sound
staticcamera
store
Advanced usage
==============
To edit a NWN1 module (instead of a NWN2 module), supply the -nwn1 argument.
To restrict the copying of fields from blueprints, use the -excludefield <name>
argument. This argument (which may be repeated any number of times) will cause
the program to not copy a specific field from the blueprint. You can use a GFF
viewer or editor program to discover field names -- BioWare's GFF Editor
program can be used to this end.
Support
=======
Visit the NWN2 Community Relations channel at irc.nwn2source.net / #nwn2cr for
assistance, should you get stuck.
Editado por SkywingvL, 29 diciembre 2010 - 03:50 .
#7
Escrito 30 diciembre 2010 - 05:48
The_Witch_King
-
- Members
- 6 mensajes
Just a note when updating "store"
In my module, I am using custom icons. When I used the tool. everything updated well except that the items from the store using custom icons lost the icons properties.
Beside all other props are good.
In my module, I am using custom icons. When I used the tool. everything updated well except that the items from the store using custom icons lost the icons properties.
Beside all other props are good.
#8
Escrito 30 diciembre 2010 - 08:13
SkywingvL
-
- Members
- 351 mensajes
Are the icons stored in the template (blueprint)? If so, they would be replaced unless you exclude them with -excludefield.
#9
Escrito 30 diciembre 2010 - 10:11
The_Witch_King
-
- Members
- 6 mensajes
The store templates do not have any icon. It is the items "in" the store that has the icons.
#10
Escrito 27 octubre 2012 - 03:54
kamal_
-
- Members
- 5.235 mensajes
Thread necro... and then after a large amount of testing, nevermind, my fault somehow 
Editado por kamal_, 03 noviembre 2012 - 12:26 .
