User talk:Shadowtrooper

Archive

Copyvio
Riffsyphon tells me you have the Essential Guide to Vehicles- would it be possible for you to do me a favor, and look up the Carrack article? Because they seem rather similar to me, which would be a copyvio; but before I go slapping a copyvio on an article, I prefer to doublecheck. Thanks. --Maru 16:38, 17 Jun 2005 (UTC)
 * Replied [[Image:Implogo.jpg|15px]] Shadowtrooper talk 17:28, 17 Jun 2005 (UTC)

EAW info
Hi! I see you´re writing some new stubs about vehicles in Empire At War. I´d like to know where you are getting your info from, as I´ve never seen any names being given to the new vehicles in that game yet. Thanks! VT-16 09:30, 28 Aug 2005 (UTC)


 * Replied [[Image:Tbhelm.gif|30px]] Shadowtrooper talk 18:36, 30 Aug 2005 (UTC)

Do you mind?
Hey Shadowtrooper, I find your little Scout Trooper really cool. Uhhh... do you mind if I use one for my own (not a Scout Trooper of course :P). It is your idea after all, right? Inmobilus 19:25, 15 Oct 2005 (UTC)
 * Replied [[Image:Tbhelm.gif|30px]] Shadowtrooper talk 03:30, 22 Oct 2005 (UTC)
 * Thanks Shadowtrooper! :D I'll use my Boba :) --[[Image:BFguy.gif]]--Inmobilus 14:17, 23 Oct 2005 (UTC)

Why your watchlist is all weird
We had a vandal earlier today calling himself "SuperShado" redirecting pages and generally causing trouble. &mdash; Silly Dan 01:27, 6 Nov 2005 (UTC)
 * So I see, thanks muchly. [[Image:Tbhelm.gif|30px]] Shadowtrooper talk 01:30, 6 Nov 2005 (UTC)

Signature icons
Hi Shadowtrooper,

I was just wondering where you came across those little icons e.g. your Scout Trooper and Imobilus's Boba Fett. Would you be kind enough to let me know please? :)

Thanks!

Forgotmytea 21:17, 14 Jan 2006 (UTC)


 * Replied [[Image:Tbhelm.gif|30px]] Shadowtrooper talk 18:26, 16 Jan 2006 (UTC)


 * Thanks - I was wondering if you've got a Jango Fett file/icon somewhere? :)

Thanks again, Forgotmytea

Infoboxes
I saw your recent edits on the ship template and on the Delta-7 fighter, and I must say that I'm impressed -- they look nice. However, on the Delta-7 article, I saw that you manually created the high-level infobox for that specific ship. While this looks great, I'm not sure if using maually generated infoboxes is the best idea. Besides being a hassle to code, they can deter newcomers and take up a lot of space (well, relatively). As I said in my question here, I think we should establish more guidelines regarding infobox type/usage for various categories. What do you think? Thanks, RMF 19:07, 5 February 2006 (UTC) {{ship| image= name=Alpha starfighter manufacturer=Rothana Heavy Engineering| line=Alpha series model=Alpha-class starfighter And so on, using the templates' fields. This is the standard way, but not necessarily the best. Although much easier to code/edit/use, the disadvantage of this is that all the fields on a template will show up on all of the articles that reference it, even when some fields aren't needed. Example: if you use the ship template with a TIE fighter, a number of the fields don't apply (such as shielding, hyperdrive). Worse, on articles with only a little information, many of the fields must be labeled "unknown." The advantage of the current method (using pl, plf, and plh) is that it is easily modifiable, allowing only the information that is known to be placed on the article page. The disadvantage of this is that it lacks uniformity and doesn't look nearly as nice as high-level 'boxes (e.g. planet, ship). Your method, using customized high level infoboxes for each page, has its own advantages and disadvantages. I'm not saying any method is right, I would just like to see more guidelines and regularity. Keep up the good work. RMF 19:34, 5 February 2006 (UTC) {{Infobox/Delta-7 Aethersprite-class light interceptor}} This way, we have all the advantages of a custom high-level infobox without all the messy code. Thoughts? RMF 21:51, 6 February 2006 (UTC)
 * Replied [[Image:Tbhelm.gif|30px]] Shadowtrooper talk 19:16, 5 February 2006 (UTC)
 * Thanks for the prompt reply. I don't know if it's the proper usage, but the standard way of using high level infoboxes is to place all the source code on a template page and then reference that for each article. This is what you would put in the article: (a fictional article using the ship template, which already has the source code)
 * I was thinking about our dilemma here and I came up with an idea: suppose we created an individual infobox for each ship, but instead of placing it on the article page we created a new template and simply reference that? For example, on the Delta-7 article, we could cut the infobox code and paste it into a template, one entitled Template:Infobox/Delta-7 Aethersprite-class light interceptor. Then, in the article, we would simply put the following at the beginning:
 * I went ahead and implemented this on a number of different articles: ARC-170 starfighter, Delta-7 Aethersprite-class light interceptor, Alpha-3 Nimbus-class V-wing starfighter, Eta-2 Actis-class light interceptor, even the AT-TE page (I used different colors and fields, of course). It works very well, and looks neat and clean on the article page itself. The only disadvantage I can see is the lack of uniformity/regularity among ships: we can negate this (for the most part) by referring to a standardized template with all available fields in the correct order. Then, when we convert low to high-level, we remove the fields that don't apply. I know you have a WookieeProject Vehicles, should we create a WookieeProject Starfighters (and others, of course) for this? RMF 01:35, 7 February 2006 (UTC)