Guild Wars 2 Wiki talk:Semantic MediaWiki/Skills

From Guild Wars 2 Wiki
Jump to navigationJump to search

The Subproperty of seems like a really good idea for Has combo effect and have Has combo field and Has combo finisher.--Relyk ~ talk > 13:51, 2 January 2013 (UTC)

Eh, I'm still not sure exactly how I'm going to handle skill facts, it may not be anything like that at all. Anyway, those subproperties aren't necessary, since we can get the same result with a "like" query: [[Has combo effect::~* field]] [[Has combo effect::~* finisher]]. (The values shown on the page are wrong, as this would be a page property, not a string, and the values would be the full page name like Dark field; can't remember why I wrote them this way.) —Dr Ishmael User Dr ishmael Diablo the chicken.png 14:03, 2 January 2013 (UTC)
No fun lol. Not appending field and finisher seemed really weird to do.--Relyk ~ talk > 14:27, 2 January 2013 (UTC)

Dual wield skills[edit]

Is for weapon needs to be multi-parametered for Has skill type::Dual wield I guess.--Relyk ~ talk > 19:54, 15 January 2013 (UTC)

Eh, but then you can't know which is the main-hand and which the off-hand weapon. Instead, make a new property Requires offhand weapon for it, with values dagger, pistol, and none. —Dr Ishmael User Dr ishmael Diablo the chicken.png 20:25, 15 January 2013 (UTC)
requires offhand weapon::none is hilarious.--Relyk ~ talk > 02:21, 11 March 2013 (UTC)

is for pet[edit]

The pet family will be set on the prt page. Its the same as setting a pet family skill property.--Relyk ~ talk > 02:45, 11 March 2013 (UTC)

Each family shares 3 skills, but every pet has 1 unique skill. That's why the different properties. —Dr Ishmael User Dr ishmael Diablo the chicken.png 02:50, 11 March 2013 (UTC)

Sorry in advance for this stream of thought. A query to output the 4 skills for a pet gets a little complicated with the separate properties. It would use the pet name as the parameter:

{{#vardefine:family|{{#show:{{{1|{{PAGENAME}}}}}|?Has pet family|link=none}}}} <!-- pet family -->
{{#vardefine:pet_skill|{{#ask:[[Is for pet::{{{1|}}}]]|link=none}}}}           <!-- Unique pet skill -->

{{pet skill header}}
{{#ask:[[Has skill context::Pet]][[Is for pet family::{{#var:family}}]]
|?Has recharge time
|?Has game description
|link=none
|format = pet skill row
}}
{{pet skill row|{{#var:pet_skill}}}}
{{pet skill footer}}

{{Pet skills}} seems to be handling the skills for a pet instead of NPC infobox setting the family and skill infobox setting skill type... I'm not sure about the query for the unique pet skill because it's a 1 to 1 relationship. Have it where setting the Is for pet property will also set the Is for pet family as well based on a query to the pet page for its family and the output template would simply check if the skill has the Is for pet property to know where to display the unique skill.

{{#vardefine:family|{{#show:{{{1|{{PAGENAME}}}}}|?Has pet family|link=none}}}} <!-- pet family -->

{{pet skill header}}
{{#ask:[[Has skill context::Pet]][[Is for pet family::{{#var:family}}]]
|?Has recharge time
|?Has game description
|?Is for pet
|userparam={{{1|}}} <!-- Pet name -->
|link=none
|format = pet skill row
}}
{{pet skill footer}}
{{#ifeq:{{{#userparam}}}|{{{3}}}|{{{3}}}<!--Unique skill-->|{{{1}}}<!--Family skill-->}}

At least, that's the behavior I want when I'm making that query. The template would make sure that unique pet skills also get the correct pet family property as this relationship is also 1 to 1, unique pet skills don't cross pet families. I'm happy if queries starting from pet families would use the exact same query but format it in terms of family instead of individual pets.

{{pet skill header}}
{{#ask:[[Has skill context::Pet]][[Is for pet family::{{{1|}}}]]
|?Has recharge time
|?Has game description
|?Is for pet
|link=none
|format = pet family skill row
}}
{{pet skill footer}}

yeah? :P--Relyk ~ talk > 04:54, 11 March 2013 (UTC)

I always thought the pet skills template (and its predecessors, e.g. "Bear/skills") was kind of a dumb implementation. In any case, fully automating that list is going to be a lot more complicated than this, because you also have to account for underwater replacements of the unique skills. I don't see why we would want to fully automate those lists anyway, since the skill names are very unlikely to change. —Dr Ishmael User Dr ishmael Diablo the chicken.png 15:47, 11 March 2013 (UTC)

Revival[edit]

Like most stuff stuck in a description, skills that revive allies aren't explicit effects. We can have the skill infobox effects set a silent property and give a parameter. There are some other effects that we need a similar approach.--Relyk ~ talk < 04:07, 18 June 2013 (UTC)

Two suggested properties[edit]

Per Template talk:Skill list dpl, I've suggested two new properties.

  1. Is replaced underwater by
  2. Is underwater replacement for

Comments on that template page if you want to suggest a better name (or approve it) -Chieftain AlexUser Chieftain Alex sig.png 13:35, 3 November 2013 (UTC)

It looks fine for me. – Valento msg 11:13, 6 February 2015 (UTC)

Skill facts and similar properties[edit]

Just a heads-up, with skill facts there are now three properties which are also part of facts: Has combo effect, Has limited projectile combo, and Breaks stun. Not sure how these are used, just thought I'd point them out. – Valento msg 11:10, 6 February 2015 (UTC)