Okay, just about done with some major mods, and used a whole hell of a lot of WeiDU features, and I must say, this is seriously one powerful tool for modding these games. Major kudos. There's very little I couldn't do. But there were a couple of blocks, and since this forum says it's meant for feature requests, thought I'd throw them out there. And hey, maybe somebody will point out there -is- a way to do these things that I just missed.
Dunno if these things have been asked for before, btw, and sorry if I'm beating any dead horses.
WISH LIST:
1. REPLACE_TRANS_TRIGGER, with the same functionality and syntax as REPLACE_TRANS_ACTION. This would seriously rock. The lack of such a function is the only thing really preventing me from making my mods totally non-destructive of existing content (ALTER_TRANS being the only alternative I know of to modify a single response trigger, and it is destructive).
2. A way to totally remove a JOURNAL or REPLY strref, which thebigg already said he was going to implement - yay
3. When using the various weidu --tlkcmp-from/tlkcmp-to options on the dialog.tlk file, add some sort of switch to handle when either of the dialog.tlk files contain non-standard carriage return handling, like CRLF. An example where this happens and has caused me tremendous grief is the Planescape Torment dialog file... try doing --traify-tlk on that and then pull it up in ConTEXT (all carriage returns are doubled), or pull it up in Notepad, save it, and reload it (most carriage returns deleted altogether), and you'll see what I mean. If it could be made so the comparison functions would -not- count a difference in carriage-return/line feeds as a significant difference, that would solve all the problems I encountered.
4. This probably is due to similar issues as #3 - when I ran "APPEND_FILE" on the PS:T file "quests.ini" to add something to the end of it, all the blank lines in my resulting file were gone, oddly including the blank lines -before- the point where I did my append.
5. I don't know if this matters -at all-, but I couldn't help noticing that, when you do STRING_SET, it makes the type of each entry in the dialog.tlk file a "7", which IESDP says is only meant for BG2. I haven't noticed it causing me any problems yet, but maybe there should be some way to tell STRING_SET what type to set the STRING as, or perhaps not to change whatever it originally is. As I said, though, it's not caused me any problems yet, so this is a really low priority request. Maybe someone else can think of an issue it -could- cause though.
6. There is no 6. After pummeling this tool hard for several weeks, those are really the only significant issues I found. Not bad at all, gents
Qwinn