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

From KHUX Wiki
Jump to navigation Jump to search

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)
Oh, so it's really only for Sleep & Caution! status (since none of the other status you listed ever really show up often); okay, duly noted.
(Should probably be noted in the template code, template's page, or something, so we're made aware of its usage protocol.)
I don't normally encounter those Heartless often enough to have their 2nd turn & 3rd turn buff/debuff/status changes memorized,
so I thought it'd be helpful to other players, to add them under the Notes column (I took the column name of "Notes" at face value).
I would've preferred putting them under the Buffs column, but the dimensions are too small & the entire chart just gets distended much worse than it already is to you.
Perhaps the chart itself could be modified to fix the issues? (Resize the columns/rows, rename "Notes" to *Unique Status*, and rename "Buffs" to * STR/DEF Status*)
Also, the enemies don't even have their own page on this wiki - only a vague description inside another chart of all the enemies - and the links to each enemy leads to another website's info, which is also lacking. So.. Where to really put it?
Only on individual pages that players have to take time to search each & every one for, while in the middle of doing Coliseum, or also the month's one Coliseum chart, which displays all the status details in one place, where the players can conveniently refer to?
I mean, I don't have a problem with adding another section on the page, dedicated specifically for the content that's been placed under the Notes column because at least it's all still on the same page.
Having all that info scattered to other pages just wouldn't be convenient for other players.
~ Xeranis
I mean, that's what I created it for. If the wiki wants to use it for something different, that's the community's decision. I'm just saying, I don't get why it's split into two columns when it could be one.KrytenKoro (talk) 06:32, 14 March 2017 (PDT)