9 replies to this topic

[Yovaneth]

I've got a bit of a funny when creating new items with DLTCEP and loading them using Weidu. The items require no lore to identify (one's a key and the other's a scroll) but when I look at them in the game, the item name is there (Key, Letter) but the long identified description is missing. Pointing both DLTCEP and NI at the in-game item shows that the identified description has been correctly attached by Weidu to each item, so I guess I've fouled up on the creation side somewhere?

-Y-

[Yovaneth]

What coding are you using? If your description isn't being shown is there any text in its place?

And I assume you've looked at it ingame?

I don't quite understand what you mean by "what coding" but yes, I have looked at them in game and the long description (right side) is simply blank. The short item description (top left) is there.

-Y-

[Potencius]

I'm not sure exactly how you're going about adding the description in DLTCEP, but if you want to add new text, you need to type -1 in the strref field first, then type your text to get a new strref added. Other than that (and I'm not even sure how that would apply, actually), I can't think of a reason DLTCEP would screw up. Might be worthwhile bringing it up with Avenger.

[Stone Wolf]

I don't know if this could be the problem, but you might need to click on another field after you enter the text before saving the item. If the cursor is still in the text box, it might not be saved.

[Yovaneth]

@Max

I'm not sure exactly how you're going about adding the description in DLTCEP, but if you want to add new text, you need to type -1 in the strref field first

I'm not - I'm actually adding the string to dialog.tlk and making the string association using a Weidu .tra/.tp2 pair. As I said, after I've run the Weidu installer, if I check both items using either DLTCEP or NI, the correct long description string is in the correct item file - it just doesn't display in-game.

@Stonewolf

I don't know if this could be the problem, but you might need to click on another field after you enter the text before saving the item.

See above

-Y-

[Avenger_teambg]

If you add an item with weidu, i guess you add the strings using its 'say' function.
If that is the case, DLTCEP is utterly innocent.
You could try to fix this in two ways:
1. export the correctly made item using dltcep's tbg export.
2. write a correct weidu script which has 4! say functions in it, one for each string. I doubt WeiDU would be buggy, otherwise many people would have alerted Wes by now.

Hmm, another question would be if you use DialogF.tlk

Edited by Avenger_teambg, 11 October 2004 - 11:43 AM.

[Vlasák]

jj, missing strrefs in DialogF.tlk can be the reason of your problem...

[Yovaneth]

@Avenger

  If you add an item with weidu, i guess you add the strings using its 'say' function. If that is the case, DLTCEP is utterly innocent.

I never thought DLTCEP was really guilty - I couldn't see how it could be. Yes, I'm using the Say function.

write a correct weidu script which has 4! say functions in it, one for each string

Now there's a thought - I was using two existing strings and two new ones for each item.

@Vlasek (Avenger included)

Hmm, another question would be if you use DialogF.tlk

No, I'm not using dialogf. I'm setting my mod up with a .tra file simply because if it gets finished and released, and then someone wants to translate it, the groundwork will have already been done.

Your replies and help have been appreciated - I'm off to try adding four strings to both items.

-Y-

[Yovaneth]

I'm off to try adding four strings to both items.

Damn - that didn't work either. Looks like I'm going to have to reduce the Weidu installer to just the two items and see what happens then.

-Y-