4 réponses à ce sujet

[DLAN_Immortality]

I've been writing a lot for my mod in the toolset (in the dialog tree).

However, at some point I'd like it to be proofread.

Is it possible to export it in a comprehensive manner for a proofreader and then import it back again (easily)?

Thanks!

[Phaenan]

Without the proofreader having to use the toolset, not sure if that's possible as yet. Apparently the TLK format changed a bit and the existent NWN2 tools (such as TabularFramework ) wasn't able to read my custom stringtable last time I tried. (hoped I'd be able to work on the dlg even while sitting at another computer)
So, since the toolset doesn't seem to have a xml import/export option somewhere, I'd say we'll have to wait until someone make a DAO compatible tlk table editor. (or update one of nwn2's)
Would be glad to be proved wrong, tho.

The only remaining option is to use the Builder-to-builder exports and imports since it does puts everything in an human readable XML format, even string table entries. But that'd be painful to proofread a complex dialog that way. Jounal (quest/codex) entries or item descriptions, yeah, why not, but dialogs lines... urrh. Not impossible as each dialog resource is exported into a big XML doc, but the dialog tree is no longer clearly visible (just stored in attribute elements) and the actual lines are drowned in an ocean of other properties so technical unsavy proofreaders may not be happy bears with those files.

Modifié par Phaenan, 28 novembre 2009 - 01:16 .

[DLAN_Immortality]

And if the proofreader has the toolset then which steps should I take?



Thanks :-)

[Phaenan]

Oh, then of the top of my head, simply make a builder-to-builder package including only your dialog resource. The proofreader can then import it via b2b load, export it back by creating another b2b package... and finally you can import it back with b2b load.

The dadbdata package will not only contain the dialog resource (named something like "phae_forgemaster_dlg_4_8085.xml") but also every single script/conditional/stuff used in the dialog, tho. You may want to use caution when importing the proofreaded builder package back into your toolset, as imho there'll be no warning if the local version of one of the scripts is newer than those included in the package.



Never tried myself, so... well, sorry if that doesn't work.

[DLAN_Immortality]

Thanks! I'll give it a try! :-)