Welcome to the DFO World Wiki. With many major updates since the release of DFO, many items are missing. Visit Item Database Project to learn more.
Please remember to click "show preview" before saving the page.
Thanks for the updated logo snafuPop!

Talk:The Great Skill Metastasis Project

From DFO World Wiki
Revision as of 19:07, 23 May 2015 by Everspace (talk | contribs) (2bits)
Jump to: navigation, search

Many of the skill tables don't have either the cast time or cool time (cooldown) on them. Are we going to include this information in the table or on the page? Imho, I think they should be put in the table... but any other say on the matter? - Blakdoxaduo (talk) 19:40, 23 May 2015 (PDT)

Hard to say really. User Talk:Dfoplayer#Consistency. I would prefer in "attributes" but if the cooldown/cast time changes, it should go into the table. But then for consistency reasons, we should keep everything in the table for all skills. --Dfoplayer (talk) 19:48, 23 May 2015 (PDT)
Thanks for the link I was looking for that discussion and glanced over your page too fast! On another quick note, are we switching to the new skill page layout now and where can I find an example/guide to go off of? - Blakdoxaduo (talk) 19:53, 23 May 2015 (PDT)
Best one would be Lesser Spirit- Wisp.png Spirit Summon: Wisp. Make sure you include
<span style="display: none;">{{</span>
//skill table
<span style="display: none;">}}</span>
since templates hate pipes "|" and we use that to "hide" the pipes in skill tables. Otherwise, we would need {{!}}{{!}} for every "||" which looks likes "butts". User_talk:Everspace#Extensions --Dfoplayer (talk) 20:03, 23 May 2015 (PDT)
So many butts. Personally, I don't care for rowspan="58"|15 littered about the wiki pages, because that value doesn't grow or change. The table should be about being able to compare how a skill changes as it progresses. Should all skills have a "rowspan=32|Instant" for their cast time component? I don't think so.
--FMageIcon.png Everspace (talk) 20:07, 23 May 2015 (PDT)

You cannot post new threads to this discussion page because it has been protected from new threads, or you do not currently have permission to edit.

Contents

Thread titleRepliesLast modified
The All-in-One Patch this coming January222:32, 24 December 2015
Stuff in Attributes; Damage Type Indication620:15, 8 September 2015

The All-in-One Patch this coming January

Hey fellow Wiki-ers. If you guys don't know, DFOG will be receiving a HUGE patch this coming January (Probably after Jan. 19, 2016). Link The link provided only lists a few of the mentioned changes. Other Link We will be receiving more 2nd Awakenings, dungeon revamps, etc. Be prepared. A lot is going to change and a lot of pages are going to be out of date, particularly skill pages.

I think what we need now is a plan to prepare for this event. Do you guys have any suggestions?

03:22, 21 December 2015

"f mage nerf" WHAT. >:O
I have taken up on a side project for this winter break, so I haven't been on DFO recently. Maybe the best thing we could do is restart the "Class Info Volunteer List" from SirKerfluffles. Just push SirKerfluffles' list into a dropdown list to hide the old one.

07:14, 21 December 2015

It's finally happening. Super sad.

I've not been playing (but rooting for neople!) So I'll pop in every once and awhile.

22:32, 24 December 2015
 
 

Stuff in Attributes; Damage Type Indication

So on some pages we currently have, things like SP cost per level and CD are listed within the skill table itself, such as with High Kick. Others have them listed in the attributes section Spirit Summon: Flame Hulk. Is there a certain way we want to be doing it?

Also, I was thinking it could be a good idea to represent the type of damage the skills do in some way (if applicable). We could include what type of damage the skill does (Physical/Magical/Neutral?/Elemental Type?) in the Attributes section (describing multiple damage cases when necessary of course). Another option would be that we could color code the damage types. In this second case, ex: Shock Wave. We could reduce the table headings to just "Sword Swing's Attack Strength", "Shockwave Multihit's Attack Strength", and the values themselves could be colored for physical/magical. It could get messy for all the elemental types though. We'd have to think up of a color chart to represent everything. And make a key.

Edit: Trying out the "Add Topic" button. Didn't know it would do this.

12:16, 7 September 2015

Well, this new threads should be for the better. May take sometime to get used to it. Also, signature is no longer required. Unless one edits someone else's post, which one should not be doing.

1) I believe we are going to try to push everything in attributes and remove rowspan.

2) I think color coding with in-line html is going to be messy.

14:10, 7 September 2015

So fancy!

  1. I'm not against rowspan itself. I'm against rowspans for things that never change (like how much SP something costs). Even for 2nd Awakening with it's 500 initial and 200 afterwards scheme, you can better express it in the attributes section.
  2. I think mentioning the type of damage is a good idea (like The Void is dark element, but only the smash of the floor of Hammer of Repentance is light damage). This should not on the skill table itself.

I'm currently thinking of how I want to handle colouring things like item rarity, or the elements across the wiki (probably something like <font/span class="Dark">). A big problem is that all the colours chosen are for viewing on a dark background (which doesn't makes sense on the default white wiki) so I've sortof just been collecting colours before I implement anything. Semantic wiki (so many nifty things!) has been taking up more of my spare time outside of job hunting.

15:31, 7 September 2015

Ok. One downside to using this thread box is that you don't get emails for updates (at least I haven't). The signature happens automatically too, so no changing that.

  1. My original question was actually the same as the first topic at the top of the pace, just noticed. Will try and keep static things in attributes, since I agree with the sentiment that some tables are wide enough with all they have going on without the extra clutter.
  2. Regarding the colors thing, it's just a suggestion, so if it doesn't work out it's fine. Honestly I think the simplistic statement of if the hits do Physical/Magical damage in Attributes works just fine. @Everspace: Since it sounds like you've been looking into it though, you've probably come across this stuff already but in case you haven't, a quick google search brings up http://www.tedmontgomery.com/tutorial/clrnmsWH.html. And tangentially you can use always use Paletton and/or Adobe Kuler to find similar colors and find variations that might work better.
23:20, 7 September 2015

That can be solved. It's going to be in your Preferences, under "user profile" tab. Unfortunately, we also have this "new messages" button on the very top. That also tell you all the threads you have been watching. [Example].

06:24, 8 September 2015
 

I like to think of it as "The Skill Growth table is only for things that grow or change with the skill".

The biggest problem is Common, Unique, and Light attributes since they're all quite bright.

16:55, 8 September 2015

Another approach that could be taken is coloring the table cell backgrounds instead of the text. Black works pretty well as text with most colors, and for the darker colors lighter shades could be used.

20:15, 8 September 2015