Difference between revisions of "Talk:Lockbox"

Revision as of 19:55, 4 August 2014

Notes

I'd like to try to keep things less rigid. For example, say "certain months" instead of "the month this happened to be introduced for first" to avoid overly detailed future edits. Unless, of course, someone gets information from a GM/Dev that says "this box is for this month" or after a few years it only shows up in one month. As far as I can see, there are not currently enough icons of lockbox types currently in the game files for all 12 months of the year. This, of course, can change. -Novaster 18:56, 2 August 2014 (UTC)

Linking

This page has the same issue as the Prize Box page regarding redirect links and certain browsers (see the discussion tab for the prize box page). It's just not as apparent because the list isn't very long - yet. I'm not sure if effort should be made to fix things for iron, as long as Iron is left at the top (as it should be if the list is DoR by default, which IMO it should be DoR by default)...but I mean, all things should be consistent. Harrumph. But for other boxes further down the list - pay close attention to other linking coding. What makes this annoying is that I don't know any nifty table/template tricks to force the column to differentiate between different acquisition methods - if these things were 100% certain to only ever come out of a box and nowhere else, then the coding used in the this template would be a super easy solution. Alas, single-acquisition source is not the case for many accessories (like the Aura in general, or specific kinds like Volcanic Spike Mohawk). Additionally, some accessories come from non-box places (like the steam dragon wings), which requires links that can't simply be "plug 'n chugged" like other sources. So, it's tedious, but at least it can be fixed...with my time-consuming, not as-slick feeling method. Anyone know any better solutions? I'm not going to go through and fix ALL the accessory tables on each page right now, since it's not a huge issue on this page yet...but mostly because I don't want to do a ton of work in case there is a nifty trick (a simple template line of code that fixes all the pages at once, which is of course the point of a template) that can solve this for all browsers. I really don't want to have two different acquisition columns, but I think that's what I'll end up doing after a good long while if nobody can come up with something nifty for a single column.

TL;DR: links that lead through redirects in tables land users who use certain browsers (firefox, idk about others) to weird, incorrect spots on the redirected-to list page, is there a quick template code solution that doesn't break tables or lose acquisition information? -Novaster 19:37, 4 August 2014 (UTC)

Forum Node -Novaster 19:55, 4 August 2014 (UTC)