WB in 3 core custom VS Name embedded major

[MdotA]

I want some advice on which gets the most out of wanted black. I feel WB in a 3 core custom loses a lot of scripting when you factor that it is 15 minutes long and has 7 modules in that custom, along with the 3 cores.

I’ve had more blatant results from the standard store version than I did with my custom. I was ill advised to add other aura modules in that though.

So I was thinking of making a WB name embedded sub. Then creating a new 2 core custom and stacking it with that, to get the most out of WB.

Does a Name embedded major title lose any scripting when compared to the standard version, since it has an additional module of choice?

[gdbdboy]

Main Disc. Thread - Name Embedded Major Titles (Testing Period)

As @RagnarLothbrok pointed out, it’s less dense, more focused and is best used for those who want to commit to a tighter stack (or single title). Except instead of a CORE (which has some of the support scripting removed in order to make it fit the custom process), this is the full sub, exactly as it would be as if you were just running the major title, except customized. Even though the UI may say “Core” (since it’s just pulling from the product database), Q-Engineer will know to use the “Maj…