teambg core stripdowns, and dltc's dialog.tlk contain *!* strings as placeholders for removed string references coming from the old game. Is it possible (via option), to reuse these strings ?
If you want to make it more general, maybe let the user specify the placeholder string. (Though I doubt anything else is being actively used).
I suppose WeiDU already supports mass replacing a range of strrefs with an arbitrary constant string ( in our case it is *!*), if not, then maybe that feature would be good too.
feature request: strref recycling
Started by Avenger_teambg, May 21 2003 10:37 AM
3 replies to this topic
#2
weimer
-
- Member
- 1569 posts
Posted 21 May 2003 - 10:47 PM
You would like a weidu option that has weidu store a new string inside an old strref that contains *!* (or whatever) instead of appending the new string to the end of dialog.tlk?
I could do this, but ...
Unless I miss my guess, it won't save space when you distribute your mod. It will only save a teeny-tiny bit of space on the user's box after your mod has been installed. I'm thinking at most 30K, tops. It just doesn't seem worth it -- no one will care or notice.
Is there some other reason you want this feature? I don't understand why it would be tempting.
I could do this, but ...
Unless I miss my guess, it won't save space when you distribute your mod. It will only save a teeny-tiny bit of space on the user's box after your mod has been installed. I'm thinking at most 30K, tops. It just doesn't seem worth it -- no one will care or notice.
Is there some other reason you want this feature? I don't understand why it would be tempting.
#3
-Guest-
-Guest-
-
- Guest
Posted 22 May 2003 - 12:42 PM
Well. Maybe the space gained isn't significant.
And the feature would be useful only for a TC.
Actually, I just don't like the ever increasing strref numbers when there are so many unused entries there.
Maybe there is a better reason, i don't know.
At the moment it is only a kind of feeling that it would be good to use them
When one adds any string in DLTCEP, the code follows this algorythm:
1. is the string already in the .tlk ? yes -> use that strref #
2. found any *!* ? yes -> use that strref #
3. append the string
And the feature would be useful only for a TC.
Actually, I just don't like the ever increasing strref numbers when there are so many unused entries there.
Maybe there is a better reason, i don't know.
At the moment it is only a kind of feeling that it would be good to use them
When one adds any string in DLTCEP, the code follows this algorythm:
1. is the string already in the .tlk ? yes -> use that strref #
2. found any *!* ? yes -> use that strref #
3. append the string
#4
Avenger_teambg
-
- Member
- 604 posts
Posted 30 May 2003 - 12:50 PM
Another strref question/idea/request: Is it possible to automatically detect the strref if it is going to be tagged or not. Then flip the tagged flag only when it needs ?
While this might seem just as useless as the previous idea, both would improve weidu's usability for me.
At the moment, if weidu compiles something with a string already existing in dialog.tlk it toggles that string's tagged flag unconditionally. This causes it to modify the .tlk when it isn't needed.
While this might seem just as useless as the previous idea, both would improve weidu's usability for me.
At the moment, if weidu compiles something with a string already existing in dialog.tlk it toggles that string's tagged flag unconditionally. This causes it to modify the .tlk when it isn't needed.
Avenger
