Template talk:InfoBoxMercUnit

Layout

I was thinking about the layout because the way it is now it fits to the info you can get from the housebooks. Wouldn't it be better to just get some basic stuff in and write the rest in the Composition passage? Also there isn't much room to write more about the composition then the size maybe, details like type of jumpship, name of jumpship, type of dropship, name of dropship, etc. have to be dropped anyway. For now I can only think of 2 points that can be covered there: 1. When was it formed, 2. What’s the status of the unit. In this way an update by a future sourcebook doesn't need another infobox just edit the one that is used. As setting up an infobox each time the unit is covered in a sourcebook, scenariobook, etc. just fills the article with a long line of boxes filled with Yes or No.--BigDuke66 21:41, 24 August 2008 (CDT)

Other Time Frames

The InfoBox only handles one time frame currently (the only data I have is for 3025). I would like to expand it so that it covers other time frames, but I'm not sure what other time frames are covered in the source books. 3050? 3056? 3125? If someone can let me know what other times are provided, I'll add those to the InfoBox. Obviously, some of the units don't exist in later frames (like my own 12th Star Guards), but others, like ELH, do, I believe. Any help would be most appreciated. Thanks! Bdevoe 11:35, 4 August 2007 (CDT)

Field Manual: Mercenaries covers 3058, while Field Manual: Mercenaries Revised, Mercenaries Supplemental, and Mercenaries Supplemental II cover 3067. Some units have separate scenario packs that cover other periods, as the Black Thorns do. I would suggest making one box (since they all contain the same info anyway) and adding it in for any appropriate time. Scaletail 13:34, 13 August 2007 (CDT)

What do you think of the idea of having multiple info boxes in a single entry? For instance, I could make it generic and set it up such that the article's author adds the date for that infobox instance? To use the 12th SG as a base, I would have one infobox with 3025 data and potentially another with 3050, but there would be two boxes. Just wondering if that kind of thing would be seen as acceptable or if I should find some way to generate a box on-the-fly. :) Bdevoe 14:34, 14 August 2007 (CDT)

I see no other way of doing it. If we're going to make use of the infobox, then we have to accept that there are going to be times when there could be several, especially for a unit like the ELH. --Scaletail 15:59, 14 August 2007 (CDT)

Extra spacing

Hi all. I think the infobox has come along nicely, but there is one aesthetic element that I need to fix, which is the extra spacing, especially when a unit has only one subunit. Once I get that sorted out, I think this will be looking good. Bdevoe 13:58, 18 September 2007 (CDT)

This is excellent. I didn't expect you to incorporate all those suggestions I made, let alone so quickly! Scaletail 16:45, 18 September 2007 (CDT)

Well, I was avoiding work, so... :) The only concern I have is the size of the text and the wrapping. There are a couple of things left to do to make it look nice, but I think overall it seems to be coming along well. Thanks for the comments and I'm glad you're happy about it. :) Bdevoe 18:06, 18 September 2007 (CDT)

Adding #if Statements

Would you mind if I added {{#if}} statements to the rows? Thanks. --Ebakunin 16:56, 21 August 2008 (CDT)

The creator of this template hasn't been around for a while, but I would have no such problem. --Scaletail 20:57, 21 August 2008 (CDT)