User talk:Chieftain Alex/sandbox4

Problem

{{#ask: [[Is for weapon::Sword]][[Category:Warrior skills]][[Has game context::Skill]]
 | ?Has game description
 | ?Has recharge time
 | ?Has activation time
 | ?Has skill type
 | ?Has skill context
 | ?Is for weapon
 | ?Has initiative cost
 | ?Has chain sequence
 | ?Has underwater replacement
 | ?Has skill slot number
 | ?Has skill point cost
 | link = none
 | limit = 250
}}

{{#ask: [[Is for weapon::Sword]][[Category:Warrior skills]][[Has game context::Skill]]
 | ?Has game description
 | ?Has recharge time
 | ?Has activation time
 | ?Has skill type
 | ?Is offhand skill
 | ?Is for weapon
 | ?Has initiative cost
 | ?Has chain sequence
 | ?Has underwater replacement
 | ?Has skill slot number
 | ?Has skill point cost
 | link = none
 | limit = 250
 | format = template
 | template = User:Chieftain Alex/sandbox4
}}

{| class="white skills table"
{{weapon skill table header}}
|- class="warrior"
! colspan="6" |
==== {{w}} [[Warrior]]====
{{weapon skill table row|chain=burst|Flurry}}
{{weapon skill table row|Sever Artery}}
{{weapon skill table row|chain=chain|Gash}}
{{weapon skill table row|chain=chain|Hamstring}}
{{weapon skill table row|Savage Leap}}
{{weapon skill table row|Final Thrust|class=line}}
{{weapon skill table row|Impale (warrior sword skill)}}
{{weapon skill table row|chain=chain|Rip}}
{{weapon skill table row|Riposte}}
{{weapon skill table row|chain=chain|Adrenaline Rush (sword skill)}}
|}

* {{#var:dwoffhand-Riposte|not working for offhand }} - {{#var:dwoffhand-Riposte|not working for offhand }}
* {{#var:weapon-Riposte|not working}} - {{#var:weapon-Riposte|not working}}

Comment

I'm using the line

{{#vardefine:dwoffhand-{{{1}}}|{{#arraymap: {{{6|}}} |,|@@@|{{#ifeq: @@@ | Offhand | {{{7|}}} }} |}} }}

to try and set the dwoffhand variable to be equal to the weapon (input #7) it needs if the skill context property (input #6) contains the value "Offhand". I'm not having much success here. any ideas guys? -Chieftain Alex 14:43, 10 November 2013 (UTC)

I'm not sure you understand what that variable is for. It should only be set for thief dual wield skills, so we can display the name of the offhand weapon within the table for the mainhand weapon. You should be using Property:Requires offhand to set it. —Dr Ishmael 16:02, 10 November 2013 (UTC)

ok then, guess I got confused. -Chieftain Alex 16:49, 10 November 2013 (UTC)

Breaking Stuff

Unique has a broken link "File:Topaz Gold Earring.png, File:Third-Place Medal.png" from "Topaz Gold Earring, Third-Place Medal" which currently is appearing on that page and links back to here. - Do_odleplex 00:00, 6 December 2016 (UTC)

Thanks Doodle. Please feel free to blank any sandbox of mine that causes an issue, ever. -Chieftain Alex 00:37, 6 December 2016 (UTC)

Roger. Unrelated, you have a busted link on your User:Chieftain Alex/Templates/Miniatures 3/miniature template page. I tried to fix, but had no luck/and or got distracted. - Do_odleplex 00:44, 6 December 2016 (UTC)

Historical items with no images

Okay, of the items you listed, only three should be fine; the short bow, the Whisper's mantle, and the clompers. We will not gain access to images of any kind of beta or NPC items. All items have had to be obtainable on live at some point to be eligible. If anyone else reading this can think of additional historical items not available through the wardrobe which need images, shout. talk 11:42, 8 March 2017 (UTC)

No access to beta heart of thorns items is lame. However, thank you for checking. -149.254.235.207 16:17, 8 March 2017 (UTC)

Agreed, but well, what can you do. Guess we'll have to wait till they go live someday. talk 16:50, 8 March 2017 (UTC)

Should lore locations be setting semantic property "Located in"?

Hrm. They really do make what should be an easy query more tricksy. I was looking at Tyria earlier and it struck me odd that it didn't link down to zone granularity.

Also Forsaken Thicket and all the locations inside it are all marked Raids... hrm. -Chieftain Alex 22:36, 3 December 2020 (UTC)

What about creating a new property Geographically located in? This property can be set on lore pages, e.g. inaccessible lore landmark Blazeridge Gap or geographical regions Blazeridge Mountains, and would be specified via the location infobox parameter "geographically within" (or "geo within", whatever...) but it takes the "within" value on default if the mechanical region matches the geographical region.

This would allow us two split two distinct concepts (probably introduce the location type "Geographical region" to clearly diffentiate it from the location type "Region") without getting wierd interactions as we currently do (e.g. recently location infoboxes had been added to geographical regions, then reverted..., overall it's not clearly defined and pretty vague). Hence we would be able to create two different location trees, first the mechanical location tree using the property Located in (note that this would not contain all locations, e.g. inaccessible lore regions won't have the property "Located in") and second the geographical location tree using the property Geographically located in (this would contain all location pages). Due to inheriting the mechanical region if no geographical region is specified and stopping at zone or area level (e.g. not applying it to NPCs, objects, etc...) it shouldn't be too much work adding those. --Tolkyria (talk) 11:40, 4 December 2020 (UTC)