No, I wasn't asking if you could carry edits from 3.x to 4.x; obviously that would be impossible. I was just wondering about 4.x upgrades. When I went from 4.08 to 4.1.2 it showed me the templates that it could and couldn't merge code and as I recall that's what this mod was supposed to do, but never really did it very well.

Nah, what this mod does is allow you to create changes to your templates without going into each style and making the changes manually. saving the changes when you upgrade and continuing to apply them. It allows you to test each of the mods you make to the templates to see if they work, and continues to apply them after upgrade without even one change. It does it wonderfully.

I was able to upgrade in 3.x version after version without all the template revert, change. When making changes you simply go to the Master Template this mod adds, you go to the template you are going to change, you add the code it looks for select the "add after" "add before" "delete" "replace" selection and put in the changed code below.

This then goes into all the styles, and makes the changes on the fly without even one iota of speed degradation. This keeps your styles templates clean and unchanged entirely, making upgrades within the same vbulletin platform very easy.

I'm not talking about style migration from 3.x to 4.x. This functionality does not exist in 4.x any more than it has in any previous versions of vbulletin.

This mod is definitely worth it, especially if you add mods often.

Clearly you're wrong there. They've made big changes to upgrades in vb4. This last one told me exactly which templates it merged with my custom code, which were successful merges and which weren't, and gave me the option to edit and compare the files side by side. A huge change from vb3.

All of which may be off topic for this particular thread, except that more than one person has said they don't want to upgrade to vb4 until this functionality is included. From what I saw with the 4.1.2 upgrade, it is included.

If this did what you are saying then it would be included. It doesn't. This simply creates an overlay system that allows the changes to be made without direct changes to templates making merges and comparisons unnecessary.

Believe me, using both 4.1.2 without the mod and with it is miles different (I have done both now, with my test upgrade on a test board). This is better.

1. This allows you to make changes in a Master Template that applies to every style without changing the actual templates.
2. These changes will continue to work unless the template changes so your search string no longer exists. In upgrades there will be no template matches to change, the ones that don't work simply will not apply.
3. Those that do no longer work are easy to find by simply running a test against them, then you can view and find a different search string to apply the "add before" or "add after" etc. to...

While changes to 4.x were large, it certainly did not add the functionality of this mod. I am glad it still worked with my RL upgraded version.

I am not "clearly wrong", you are simply incorrect as to what this mod actually does. However, if you believe that you get the same functionality then I have no dog in this fight. I felt crippled without it on the test site and I'm very glad it is working now. It most definitely wasn't the same thing, nor did it give me the same capabilities with just 4.1.2 without the mod.

Did they fix the bug in the newest release? (Please)...

No, that bug has not been fixed yet. Please vote for it in the tracker:
http://tracker.vbulletin.com/browse/VBIV-7378

Or directly by clicking this link (you'll need to login at vb.com):
VOTE!

Is this still usable in 4.1.3 then?

With minor limitations because of the bug I linked: Yes. I used it since vB4 alpha 1 and it's basic functionality is intact. I wouldn't want to modify vB4 without it.

Isn't that bug also in stock vb ? I get it sometimes where it goes to a white page and says something about child nodes when I do something wrong in a template edit (like no ending if statement for instance).

Jap, of course, that's a bug in sstock vB that needs to be fixed. The bug in vB affects TMS and has been reported ages ago. Sadly, 1300+ installations (counting those registered on vBG.org, too) have not been enough to varrant a little fix until now...