Template talk:Infobox Djinn

Examples
Ok, here's an example of each box for every element.

~ dkpat 16:11, 26 May 2011 (CDT)

Suggestions
Okay, first of all, I think we should dump the "games" and "locations" fields. I feel that there's a good reason we haven't used such fields before. Also, we may want to have separate fields for each stat under "set bonuses", much like what we do with equipment. I may come up with more examples later. P.S. I like how the colors came out ;) (I still think Venus 3 should be changed, though.) The World&#39;s Hungriest Paperweight 16:24, 26 May 2011 (CDT)


 * I figured with set effects we could list them in that field, because there is such a variety, and not every Djinn will have the same ones. Just put each effect on a new line. and I was struggling to come up with possible fields for this box.


 * Also, does anyone else care to add input? would be great to get more than my and paperweight's opinions ~ dkpat 04:50, 27 May 2011 (CDT)


 * I agree that with the stat bonuses being what they are, it would be easiest to put them all in one field. But I also feel that as Hungry said, having a Locations field would be unwise because of the likelihood of clutter. Having a Games field doesn't seem too bad, though; we can just use the 2-3 letter acronyms to conserve space. The only issue is how to deal with items not normally available in TLA, but available with the data transfer, but I think we can come up with something. --TheOthin 05:39, 27 May 2011 (CDT)


 * First of all, I'm still opposed to keeping the "games" field, but I'll agree that if we do keep it the acronyms would be the way to go. As for set bonuses, I'd like to remind you both that some fields can be optional and don't appear unless you actually type them in. If you don't believe me, just take a look at the weapon and armor infoboxes. These have separate fields for all possible stat boosts, but you don't see all of the fields popping up on every article. I'm just suggesting we do something similar for this infobox: Each of the six stats would have a separate field, but would only show up on appropriate pages. The World&#39;s Hungriest Paperweight 10:32, 27 May 2011 (CDT)


 * Now that I think about it, we could do something similar for the games/locations fields: Have a separate "location" field for each game, which would only appear if that Djinni actually appears in that game. I wouldn't exactly approve of the idea myself, but I felt it was only fair to share it. The World&#39;s Hungriest Paperweight 10:58, 27 May 2011 (CDT)


 * Good point about the infoboxes. Looks like I still have a lot to learn about those things. As for the fields for the location and games, is there a reason why you're opposed to them? It may be that you're seeing an issue that dkpat and I aren't seeing. TheOthin 11:41, 27 May 2011 (CDT)


 * I think my opposition to listing the games and locations is more of a personal opinion than a logical deduction. I personally don't think such information should go in an infobox, but I may very well be in the minority here. Since Wikis are collaborative efforts, I won't put up any struggle if everyone else wants to add that info. After all, finding the best way to portray something is more productive than being the only person trying to get it removed ;) The World&#39;s Hungriest Paperweight 12:31, 27 May 2011 (CDT)


 * How would the content inside this location section be presented? That's a deciding factor in whether I'd approve of the section or not. First of all, I wouldn't approve of it if the content takes a full sentence to get its information across, like for Petra, "Randomly fought in the eastern part of Hesperia". But I'd like to get some concepts across.
 * For Steel:
 * Gabomba Statue
 * Kaocho


 * For Vine:
 * Angara
 * Teppe Ruins


 * Essentially, with the syntax underneath these acronyms you can convey what each acronym means by letting the viewer roll over it. Even so, I'd have to wonder if explaining the location is the point of the main article content to begin with... Erik the Appreciator 14:07, 27 May 2011 (CDT)


 * Erik, you'll have to explain the last bit of your comment. Do you mean we shouldn't because that is the whole point of the article? or that we should because.. umm something. Also, wow, what a turn this took, wasn't expecting this much feedback. lol. I'm not overly pro location and games, I just think it would be good information to put into the box. Further, the stat bonus I would almost like to change the others personally.. though that would be a big hassle. lol... Consistency is key though, I agree. ~ dkpat 16:14, 27 May 2011 (CDT)
 * Right, I meant that since the main content of the article is where a Djinni's location and obtainment method is elaborated on in full, and since that is information that can't really be encapsulated in few enough words to fit it in an infobox (unlike how much HP a Set Djinni gives, for example), I would vote to have that left out of the infobox. It's like how some years back someone was trying to put in debut information for character infoboxes, and this was the content that was stuffed into Isaac's infobox at one time:

|goldensundebut= Prologue sequence at Vale, both as his younger and modern-day selves. |thelostagedebut=Jupiter Lighthouse. Recruited at Felix's party at Contigo after a conversation.
 * That is information that's more appropriate to have explained in-depth in the article to begin with, and it also made the balance of space between infobox cells very lopsided (one cell in a column having lots of text in it makes all the other cells very wide too even if they don't have much in them). Erik the Appreciator 16:36, 27 May 2011 (CDT)


 * I mentioned earlier that we could simply have separate fields for separate games. For example, let's use Gust:


 * That's just my idea. And, again, that's only if we decide to go through with this. I hadn't thought about the "battled or not" stuff, in which case doesn't sound so bad. The World&#39;s Hungriest Paperweight 22:23, 27 May 2011 (CDT)


 * I don't mind dumping location, I do think that games should stay. How hard is it to keep this in it? Just make Abbreviations for each (the established TLA, GS, DD) and stick those in the field with links to the games page. Location is detailed, but Games is not, and it is basic information. ~ dkpat 12:10, 28 May 2011 (CDT)

Version 1.1
Okay, I've tried "upgrading" it. Now, just give me a moment to see if it works. What do you say we use Flint?

Okay, so there's a problem, but just give me a moment. I think I know how to fix it. Problem fixed! Anyways, what do you think? I'm sure it needs some fine-tuning, of course, and we still can't seem to agree on what to do with the games and locations, so for now I just tossed them in and we can remove/change them as necessary. The World&#39;s Hungriest Paperweight 12:01, 3 June 2011 (CDT)
 * I think all of it is good, making the locations content like that would inform the readers well. Erik the Appreciator 13:51, 3 June 2011 (CDT)
 * Sounds good to me! (P.S. I would have taken some initiative myself here but.. I am graduating today, So I've been pretty busy lately. lol Sorry guys.) ~ dkpat 14:38, 3 June 2011 (CDT)

I've tried something else new (and adjusted dkpat's original examples so they wouldn't look wierd. Hope ya don't mind ;) ^_^; ). Basically, I took out the "starelement" field and added a new "skin" field. I also adjusted the "element" field so it just acts like a normal field. Now, you're probably wondering why I did so, since the infobox worked the way it was. I've got two reasons for you:

1) It might just be me, but the "starelement" field is terribly counter-intuitive. People familiar with other infoboxes, but not this infobox, would have no idea such a field exists and would try adding the star icon manually. Doing so would just plain screw things up. Now, I'll admit that having a separate "skin" field may also seem counter-intuitive, but at least the "element" field works how people would expect it to. Besides, I'm hoping to find a way to make it so that the infobox has a "default" color it uses when the skin field is left blank, that way people unfamiliar with the skin field won't post a pure-white infobox (just one that isn't "customized").

2) I'm hoping we can set up other infoboxes to change their colors to match their elements as well. Some of these infoboxes, like pure-element weapons, don't have an element field (in the case of weapons, we just put the star icon in front of the attack rating). Rather than adding element fields and having to re-arrange every article, we can just add the "skin" feature to those infoboxes and add the skins whenever we get around to it. Again, this is assuming we can set up default colors, and I don't know enough about infoboxes to pull that off ^_^;

Anyways, I don't expect everyone to like my idea, but at least I've explained why I did this. If anyone can see some fatal flaw in my plan, please speak up so we can figure out a solution before putting this infobox into use. The World&#39;s Hungriest Paperweight 22:56, 3 June 2011 (CDT)


 * ".Besides, I'm hoping to find a way to make it so that the infobox has a "default" color... " It's easy to accomplish, I promise. Get me some colors together, and I can do one for you to show you how. .. actually there is probably multiple ways to do it.. but the one I'm thinking uses templates like the rest of the colors. Where we have "Background:# {{ {{{element}}} Color 1};" simple change the element portion to... "" doing this will fill it is with the word default when the field isn't used.
 * Also, I did the starelement because I thought it would be neat and simple, I really wanted 1 input to rule them all.. but the star images had to be lowercase, unlike how we need the element said. lol. I have no problems splitting it up, I just liked 1 field to rule them all. :P ~ dkpat 01:50, 4 June 2011 (CDT)


 * Thanks, and I'll have to remember how that works! And it sounds like there's no hard feelings, which is always good ;) The World&#39;s Hungriest Paperweight 11:27, 4 June 2011 (CDT)