| Site Notice |
|---|
| Due to recent vandalism, all edits performed by IPs and new users will be reviewed before being published. This means it might take some time for your edit to show up. New accounts also have to be confirmed before being created. If you have any questions, contact one of the staff members on their talk page, or on the Discord server. |
Talk:Coliseum Quests/March 2017: Difference between revisions
Jump to navigation
Jump to search
→Reply: to KrytenKoro/Kvasir |
KrytenKoro (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
:At the very least, can we put buffs and notes in one column, maybe with rowspan=2, and shrink the images or text?[[User:KrytenKoro|KrytenKoro]] ([[User talk:KrytenKoro|talk]]) 20:25, 9 March 2017 (PST) | :At the very least, can we put buffs and notes in one column, maybe with rowspan=2, and shrink the images or text?[[User:KrytenKoro|KrytenKoro]] ([[User talk:KrytenKoro|talk]]) 20:25, 9 March 2017 (PST) | ||
::I already shrunk the buff/debuff images' pixel size from when they were initially implemented via templates, so they at least match the size of the attribute gems & are still legible (''I tried going smaller & anything smaller than the current size is too small to be legible''); the column that's being distended, when it shouldn't, is the Enemies column - there's so much leftover space. (''Maybe shorten that column width-wise & lengthen the Notes column width-wise?'')<br>Instead of shrinking the buff/debuff images & text, maybe enlarge the enemy images by a few pixels?<br>The only thing really bothering me is Round 10's Black Gummi Copter row, where the enemy names & buff images aren't aligned to the top of their boxes. Other than that, everything else looks fine to me.<br>Alternatively, there's an unused Quest Walkthrough section that the longer notes could possibly go to?? (''What even are the Notes column & Quest Walkthrough section really meant to be used for, anyway?'')<br>'''<span style="color:lightgray; background:gray">~ Xeranis</span>''' | ::I already shrunk the buff/debuff images' pixel size from when they were initially implemented via templates, so they at least match the size of the attribute gems & are still legible (''I tried going smaller & anything smaller than the current size is too small to be legible''); the column that's being distended, when it shouldn't, is the Enemies column - there's so much leftover space. (''Maybe shorten that column width-wise & lengthen the Notes column width-wise?'')<br>Instead of shrinking the buff/debuff images & text, maybe enlarge the enemy images by a few pixels?<br>The only thing really bothering me is Round 10's Black Gummi Copter row, where the enemy names & buff images aren't aligned to the top of their boxes. Other than that, everything else looks fine to me.<br>Alternatively, there's an unused Quest Walkthrough section that the longer notes could possibly go to?? (''What even are the Notes column & Quest Walkthrough section really meant to be used for, anyway?'')<br>'''<span style="color:lightgray; background:gray">~ Xeranis</span>''' | ||
:::I created the Notes columns to include stuff like whether an enemy has a ''unique'' status, like ambush, hidden, chance, or a stage-unique buff like in the DDD quests where everything starts off asleep. However, I'm really quite certain that, especially for Coliseum, everything listed on this page is the enemy's ''normal AI'', and should thus be covered on that enemy's page, and possibly referenced in a strategy write-up for the coliseum (which we definitely should be doing).[[User:KrytenKoro|KrytenKoro]] ([[User talk:KrytenKoro|talk]]) 14:55, 13 March 2017 (PDT) | |||
Revision as of 13:55, 13 March 2017
The long notes are distending the box and having their icons be way bigger than the images of the actual enemies. In addition...man, I swear I've seen that behavior from every member of that species. I'm really sure we're conflating enemy AI with quest-specific stuff.KrytenKoro (talk) 20:24, 9 March 2017 (PST)
- At the very least, can we put buffs and notes in one column, maybe with rowspan=2, and shrink the images or text?KrytenKoro (talk) 20:25, 9 March 2017 (PST)
- I already shrunk the buff/debuff images' pixel size from when they were initially implemented via templates, so they at least match the size of the attribute gems & are still legible (I tried going smaller & anything smaller than the current size is too small to be legible); the column that's being distended, when it shouldn't, is the Enemies column - there's so much leftover space. (Maybe shorten that column width-wise & lengthen the Notes column width-wise?)
Instead of shrinking the buff/debuff images & text, maybe enlarge the enemy images by a few pixels?
The only thing really bothering me is Round 10's Black Gummi Copter row, where the enemy names & buff images aren't aligned to the top of their boxes. Other than that, everything else looks fine to me.
Alternatively, there's an unused Quest Walkthrough section that the longer notes could possibly go to?? (What even are the Notes column & Quest Walkthrough section really meant to be used for, anyway?)
~ Xeranis- I created the Notes columns to include stuff like whether an enemy has a unique status, like ambush, hidden, chance, or a stage-unique buff like in the DDD quests where everything starts off asleep. However, I'm really quite certain that, especially for Coliseum, everything listed on this page is the enemy's normal AI, and should thus be covered on that enemy's page, and possibly referenced in a strategy write-up for the coliseum (which we definitely should be doing).KrytenKoro (talk) 14:55, 13 March 2017 (PDT)
- I already shrunk the buff/debuff images' pixel size from when they were initially implemented via templates, so they at least match the size of the attribute gems & are still legible (I tried going smaller & anything smaller than the current size is too small to be legible); the column that's being distended, when it shouldn't, is the Enemies column - there's so much leftover space. (Maybe shorten that column width-wise & lengthen the Notes column width-wise?)