Template talk:4e Power

I made a small mistake

The if statements for color should have a default (if people mess up). Have them like this (untested):

{{#ifeq: {{{usage}}}|At-Will
  |{{!}}- style="color: #fdf9d3; background-color: #588d60;"
  |{{#ifeq: {{{usage}}}|Encounter
     |{{!}}- style="color: #fdf9d3; background-color: #80142E;"
     |{{#ifeq: {{{usage}}}|Daily
        |{{!}}- style="color: #fdf9d3; background-color: #3D3F3F;"
        |{{!}}- style="background-color: #FF0000;" {{!}} style="" colspan="2" {{!}} Please set "usage" to "At-Will", "Encounter", or "Daily".
         {{!}}- style="background-color: #FFFFFF;" {{!}} 
      }}
   }}
}}

This will help alert users on how to format their powers if they mess up. --Aarnott 14:31, 1 August 2008 (MDT)

The plan was to eventually tie them to a form and a property to limit what could be put there. Shouldn't really matter too much.--Taritus 15:32, 1 August 2008 (MDT)

More than Just Classes

Why the name change from "Power" to "Class Power"? What about racial, paragon path, epic destiny, and feat powers? —Sledged (talk) 15:52, 4 August 2008 (MDT)

The reason I separated this page into the templates 4e Paragon Class Power, 4e Class Feature Power, and 4e Feat Power, is that I have the breadcrumb and categories based on the parameters in the template, so they need to be included in this template, and those don't need to be added to the pages that the various templates can be included into, but I was just lazy about it. I can just throw in some #ifeq's and fix that up. —The preceding unsigned comment was added by Taritus (talk • contribs) 2008-08-05 13:17. Please sign your posts.

I'd say just use one template to format them all, and use separate wrapper templates for the breadcrumbs, categories, and author template. —Sledged (talk) 13:40, 5 August 2008 (MDT)

On a minor unrelated note, it's "paragon paths" not "paragon classes." I know it's a matter of semantics, and that they fill the same role that prestige classes did in 3.x, but they're making a point not to call them classes in 4e. Hence, path powers and path features instead of class powers and class features. —Sledged (talk) 13:49, 5 August 2008 (MDT)

I feel that each page should use Template:Author on the top, a L3 title, Template:4e Power for the game information, some flavor text next, the correct breadcrumb template, and then have categories present at the bottom. I feel that one template to include everything is just too much. --Green Dragon 16:49, 5 August 2008 (MDT)

The problem with that is when one adds a breadcrumb to a 4e Power, they should link back to their specific dpl list, so including the breadcrumb is almost necessary.--Taritus 12:43, 6 August 2008 (MDT)

Power Formatting

Off to a good start, now it just needs to be refined a bit. Unless otherwise specified, I'm using Shadow Lash (4e Power) for points of interest.

• Range bolding: only the range type (the words "Melee," "Ranged," "Close," "Area," and "Personal") is bolded (e.g. for twin strike in the range "Melee or Ranged weapon," the words "or" and "weapon" are not bolded.)
• too much space between the "hit" entry and the "cunning aura" entry
• there's extra space at the bottom of the power block.
• A power that grants a secondary attack to a different target has "primary target" instead of "target" (e.g. arc of the righteous PH 67). Powers that grant a secondary attack against the same target still use "target."
• high-/lowlighted lines of text: After the first "hit" or "effect" entry, the background color is supposed to alternate between entries. "Cunning aura" uses the same background color as the previous entry.
• Indentation: "cunning aura" should be indented, as should any powers whose secondary attacks/effects are dependent on a successful hit with the primary attack.
• "Special" entry: the "special" entry can appear in various parts of the power. It can be after the action type + range line (precision cut PH page 88), the last line (avenging flame PH page 64), or anywhere in between (radiant charge PH page 95, and nimble strike PH page 105). And though I don't see any examples of such, I imagine it's possible for a power to have more than one "special" entry.
• Instead of using consecutive #ifeq calls, use #switch instead.
• Usage and action type can be suffixed with "(Special)" (e.g. healing word PH 62 and precision cut PH 88).
• "Effect" can occur before "attack," (come and get it PH 80). 11:31, 19 August 2008 (MDT)
• Build options (e.g. "weapon," rogue tactics, pacts, and commanding presences) can occur in multiple places (armor-piercing thrust PH 79). 11:31, 19 August 2008 (MDT)

—Sledged (talk) 12:29, 5 August 2008 (MDT)

Well, the addition of the 'or' for the weapon might be more difficult that the addition of the 'primary' before target when there are multiple attacks. The parameter {{{rangemod}}} is there for the 'weapon' or the burst/blast/area range. I'm not too certain how to go about adding the 'or' without cluttering it more. It is already a bit of a CF... For the 'Cunning Aura' bit could you find me an example in the PHB? I don't think I've ever seen something like that in it... Another thing I noticed is the Fighter power 'Come and Get It' has Effect before Attack... That happens to pose a lovely problem. This entire thing is slowly turning into a complete CF. Not what my original plan was. The backgrounds are putting me at a bit of a loss for ideas. --Taritus 13:54, 5 August 2008 (MDT)

Kk, added in the switch at the beginning. Not sure if you thought it may work somewhere else. I see where the whole Cunning Aura thing is coming from now. It's the build option. That won't be a complicated thing to add in. Just two new parameters, but if you feel that multiples of them are needed just in case, that's okay too. I have no idea why there is a huge amount of extra space. I don't have anything odd that I know may be adding that, but if you can find it please MoI me about it.--Taritus 14:09, 5 August 2008 (MDT)

From the wording of all the special parameters in the PHB, it doesn't seem to matter the positioning of it, and the addition of the (Special) to either the action type of usage type seems just to alert players or DM's to the fact that it's not a normal encounter/at-will/daily or that the action type is dynamic. So, unless it bothers you so extremely that it needs to be changed to reflect the PHB exactly, I don't think there's a problem. --Taritus 14:21, 5 August 2008 (MDT)

The placement of the special entry seems to be dependent on to what it relates:

• The radiant charge (pg 95), "special" entry says "you must charge as part of this attack," and it's placed immediately after the "attack" entry.
• The rule of the order (pg 101) entry says that there's a conditional attack bonus and additional damage, and it's placed between the "attack" and "hit" entries.
• The entry is placed immediately before or after the attack entry for powers that let you perform an action before or after the attack (e.g. nimble strike [pg 105] lets you shift, frenzied skirmisher [pg 107] lets you move, slasher's mark [pg 115] lets you spend a healing surge, etc...).
• For usage and action types that are tagged with "(Special)", it appears immediately after. In fact, if you look at healing word, it's between the usage + keywords and action type + range entries.
• It seems the default placement when it doesn't relate to any specific entry is at the bottom.

I have some ideas to address most of the problems, but every solution I have breaks the form, and some of them require the site's MediaWiki to be upgraded to 1.12alpha or later and a few extension upgrades/installations. —Sledged (talk) 11:20, 6 August 2008 (MDT)

While it does matter in the PHB where the Special is located, it always mentions what it does and you still know what exactly is going on. Making it so the template puts the special entry in a specific place is almost silly and doesn't break it. I do agree that the random bit of extra space is annoying. Sometimes though it doesn't put it in, other times it puts in somewhere around 4 lines of extra space, sometimes 2. It doesn't make a whole lot of sense.--Taritus 12:41, 6 August 2008 (MDT)

If the location of "special" is not a concern, I'd say use the default and put it at the bottom. —Sledged (talk) 11:31, 19 August 2008 (MDT)

Move Action

Why does move action show up as an error when placed in the action type bit of the power? --Sam Kay 04:52, 19 August 2008 (MDT)

Because I don't have it as an available option under the action type.--Taritus 07:28, 19 August 2008 (MDT

Okeedokee. Fixed. You'll probably have to edit the page and save it again for it to show up without an error.--Taritus 07:31, 19 August 2008 (MDT)

Thanks. --Sam Kay 09:49, 19 August 2008 (MDT)

Not all attack powers have an "attack" or a "hit" thing (wall of fire, PHP 163), yet the template puts them in if you put the power down as an "attack" power. Can someone sort this, please? --Sam Kay 12:26, 20 August 2008 (MDT)

Mrh... Fixed.--Taritus 13:42, 20 August 2008 (MDT)

Thanks. --Sam Kay 04:51, 21 August 2008 (MDT)

Also, if there are no keywords, "✦ {{{keyword1}}}" turns up... Can someone sort this, please? I've tried, but I can't sort it. --Sam Kay 11:57, 23 August 2008 (MDT)

An example of this please? I'm not seeing it. If you remove all the keywords from the example on this page there's no trouble...--Taritus 12:01, 23 August 2008 (MDT)

Here. Also, "Immediate Interrupt" seems to be taking up two lines, and the "hit" bit seems to be too large. --Sam Kay 12:03, 23 August 2008 (MDT)

It was using an antiquated template.--Taritus 12:07, 23 August 2008 (MDT)

How do I make it a racial power? --Sam Kay 12:08, 23 August 2008 (MDT)

The owner parameter. |owner determines what the power belongs to whether it's a Base Class, Paragon Class, Epic Destiny, Feat, or a Race. Without the parameter it assumes it's a Base Class Power.--Taritus 12:15, 23 August 2008 (MDT)

←Reverted indentation to one colon

Oh. Thanks! --Sam Kay 12:36, 23 August 2008 (MDT)

Also some powers have a "hit" but no "attack", but the template prevents this (see cloudkill, PHB pg 166). Can someone sort this, please? --Sam Kay 07:36, 26 August 2008 (MDT)

Errata'd. http://www.wizards.com/dnd/files/UpdatePH.pdf

Strangeness

I've been attempting small changes to see what the hell is wrong with the usage line in the power template, but everything I've tried has so far been in vain.--Taritus 13:40, 22 July 2009 (MDT)

Oh, god. Never mind then. There was a single space in the padding parameter of the fullrow template.

Bold Keywords Error

It appears that the template is no longer automatically having keywords appear in bold font. --Dracomortis 20:44, 19 August 2009 (MDT)

Fixed. --Green Dragon 22:16, 28 January 2011 (MST)

Racial utility powers

Can the template be adapted to handle Racial Utility powers like those in Heroes of the Feywild? If you set "owner" to the race, then the level isn't printed. The level is printed if I put the race in "class", but then it leaves a breadcrumb, which looks messy when you're listing them on the race's page. Marasmusine 06:18, 24 December 2011 (MST)

Eventually breadcrumbs may be removed from this template since, like you are saying, they make problems. Someone just needs the initiative. --Green Dragon 12:34, 9 January 2012 (MST)

Trigger

Please make the Trigger field appear when the actiontype is Free Action. Marasmusine 11:16, 31 December 2011 (MST)

I added it. Should that show up all the time (like it is now) or should I try to make it show up only when data is entered in that parameter? --Green Dragon 12:34, 9 January 2012 (MST)

Test Power	Racial Power
When you are hurt, you vomit photons out of your ears and nose.
Encounter ✦ Radiant
Free Action	Close Burst 1
Target: All creatures in burst
Effect: All targets take 5 radiant damage.

That's great, thanks.

As far as I know, all Free Actions should have some kind of trigger, so yes, leave it like that. Marasmusine 13:59, 9 January 2012 (MST)

No problem. Sounds good. --Green Dragon 18:14, 9 January 2012 (MST)

Is this true? I thought not all Free Actions require a trigger (cleric I think)?--Yanied (talk) 21:19, 28 January 2021 (MST)

Failing category logic

This template certainly looks like it's meant to automatically do this, but articles like Empower_Orb_(4e_Power) don't seem to get automatic [[Category:4e Power]] [[Category:4e At-Will Power]] etc. My lack of familiarity with 4e and this logic maze template makes me feel not well suited, so I could maybe work out how that works, but does anybody have an idea how to fix this? As it seems to be rather prevalent. --SgtLion (talk) 14:30, 14 May 2015 (MDT)

That happens when the |owner=Paragon Class parameter exists. This parameter is not defined by this template, since the correct parameter is |owner=Class. It would be best to fix the powers with this error, but I will see if I can make the template respond to this usage too.

Its partially better now. Now the class powers without any |owner= parameter still have this problem. I don't know if this can be so easily resolved since some classes have |owner=Feature , others |owner=Class Feature , and even others nothing at all. If they are all classes I guess that adding the categories anyway would not be a problem, or is there some reason that I am not seeing that this cannot be the case? --Green Dragon (talk) 04:08, 17 May 2015 (MDT)