Talk:Essentials Class Preload

Only Option

Using this preload as the default class preload would make users more aware of the powers attached to the class. I am of the opinion that we should make this preload the only option (and reformat all the current classes to use this template). Of course this would make 4e Powers much different than it currently is, but I feel that just applying a category link of come sort is appropriate for the powers, as well as a list of "add-on" powers. Thoughts? --Green Dragon (talk) 04:43, 29 September 2013 (MDT)

There are some things I need to look at. Firstly, some essentials classes have the paragon path and epic destiny "built in", whilst others specify "at this level you take the power from your paragon path", so the preload needs to support both options. Secondly, I can look at the possibility of splitting the three tiers off onto their own sub-pages. Thirdly, we can keep the powers on their own pages and transclude them into the main page, but some fiddling about is needed so we don't get breadcrumbs everwhere. The breadcrumb can be noincluded, but its currently included in the power template, and I don't know how to include a noinclude tag. Or the breadcrumb could be moved to the power preload, but then every single existing power would need the breadcrumb adding. If that sounds confusing, it is.

At some point I will try converting an current homebrew class to the format to see what the workload is like. Marasmusine (talk) 08:52, 11 October 2013 (MDT)

So, an issue is paragon path implementation into this preload. Specifically how they are integrated into certain classes with regard to the preload.

D&D Wiki is on the long-term support version of MediaWiki. Although it's in testing on MWF's wiki's, likely the next version will have Lua support. Lua support could help us with the power's breadcrumbs.

This brings me to the second issue here. Yes, the power's breadcrumbs are not pleasant to transclude or they require a major overhaul for this preload's implementation. We can wait for Lua support, though, and see if that can clear up this problem.

If Lua support can deal with this issue, because it is derived from {{4e Power}}'s use of ParserFunctions, then implementation will be much smoother. I feel that we should wait and see, unless you know of any solutions to these issues. --Green Dragon (talk) 08:17, 20 October 2013 (MDT)