Convert PC (bic) to NPC (blueprint). Impossible?

[Legacy_FunkySwerve]

               

HipMaestro wrote...

Trying to grasp the scope discussed here, so far...

Funky's
suggestion addresses the ability to generate uti versions of the data
found within a list of bics using a loop procedure of sorts, at least
that is my rough interpretation.  The main hurdle for me is making sure
all the necessary components are installed to process a letoscript file.
 Still working on this.  (Funky, plz chk ur mesg center for some
peripheral guidance by me regarding letoscript.)

I accepted the friend request, but I see no messages. The thread I mention
in the Scripting forum, linked
here,
explains every step in installing all that you need to run letoscript
files using Moneo.

The alternative WhiZard proposes
seems actually less involved although there is an issue of populating
some default fields like event scripts, appearance, description, CR...
essentially all values that are not normally associated with a PC
profile (bic).  I would expect that saving the DB object would need to
be interrupted (or redirected temporarilty)  to a file that contains the
default values while those fields are filled in.  The procedure itself
would likely be: load a module with the conversion-intended PC, run the
conversion script, then quit, possibly rename the resultant object  (not
sure if the object created uses an existing ID or a default name),
reload module with the next bic, and then rinse and repeat until the
entire local vault has been converted.  Am I even close to the basic
mechanics of this alternative?   Would the resultant DB object be a uti
or some other file format?

Actually, that way seems a LOT more
involved, though my way means puzzling a few things out up front. It
also doesn't really do what you were asking, and I didn't read Whiz as
actually suggesting it.

Some other clarifications. Most bioware
file formats are variations on gff files (for generic file format, or
general, I forget). utis are for items, not creatures, those are stored
in utcs. I think of the 'ut' as universal template, like a resref,
though I forget if that's what it actually stands for. The i at the end
of uti is for item, however, the c in utc for creatures, p in utp for
placeable, t in utt for trigger, w in utw for waypoint, and so on - that
may help you to remember.

Maybe you should tell us why you want to do what you asked how to do - it's a little hard to tell if a database-based approach would even work for you.

Funky
               
               

               
            

[Legacy_OldMansBeard]

               Sorry if I have come late to the party.

Converting your bic files via the OHS to make henchmen you can embed in a module, would certainly be possible with a bit of extra scripting. You could take the RecallHenchmen() function in ohs_i0_commands as a guide. You would just need some extra scripting to put each henchman in the right place to start the module.

But that's a silly way to do it '>

Leto does convert bic files to utc files and embeds them in an erf for you to import into a module in the toolset. At least, the version of Leto that I have does that. I'm looking at Leto Hotu 4.7.5.70 as modified by Kaliea which is on the NWVault but that's many years out of date and you might want to use this one instead.
               
               

               
            

[Legacy_FunkySwerve]

               

OldMansBeard wrote...

Leto does convert bic files to utc files and embeds them in an erf for you to import into a module in the toolset. At least, the version of Leto that I have does that. I'm looking at Leto Hotu 4.7.5.70 as modified by Kaliea which is on the NWVault but that's many years out of date and you might want to use this one instead.

Whoa, nice. Learned something. Still, one-at-a-time...eh, depends on what you want to do it for, I guess.

Funky
               
               

               
            

[Legacy_werelynx]

               Why don't you save game with the .bic and then change the extension of the .sav (?) file to .mod?\\
Afterwards open in toolset make blueprint and export..
               
               

               
            

[Legacy_Thayan]

               Ok - need a little help here. So I have figured out (I think) how to use Leto to create an erf with the bic file saved as a utc. But when I import that into the module, it doesn't show up in any of the palettes (likely because the creature was never assigend one, I suppose). If I reimport the erf, it says teh creature resource is already there, but even if i try to create it programtically using CreatObject with the resref for the converted PC as it shows using NWNExplorer, I still can't create it.

The same thing also happens if a convert a sav to a mod and open it in the toolset - no PC 'creature' to be found.

So how does one go about getting these converted bic-to-utc files in either case?
               
               

               

                     Modifié par Thayan, 07 septembre 2013 - 03:10 .
                     
                  

            

[Legacy_FunkySwerve]

               Use Alia, another app by dragon song (on his leto sourceforge page), or you can use moneo/letoscript, to set the palette id to whatever you need. You can also download Alia here:

Funky's Dropbox Alia link from the Scripting forum tutorial on mass edits and datamining

LMK if you need more help. You can find the appropriate palette number by looking at it in NWNExplorer, or just by grabbing a creature in the current palette in the category you want, and looking at in in Alia.

I generally copy files out of my module before using leto/alia/etc on them, by the way, so I have a second copy, and I make another backup if I'm intending to edit the copy and put it back in the module, as a failsafe.

We use the cep, but have our own custom palettes in the custom hak. For us, Special/Custom 1 is PaletteID 0, and Special/Custom2 is 1, just by way of example.

Funky