Difference between revisions of "Template talk:Unusual quality checklist"

From Team Fortress Wiki
Jump to: navigation, search
(A "Used To be" key)
(A "Used To be" key)
 
(4 intermediate revisions by 2 users not shown)
Line 8: Line 8:
  
  
Hi to all, I'm updating this list on a REGULAR basis. I check often if new hats exist, and have updated a couple lately. Will keep doing this, its the best way I can help :D I have also been looking for more bugs. [[User:goldnuts]]
+
Hi to all, I'm updating this list on a REGULAR basis. I check often if new hats exist, and have updated a couple lately. Will keep doing this, its the best way I can help :D I have also been looking for more bugs. [[User:goldnuts]] — <small>The preceding comment was added at 19:26, 9 January 2012</small>
 +
==Cleanup==
 +
Good idea there to clean it up and separate "can't be unusual" into a section, and then its neater. Even better, why have "can drop" It does not drop this is about UNUSUALS. Drop or not means nothing here. Remove that entirely?? then you can have GREEN can be unusual RED not unusual, way way easier to understand the page. [[User:goldnuts]] — <small>The preceding comment was added at 19:27, 9 January 2012</small>
  
Good idea there to clean it up and separate "can't be unusual" into a section, and then its neater [[User:goldnuts]]
 
  
Once hats are on the unusual list I think it is very unlikely they would come OFF the unusual list, but effect combinations might get stopped (like unboxing a burning slug might not be possible one day) [[User:goldnuts]]
+
Once hats are on the unusual list I think it is very unlikely they would come OFF the unusual list, but effect combinations might get stopped (like unboxing a burning slug might not be possible one day) [[User:goldnuts]] — <small>The preceding comment was added at 19:43, 9 January 2012</small>
 +
 
 +
:The template definately needs cleaned up - the colour coding for Halloween items, for example, is completely unnecessary. None of those items can be unusual anyway! I agree that it would make the table much more readable if items which cannot be unusual are simply removed. It's got to the point where there are so many items that it's just too much to list them all in one table. A simple layout similar to [[Template:Hat craftability list|this one]] would work, with classes down the left-hand side. '''» [[User:Cooper Kid|<span style="color:red">Coo</span><span style ="color:gray">per</span><span style ="color:blue"> Kid</span>]]''' <small>([[User_talk:Cooper Kid|blether]]) • ([[Special:Contributions/Cooper Kid|contreebs]])</small> 07:01, 12 January 2012 (PST)
 +
::Alright, I've had a play around and I've come up with [[User:Cooper Kid/Sandbox#Testing stuff below this line|this]]. What do you think? '''» [[User:Cooper Kid|<span style="color:red">Coo</span><span style ="color:gray">per</span><span style ="color:blue"> Kid</span>]]''' <small>([[User_talk:Cooper Kid|blether]]) • ([[Special:Contributions/Cooper Kid|contreebs]])</small> 08:25, 12 January 2012 (PST)
 +
 
 +
That looks really good, nice and clean.. gets my vote [[User:goldnuts]]

Latest revision as of 11:16, 7 May 2012

A "Used To be" key

Should there be a "used to be" symbol added, seeing as how the Blighted Beak and Le Party Phantom could have been unusual only if received before the change to misc. -= M-NINJA Burger Gib.png =- 21:59, 2 January 2011 (UTC)

How about this thing? P Had.png -= M-NINJA Burger Gib.png =- 22:01, 2 January 2011 (UTC)
Not really necessary, the tables just showing which hats can have that quality. Whether they can still be found or not is not that important I think, the information is on the relevant hat's article. User Moussekateer signature sprite.pngMoussekateer·talk 22:40, 2 January 2011 (UTC)

I believe we should clean this list up and remove all items that can't be unusual, similar to the vintage and genuine lists. A second list with non unusual items can be created if needed and linked. kenny 07:44, 11 November 2011 (PST)


Hi to all, I'm updating this list on a REGULAR basis. I check often if new hats exist, and have updated a couple lately. Will keep doing this, its the best way I can help :D I have also been looking for more bugs. User:goldnutsThe preceding comment was added at 19:26, 9 January 2012

Cleanup

Good idea there to clean it up and separate "can't be unusual" into a section, and then its neater. Even better, why have "can drop" It does not drop this is about UNUSUALS. Drop or not means nothing here. Remove that entirely?? then you can have GREEN can be unusual RED not unusual, way way easier to understand the page. User:goldnutsThe preceding comment was added at 19:27, 9 January 2012


Once hats are on the unusual list I think it is very unlikely they would come OFF the unusual list, but effect combinations might get stopped (like unboxing a burning slug might not be possible one day) User:goldnutsThe preceding comment was added at 19:43, 9 January 2012

The template definately needs cleaned up - the colour coding for Halloween items, for example, is completely unnecessary. None of those items can be unusual anyway! I agree that it would make the table much more readable if items which cannot be unusual are simply removed. It's got to the point where there are so many items that it's just too much to list them all in one table. A simple layout similar to this one would work, with classes down the left-hand side. » Cooper Kid (blether) • (contreebs) 07:01, 12 January 2012 (PST)
Alright, I've had a play around and I've come up with this. What do you think? » Cooper Kid (blether) • (contreebs) 08:25, 12 January 2012 (PST)

That looks really good, nice and clean.. gets my vote User:goldnuts