*Necro* - sorry, but this was a question I had, and I think future nostalgia players of Warband (etc) might benefit from what I've found so far:
You can't add this TweakMB functionality to modern patches without introducing a ton of bugs because it just takes its old Native 1.143
(I've realised that the archived version linked at the end of the TweakMB release thread is more current than the one on nexusmods - thought I was being clever...But anyway, while the newer version is better synchronised for some functionality, the quest menu configurations still contain wayyy too many outdated references)
conversation.txt file and dumps it into/overwrites your existing one (Native live on Steam is 1.174), and then adds about 50 extra lines of new conversation data in the bottom.
If you have the modified conversation file with the quest selection menu and you want to find where the newly added quest menu lines start, the following text are the first non-vanilla lines:
But obviously, just the information dumped on the bottom by itself probably won't overwrite the vanilla responses when you ask for a quest. So you'd also have to track down any reference IDs mentioned below the vanilla text, track them down in the vanilla text as reconfigured by TweakMB and see how they're connected, and identify which ones are different from the original vanilla reference IDs, if you want to do the same thing to your own menu - whether that's a mod, or a patched Native game.
Just to be clear, it *does* "work" just to take the complete TweakMB database conversation config file and just run the game with it. It "works" insofar as that you get to see the menu when you talk to an NPC that has quests. But the hybrid of version 1.158 dialogue, code and references introduces lots of bugs in conversations, and chances are it ruins the functionality of quests in the backend, as well.
You could use something like the ComparePlus plugin in Notepad++ to compare all the differences between the unedited config file with the new file, and find the differences associated with getting the selection menu to work (as opposed to just being unrelated version differences - of which there are a ton.) If you isolate those and convert all the changed references to align with the current patch, you might be able to figure out how the menu works and add it.
I'll update if I figure out the relevant reference IDs to get the menu working cleanly on my patch; you'd still have to track down and change the data yourself if you want it to work in a mod module.
