User talk:FaceLicker329
Hello Face!
I made a template from your unqiue item sheet, to speed up inserting and updating data. Actually placed at the german pages, but I expect you can access it also as 'template:unique' at the en.* part (that how it works also the other way around for me) It should be self-explaining, even for having the description in german; but feel free to ask if there are things unclear. To have a look, I already put the first amulet in: Araku Tiki --Mr.Cee (talk) 09:48, 13 August 2012 (UTC)
- add: didnt work with the different data on non-item uniques (gem, map) but can easily be adapted if we would.
- add2: found a solution to also cover the different requirements into a (hopefully) working visual, 2nd example: Astramentus --Mr.Cee (talk) 11:51, 13 August 2012 (UTC)
- I think we'd definitely be better off modifying the item template so every item looks the same. It will make it much easier to update everything at once. I'll have a play with the template when I'm not at work and see what I can come up with. It's in need of a restructuring either way. Iamacyborg (talk) 13:08, 13 August 2012 (UTC)
- I just took a look into other templates, to see how far I could get it working - the used structure just reminds me on the templates of the areas and quests. Just as a test and suggestion how we could avoid a lot redunant code on multiple pages. Only 'played around' with my little practice on such things! Feel free to reassemble it in any useful way. --Mr.Cee (talk) 13:32, 13 August 2012 (UTC)
- Nice work, Mr.Cee! That's awesome, but as Iamacyborg said, we'd be better off having the item template look the same for every item. My suggestion would be to create one template and include every possible line option. So basically, it's just one long list and you include what is necessary for each item, have every option available from 'Physical Damage' to 'Energy Shield' to 'Req Str:' to 'FlavorText' and for the options that aren't applicable make sure they are hidden. Oh, one thing I noticed is that the http://en.pathofexilewiki.com/wiki/Template:Item is missing 'Bonus Accuracy' for weapons. Mr.Cee, for the template you made.. the 'desc' line should be renamed to 'Implicit' because that's exactly what it is, the implicit mod. 'Desc' is actually the name for the blue-green text you see on the Vaults of Atziri map and on Currency items. Also, you need 9 explicit mod lines. An item can only have 6 explicit mods, but those mods can take up to 9 lines. Take a look at Charan's Tipua Kaikohuru to see what I mean. And last but not least, change 'slogan' to 'flavor' only for the sake of consistancy. GGG's website use the term 'flavourText' and that's what the users also know it as.--FaceLicker (talk) 14:51, 13 August 2012 (UTC)
- Yeah of course, the variable names are just quick set from my look on the first amulet, then softly adapted to the second one. Also had the idea in mind to add more lines to each section and to sort them out by more #if-statements. But at first I was so glad to get it working at all, needed some tries and research to find a way to get rid of the double parting line if there are no requirements ^^. Have another thing about the template:item - the use of attacks per second is a bit uncommon, 'attack time' should be the term the users are more familiar with, since thats what the game shows. --Mr.Cee (talk) 18:51, 13 August 2012 (UTC)
- Just created the talk page for the template. What are the exact parameters we're likely to need? I suspect FaceLicker will know this much better than me as I've not paid too much attention to the items for a little while. Iamacyborg (talk) 20:14, 13 August 2012 (UTC)
- Yeah of course, the variable names are just quick set from my look on the first amulet, then softly adapted to the second one. Also had the idea in mind to add more lines to each section and to sort them out by more #if-statements. But at first I was so glad to get it working at all, needed some tries and research to find a way to get rid of the double parting line if there are no requirements ^^. Have another thing about the template:item - the use of attacks per second is a bit uncommon, 'attack time' should be the term the users are more familiar with, since thats what the game shows. --Mr.Cee (talk) 18:51, 13 August 2012 (UTC)
- Nice work, Mr.Cee! That's awesome, but as Iamacyborg said, we'd be better off having the item template look the same for every item. My suggestion would be to create one template and include every possible line option. So basically, it's just one long list and you include what is necessary for each item, have every option available from 'Physical Damage' to 'Energy Shield' to 'Req Str:' to 'FlavorText' and for the options that aren't applicable make sure they are hidden. Oh, one thing I noticed is that the http://en.pathofexilewiki.com/wiki/Template:Item is missing 'Bonus Accuracy' for weapons. Mr.Cee, for the template you made.. the 'desc' line should be renamed to 'Implicit' because that's exactly what it is, the implicit mod. 'Desc' is actually the name for the blue-green text you see on the Vaults of Atziri map and on Currency items. Also, you need 9 explicit mod lines. An item can only have 6 explicit mods, but those mods can take up to 9 lines. Take a look at Charan's Tipua Kaikohuru to see what I mean. And last but not least, change 'slogan' to 'flavor' only for the sake of consistancy. GGG's website use the term 'flavourText' and that's what the users also know it as.--FaceLicker (talk) 14:51, 13 August 2012 (UTC)
- I just took a look into other templates, to see how far I could get it working - the used structure just reminds me on the templates of the areas and quests. Just as a test and suggestion how we could avoid a lot redunant code on multiple pages. Only 'played around' with my little practice on such things! Feel free to reassemble it in any useful way. --Mr.Cee (talk) 13:32, 13 August 2012 (UTC)
- I think we'd definitely be better off modifying the item template so every item looks the same. It will make it much easier to update everything at once. I'll have a play with the template when I'm not at work and see what I can come up with. It's in need of a restructuring either way. Iamacyborg (talk) 13:08, 13 August 2012 (UTC)
Another template for item display
Hi, I saw the Unique_Swords page you created, and thought you might be interested in this template: Template:Hover. I've only just created it in the last couple of days, so if you're interested in using it and have any suggestions for better usability or requests for functionality let me know and I'll see what I can do. — Malice (talk) 16:20, 11 February 2013 (UTC)
- Yeah about the font thing, I actually designed that template locally on my machine using that font. I think I have the font installed too, but on here it is not rendering properly - crossbars on A's and E's are missing for example, and it just doesn't look right.
- About Template:HoverRequires, it does not currently have the ability for blue text but it is easily added, I'll get on that now. Is there anything else you can think of that is needed? — Malice (talk) 17:21, 11 February 2013 (UTC)
- To center it in there you can add
style=margin-left:auto;margin-right:auto;into the hover template. I did this to the bottom one as an example for you. — Malice (talk) 20:03, 11 February 2013 (UTC) - Or you could say style=width:100%; and it will expand to fill the containing box. — Malice (talk) 20:06, 11 February 2013 (UTC)
- To center it in there you can add
Unique Item Pages
I think that was a bad decision, having one page for all the items was extremely helpful. No reason we can't have both. -- Nickoladze (talk) 15:14, 16 February 2013 (UTC)
- I strongly agree. Perhaps transclude the sub-pages into the main page to eliminate duplication. -- Nightblade (talk) 01:24, 17 February 2013 (UTC)
- Ok, so there is a page with all the sub-pages on it. Called something different. Not confusing at all! -- Nightblade (talk) 01:30, 17 February 2013 (UTC)
- It's actually fine to have both pages—Unique Items for information about uniques in general and Full Unique Index for a list of all uniques—although we ought to standardize page naming a bit. To discuss this further, use the Community Portal. —Vinifera7 (talk) 04:28, 17 February 2013 (UTC)
Hey just wondering what sort of protocol we are using for the base stat values on unique items. If an item can roll within a range e.g. +(x-y)% Energy Shield, should we use the end results of those boosted values in the info box and list pages, or should we use the base value before multipliers are applied? --Spud (talk) 12:15, 13 March 2013 (UTC)
Item Images
I like the double resolution item images. They look really nice. The only consideration is making all of the item images consistent throughout the wiki. Basically, it's fine to use the double-res images as long as we do it on all of the items. —Vinifera7 (talk) 23:57, 9 April 2013 (UTC)
- That's the plan, Stan :). We might need to scale down the resolution for the table rows, some of the items are rather large, but that's easily fixed with the template. --FaceLicker (talk) 23:59, 9 April 2013 (UTC)
- Oh, and I know it looks weird right now with the Unique items, but that's because the wiki has caching issues. After a few hours/days, all the images will normalize. --FaceLicker (talk) 00:01, 10 April 2013 (UTC)
Searing Bond
Being as I was the one who added the column in in the first place, I figured I had the right to remove it as the skill had information up to level 15 and the duration had not yet changed. --Tmblake09 (talk) 22:27, 12 April 2013 (UTC)
- FaceLicker's reaction might have been a bit harsh, but he does have a point. I think we can agree to leave in the totem duration column until it can be determined that the duration remains unchanged as the gem levels. —Vinifera7 (talk) 05:35, 13 April 2013 (UTC)
Hmm
In case you didn't know, br tags don't need closed with a slash. The expected form for HTML5 is <br>, though <br /> is valid. In HTML4 <br /> is weird but mostly ignored. I tried serving a website with the correct XHTML mime-type for a while but gave up, lol -AnnanFay (talk) 21:34, 28 April 2013 (UTC)
- I do the same thing because I got used to writing strict XHTML for years. For HTML5,
<br>is sufficient, but<br/>is also fine. —Vinifera7 (talk) 21:40, 28 April 2013 (UTC)
- I was not aware. For some reason I thought void elements always had to have a closing tag to validate correctly.--FaceLicker (talk) 04:09, 29 April 2013 (UTC)