User talk:The Emmisary/Sandbox

Comment on Format
Hello. I was bored out my fucking mind so I decided to make this rough list in response to the Life Sheath dispute. I would like comments on if it should even exist, how many skills should be added, and are the categories too broad/specific. DO NOTE THAT THIS IS A LONGER VERSION THAT THE ONE CURRENTLY EXISTING.--The Emmisary 21:34, 23 September 2010 (UTC)
 * Skill quick reference and List of skills by related subject. It already exists in two forms. The first list is part of the skill guideline at the moment. I don't believe it is useful, but it is clearly wanted as it comes up again and again. I don't believe it is useful because it can only be used to theorycraft new builds and anyone who is skilled enough to do that should already know more or less all the various skill interplays. Obviously these lists are too large to put directly on the skill pages themselves, which is why at the moment links are placed on skill pages to the relevant sections. It simply hasn't been widely implemented because no one seems to want to take the time. Note that some skills do end up in multiple categories because they do multiple things. I also don't see how it is longer, it is simply complete for warrior skills. It is in fact shorter than either list. Misery  21:44, 23 September 2010 (UTC)
 * ...Never saw the second list before. I guess my work was for nothing. Thanks I will implement the other one then. However does anybody object to a Functional Usage list?--The Emmisary 21:56, 23 September 2010 (UTC)
 * I think that the functional usage list is a necessary counterpoint. &mdash;  Raine Valen  [[Image:User_Raine_R.gif|19px]]  21:58, 23 Sep 2010 (UTC)


 * The "complete" list would indeed be massive, as there will be a section for everything that a skill can possibly do, and each section will have a line for each skill that does that thing. I think, in the end, it'll have to be split up.
 * Other than that, though, looks good. I'd add a short note to each skill elaborating on it (like the SQR "skills that disable skills section), though.  &mdash;  Raine Valen  [[Image:User_Raine_R.gif|19px]]  21:58, 23 Sep 2010 (UTC)
 * A functional one would be considerably shorter since a lot of skills are not widely used.--The Emmisary 22:02, 23 September 2010 (UTC)

A couple of categories
Are lacking skills; Crushing Blow and Heavy Blow should be damage skills, for example. :> &mdash;  Raine Valen    2:12, 25 Sep 2010 (UTC)
 * Quivering was just a mistake but the others are already under knockdown. I didn't put them in damage because if I did almost every other warrior skill would also be under it. This is still a mechanical list after all.--The Emmisary 02:14, 25 September 2010 (UTC)
 * I think that mechanical lists should be inclusive, no?
 * Also, skills being in multiple categories isn't a problem, so long as they fit into all of those categories. &mdash;  Raine Valen  [[Image:User_Raine_R.gif|19px]]  3:02, 25 Sep 2010 (UTC)
 * Perhaps a grid list is in order? Divide it into professions, and have it in a sortable list setup. Have every skill on one side in alphabetical order, then have its attribute followed by the empty boxes. Place all the categories on the top and bottom. Finally put check marks along the skill's line to determine what categories they fall under. Using an overflow=auto function could let you have a tall table placed within a preset-height box. Putting icons in the category row, then have tooltips display the category name would let you have a lot of categories without stretching the page. Use an icon for the check mark to allow for the tooltip to tell if, for example, a knockdown skill is conditional instead of assured. Once filled in, a sortability should be availiable for each column. If not, a hidden sort variable could be used. Just use ... and put a number into the ... section before the icon. The last column is the "hide/show" button column to prevent it messing up a category header. It has a rowspan variable in the first skill's row to keep that entire column blank. Make sure that rowspan number is equal to the rows you have in the list.


 * --Neithan Diniem User Neithan Diniem Sig.png]] 20:51, 28 September 2010 (UTC)
 * oooooo that looks fancy. I'll try to do it.--The Emmisary 22:34, 28 September 2010 (UTC)
 * Hehe, glad I could help ^_^;. I tried to make a horizontally scrollable version, allowing for full category names and the like, but it wouldn't cooperate. Once I get it to work right I could post it again. The icons and all was the best compromise I could come up with. I could try to template it for ya, make it easy and all. It would probably be similar to the Wanted Bounty table I made. Ill see what I can do.--Neithan Diniem User Neithan Diniem Sig.png]] 04:28, 29 September 2010 (UTC)
 * Take a look here, Ive made alot of progress on it.--Neithan Diniem User Neithan Diniem Sig.png]] 03:41, 30 September 2010 (UTC)

Completion
I completed that template now, and its all ready for you to go at it with your project. The page for the template is here, and has all usage notes ready for you. Now, the template can support all 10 professions, an infinite number of skills (within reason, all the game's skills should be easily supportable), and 20 categories total. There are functions to allow for hiding unused categories, changing the size of the template, recoloring everything about the template, and sub-categorizing skills within the existing categories. The sections are sortable; skill icons alphabetically, attributes alphabetically, and categories by categorization. Each profession's bar can also be hidden or expanded upon start up, your choice. All in all, this template is ready for use. Use it if you will, either way it helped me learn even more things about coding on the wiki. If you want/need help with the template or project, or want something about the template changed, just give the word. Im thinking about adding a "monster's skill" section, as well as dividing the profession tables to be separate (to allow for sub paging the sections) once you get further along, sub-paging them would be a great asset.--Neithan Diniem 20:34, 30 September 2010 (UTC)