Talk:Equip region/Archive 1

The following discussion is preserved as an archive. Please do not modify it.

Arms/Left Arm

Should the Pip-Boy go to the "Arms" region and/or the Purity Fist go to the Left Region? TFPlayer™ 22:20, 18 October 2011 (PDT)

Those are the equip regions as defined in items_game.txt so no. —Moussekateer·talk 22:27, 18 October 2011 (PDT)

Hat regions

"All hats have an equip region of Hat." Except some take up other regions as well, such as Spiral Sallet, or are Whole Head, like Horseless Headless Horsemann's Head. These should probably be listed in the table too, no? Mar 00:14, 19 October 2011 (PDT)

Yes, those should also be listed, along with the hats that are "whole head" Balladofwindfishes 10:14, 19 October 2011 (PDT)

Region Conflicts

I'm not quite sure, but I think the table is wrong. I've seen several people using Foster's Facade (face region) with glasses/eyes. According to the table, this is not possible. BadKarMa 04:54, 20 October 2011 (PDT)

Those people are using the current exploit via the Quickswitch menu to equip conflicting misc items at the same time. It is not Valve's intention. SS2R 04:57, 20 October 2011 (PDT)

Obsessive Templation Disorder

Like most of my other projects, I felt the need to craft a hybrid template. In this case I created a new Equip Region Table. It's a combination between the style of our Hats/Misc Navboxes and our current Equip Region Table. It probably won't be easy to update as the current one, but it still looks pretty nice. So gather your opinions and tell them to me; shall we use it? 14:27, 25 October 2011 (PDT)

 Oppose I prefer the actual one, it's smaller and clearer. We don't need bigger icons, small are sufficient, and more elegant here. It's not like the Hat page where you need to see the hat to click on it. Tturbo _{( / )} 16:18, 25 October 2011 (PDT)

Robot hats

All of the MVM robot hats/misc are missing, as is the gear grinder/oil spill badge. C2Vproductions The Ultimate Nintendo Fan 23:05, 21 October 2012 (PDT)

Fixed. TNS 01:12, 22 October 2012 (PDT)

Nesting issue

All of the lines after the equip region table are inside of it. r 1 ^{[ C T ]} 21:31, 31 October 2012 (PDT)

Bearded Bombardier contradiction

On the Bearded Bombardier page in the info, it says that it's a Beard region item, but on this page it says that it's a Face region item. Could someone clear this up? — The preceding unsigned comment was added by Reduxist (talk) • (contribs) 20:13, 01 December 2012

Demoman face and mustache.

One of the equip regions for the English page is "Demoman face and mustache" translated into Finnish. I can't seem to get into the table, so I'll let one of you guys do it :D ---- MrFreakshow182 at 18:57 (GMT) on 15th June 2013

You can simply sign your comments with ~~~~. I'll take a look, thanks. – Smashman _(talk) 10:58, 15 June 2013 (PDT)

 Done – Smashman _(talk) 11:29, 15 June 2013 (PDT)

My fault, I'm sorry lmao

Zabidenu

(contribs ▪ talk) 11:29, 15 June 2013 (PDT)

Heart of Gold Needs on the Medal portion on the List of Equip Regions.

I checked and as of this post it isnt on there. I'd do it myself but i'm rather new to editing pages and i couldnt figure it out.

Spell Nexus (talk) 02:27, 3 December 2013 (PST)

Yes it does. I will update this entire list later on, thanks for pointing it out. —Moussekateer·talk 03:13, 3 December 2013 (PST)

Class Sorting?

Since the list is already some kind of table, shouldn't it be split into separate columns for the classes? I'm thinking, since this list orders the items by directly relevant and observable properties, as opposed the introduction date based sorting used everywhere else on the wiki, it's probably the most useful list already. Having it all in one column makes it somewhat hard to read, though, and I really don't see the harm changing this. LupoCani (talk) 12:55, 13 October 2014 (PDT)

Most of the template is done through a script that automatically outputs the contents once the updated tf_english.txt and items_game.txt files are run through it. To change how the template is arranged would require a large part of that script to be changed. --Omolong (talk) 17:46, 13 October 2014 (PDT)

How large an undertaking would this be? Where can this script be found?LupoCani (talk) 13:41, 14 October 2014 (PDT)

No idea how large an undertaking it would be, I didn't make the script and I don't understand Python (the language it's written in). I can also never remember where I got it from in the first place. --Omolong (talk) 13:44, 14 October 2014 (PDT)

If you have it, (And it's probably mousse's) I can edit it for you. LupoCani: Can you make a sample/describe more precisely what you want? Darkid (Talk | Contribs) 13:50, 14 October 2014 (PDT)

Yeah, I'm pretty sure it was originally Mousse's, I just can't remember where I downloaded it from. But here, that's my most up to date version. It includes all the tournament medals and such. Though we could probably do with something to automatically add in items without an equip region as well, but I've got no clue how to go about that. --Omolong (talk) 13:54, 14 October 2014 (PDT)

Alright, preciseness. What I suggest is that the items in each row be sorted into columns by what class they belong to. Ten columns would be preferable, one for each class plus one for all-class items. Items equipable by multiple classes, but not all, could get duplicate entries in the different columns.

Of course, the only reason I suggest this is because I think the wiki should have region-sorted and readable a list somewhere, and this is the one that is the closest at the moment. After all, the first thing you'll notice or want to know about an item is if it's a hat or a shirt, not what update it was introduced in. Having such a list somewhere on the wiki is what I'm actually trying to suggest, not that it specifically be found here. Before anyone codes anything, it should be considered whether it's the optimal place to keep it.LupoCani (talk) 14:54, 14 October 2014 (PDT)

So:

Equip Region	Scout	Soldier	Pyro
Arm Tattoos	Fast Learner Paisley Pro Track Terrorizer
Arms	Essential Accessories	Steel Pipes	Abhorrent Appendages

That look right? With all the classes and rows, of course. Darkid (Talk | Contribs) 16:11, 14 October 2014 (PDT)

I've got a sample (working) version at my sandbox. The formatting is not perfect, feel free to play with it, but it raises an interesting point about size concerns: This seems very cramped. Darkid (Talk | Contribs) 23:04, 14 October 2014 (PDT)

Yes, that's exactly what I was suggesting. Seeing it in practice, as you say, does reveal a number of problems. While some categories, such a the shirt one, are radically improved, the table in general is riddled with so much empty space it hurts.

I'm not to certain of what the constraints are. If the script could deviate from a strict grid format, possibilities like putting the all-class items in a separate repeating row (like [1]. My apologies for the quality) could help a lot. I can think of other options too, but it all comes down to what wikimedia will or will not allow. LupoCani (talk) 04:32, 15 October 2014 (PDT)

Yeah looking it over, it is pretty cramped. I've made a small change to it that should reduce how cramped it is, but it does mean that it takes up a lot of space, and it doesn't really do much about the empty space. I also made a few other minor changes, such as adding in a link to Tournament Medal, so we have a general link to those, and removing all the different variants of Spine-Chilling Skull 2011, seeing as they all redirect to that page anwyay. --Omolong (talk) 08:02, 15 October 2014 (PDT)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ LupoCani: I can easily do that. Please, if you have suggestions, make them, odds are we can do it. Omolong: I'll implement those changes in the code. Any other suggestions? Darkid (Talk | Contribs) 16:36, 15 October 2014 (PDT)
New revision with moved allclass is up: User:Darkid/Sandbox2. I've also implemented a bit to remove the particular classes if there are no individual classes (Earbuds, Flair, e.g.) Darkid (Talk | Contribs) 01:39, 16 October 2014 (PDT)
I've attempted to clean up a bit more: User:Darkid/Sandbox3. I don't have code yet for this (though it won't be hard), I'm merely looking for positive/negative input, or other stylistic suggestions. Darkid (Talk | Contribs) 04:30, 16 October 2014 (PDT)

Alright then. This multi-table approach decimated the empty space quite effectively. Could the class-specific lists perhaps be integrated into the main table? I'm thinking they could have their item fields changed from stacked columns to regular rightward-expanding rows to save vertical space, and then be stacked on top of each other and put directly under the multi-class section. I think that's all that's left to do before it's fairly complete. LupoCani (talk) 11:29, 16 October 2014 (PDT)

I've changed User:Darkid/Sandbox3 to vaguely reflect what you mean. It is going to be hard to merge those tables together, unfortunately. Darkid (Talk | Contribs) 14:25, 16 October 2014 (PDT)

You missunderstand. When I said row strucure, I meant stacked rows. As in, exactly the same as stacked columns structure, but with the listed items paralell to each other, not on top. Or, of you will, what you would get if you took the current lists and rotated them 90 degrees. Would that be any easier to integrate in the main table?LupoCani (talk) 06:04, 17 October 2014 (PDT)

I have updated my sandbox again. Is this what you mean? If not, please use visual aids. Darkid (Talk | Contribs) 06:13, 17 October 2014 (PDT)

Just for reference, I've done a bit of editing to the formatting which should make the unexpanded table headers a bit nicer to look at. --Omolong (talk) 06:39, 17 October 2014 (PDT)

Yes, that is quite precisely what I meant. Would these tables be tables be easier to intergrate into the main one? If not, perhaps they could be merged into one, called "class-specific regions" with no class subcategories, but class symbols as indicators next to the region name, where the same thing is currently said in hyperlinked plaintext? LupoCani (talk) 12:22, 17 October 2014 (PDT)

Is it crucial that these equip regions be sorted separately? If this is not required, it would be considerably easier to integrate them into the main table if they could retain their original alphabetization. This would not, however, sort them in class order. Darkid (Talk | Contribs) 12:31, 17 October 2014 (PDT)

This should not be a problem. Darkid (Talk | Contribs) 12:36, 17 October 2014 (PDT)

Somewhat confusingly, you edited your message to state that it wouldn't be a problem just as I was writing my response. I was actualy going to say that it would probably look quite alright even if the single-class categories were sorted alphebetically, possibly even better in fact, but if you can group them easily, go ahead. Maybe even try both and put them up next to one another. LupoCani (talk) 12:48, 17 October 2014 (PDT)

Sorted in: User:Darkid/Sandbox2. Sorted out: User:Darkid/Sandbox3. Darkid (Talk | Contribs) 14:00, 17 October 2014 (PDT)

Alright, it's not that big a difference, but I have to say the "sorted out" one is more readable. Unfortunately, it seems we have again run into the issue of excessive empty space. Another way to sort the class-specific lists would be to keep adhering to the the class columns that the rest of the table uses, but put different equip regions next to each other. So in the scout column you would have backpack, bandages, hands, pants and wings, and next to that in the soldier column you would have cigar, coat, legs and pocket on the same height. This would only work if the areas could be individually labeled, but should eliminate the last shreds of excessive emptiness. LupoCani (talk) 15:56, 17 October 2014 (PDT)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ You should only use outdent if you're the person starting a new post, not at the end of your post.
The problem with merging them together is the fact that it is very hard to do dynamically. Not that hard, mind, but we'd run into issues like the Pyro Head replacement. Honestly, the whitespace in the table is pretty negligible now, I'd be OK with it "sorted out". Darkid (Talk | Contribs) 16:01, 17 October 2014 (PDT)

Alright then. I'm fine with it too, so I say we go ahead and put it on the page. One last thing though- the table's title is currently written over three lines when hidden, when one quite enough. An insignificant detail, but probably an easy fix as well. LupoCani (talk) 16:39, 18 October 2014 (PDT)

Well then. As a finishing detail, could the plaintext class names in the class-specific region section be replaced with icons? Seems to be the convention on the wiki to do that, and it does look better. Possibly put the icons to the left of the region name too. LupoCani (talk) 02:16, 20 October 2014 (PDT)

The problem is those strings are a part of the dictionary, and are used in the infobox. If you can find a way of making them look good there too, feel free to change it. Darkid (Talk | Contribs) 02:28, 20 October 2014 (PDT)

Beard and Hat conflict

I haven't tested it yet, but using itemtest and googling, it appears that beard items cannot be equipped with a hat item. If this is true, please add it to the wiki, if not, sorry for wasting your time and thanks for telling me :) Zxthad (talk) 01:43, 1 November 2014 (PDT)

Some multi-class hats have changed

From what I have noticed, the Cute Suit is no longer just avaliable for pyro, but also engineer. In the table it is under Pyro head replacement, not pointing anything to engineer. Also another one I have noticed is the HazMat Headcase also is under head replacement for pyro, but also can be equipped by the sniper. Mightyplate (talk) 13:37, 19 January 2017 (PST)

Fun fact

Do you know, that Cammy Jammies and HazMat Headcase have same region? Yes, I was shocked. And even more interesting, there is nothing say about these two items for Sniper in the table. Maybe you need to somehow to describe this? And if there are experts here, then tell please, why are they in conflict areas? Which area of them are in conflict? Is this a bug, maybe? Герамтур (talk) 20:47, 22 November 2018 (UTC)

List of Currently Missing Cosmetics on this page

Arm Tattoos:

Heavy - Soviet Strongmann

Arms:

Sniper - Scoper’s Scales

Back:

Demoman - Melody of Misery

Engineer - A Shell of a Mann

Beard:

Scout - Fuel Injector

Demoman - Gaelic Glutton

Heavy - Wild West Whiskers

Engineer - Wise Whiskers

Medic - Madmann’s Muzzle, Miser’s Muttonchops

Sniper - Most Dangerous Mane

All-Class - Bread Biter

Belt:

Pyro - Deity’s Dress, Pocket Pardner

All-Class - Gingerbread Mann, Pocket Admin, Pocket Halloween Boss, Pocket Santa

Face:

Demoman - Unforgiven Glory

Feet:

Scout - Olympic Leapers (needs image)

Pyro - Hot Huaraches

Heavy - Abominable Snow Pants

Spy - Bandit’s Boots

All-Class - Loaf Loafers

Glasses:

Scout - Soda Specs

Pyro - Pyro in Chinatown

Medic - Flatliner

All-Class - Stapler’s Specs

Head Skin:

Scout - Speedy Scoundrel

Heavy - Mediterranean Mercenary

Engineer - Dell in the Shell

Sniper - Handsome Hitman

Left Shoulder:

Pyro - Fiery Phoenix

Heavy - Momma Kiev

Spy - Bird’s Eye Viewer

All-Class - Croaking Hazard, Pebbles the Penguin, Polar Pal, Quizzical Quetzal, Sledder’s Sidekick, Terror-antula

Necklace:

Medic - Harry, Self-Care

Spy - Harry

All-Class - Glittering Garland, Slithering Scarf

Shirt:

Scout - Aloha Apparel, Athenian Attire, Jungle Jersey, Juvenile’s Jumper, Pompous Privateer, Poolside Polo

Pyro - Wanderer’s Wear

Demoman - Dynamite Abs

Heavy - Kapitan’s Kaftan, Paka Parka, Siberian Tigerstripe

Engineer - Aloha Apparel

Medic - Coldfront Carapace, Derangement Garment, Vitals Vest

Sniper - Conspicuous Camouflage, Mislaid Sweater, Wagga Wagga Wear

Spy - Aloha Apparel, Dressperado

Whole Head:

Scout - Cross-Comm Express (remove)

Heavy - Kathman-Hairdo

Sniper - Re-organize cosmetics

Pants (Scout) - Transparent Trousers

Coat (Soldier) - Sharp Chest Pain

Pocket (Soldier) - Attack Packs

Towel (Heavy) - Heavy Harness

Belt (Engineer) - Conaghers’ Utility Idol, Mini-Engy

Pocket (Engineer) - Pocket Saxton, Pocket Yeti, Tropical Toad

Hip (Medic) - Pocket-Medes

Bullets (Sniper) - Jarmaments

Legs (Sniper) - Scoper’s Scales

Pocket (Sniper) - Bait and Bite, Koala Compact, Pocket Saxton, Pocket Yeti

Quiver (Sniper) - Elizabeth the Third

Vest (Sniper) - Down Tundra Coat, Rifleman’s Regalia

Coat (Spy) - Smoking Jacket

Missing Equip Regions

Right Shoulder:

Scout - Catcher’s Companion

Engineer - Aim Assistant

NOTE: Polar Pals conflict with Right Shoulder

Ears:

All-Class - Deadbeats

No Equip Region

Scout - Wild Whip

Soldier - Public Speaker

Pyro - Trick Stabber

Engineer - Trick Stabber

All-Class - BINOCULUS!, Hypno-eyes

Should be complete list. Sorry if this looks intrusive. Kursk (talk) 20:42, 22 September 2020 (UTC)

Should be updated. Thanks~ — Tark lm(pt-br) 02:15, 23 September 2020 (UTC)

"Shared" Equip Regions?

Hi. I noticed that it's not possible to wear the Sandvich Safe and Gift Bringer together, despite them having different equip regions. Apparently, there's a section in the item_schema called "shared". I'm not really sure why this is here, but it may be the reason as to why I was unable to use these together (as well a previously listed bug with the HazMat Headcase on Sniper + Cammy Jammies, when it used to have soldier_pants as the equip region).

• "shared"
  • {
    • "pyro_spikes" "1"
    • "scout_bandages" "1"
    • "engineer_pocket" "1"
    • "heavy_belt_back" "1"
    • "demo_eyepatch" "1"
    • "soldier_gloves" "1"
    • "spy_gloves" "1"
    • "sniper_headband" "1"
  • }
• "shared"
  • {
    • "scout_backpack" "1"
    • "heavy_pocket" "1"
    • "engineer_belt" "1"
    • "soldier_pocket" "1"
    • "demo_belt" "1"
    • "sniper_quiver" "1"
  • }
• "shared"
  • {
    • "pyro_wings" "1"
    • "sniper_bullets" "1"
    • "medigun_accessories" "1"
    • "soldier_coat" "1"
    • "heavy_hip" "1"
    • "scout_hands" "1"
  • }
• "shared"
  • {
    • "engineer_left_arm" "1"
    • "pyro_tail" "1"
    • "sniper_legs" "1"
    • "medic_gloves" "1"
    • "soldier_cigar" "1"
    • "demoman_collar" "1"
    • "heavy_towel" "1"
  • }
• "shared"
  • {
    • "engineer_wings" "1"
    • "pyro_head_replacement" "1"
    • "scout_wings" "1"
    • "heavy_hair" "1"
    • "medic_pipe" "1"
    • "soldier_legs" "1"
  • }
• "shared"
  • {
    • "scout_pants" "1"
    • "heavy_bullets" "1"
    • "engineer_hair" "1"
    • "sniper_vest" "1"
    • "medigun_backpack" "1"
    • "sniper_pocket_left" "1"
  • }
• "shared"
  • {
    • "sniper_pocket" "1"
    • "heavy_hip_pouch" "1"
    • "spy_coat" "1"
    • "medic_hip" "1"
  • }

Pay attention to the bold strings. "soldier_coat" (Gift Bringer's equip_region) and "heavy_hip" (Sandvich Safe's equip_region) is on the same "shared" section... while "pyro_head_replacement" (HazMat Headcase equip_region) and "soldier_legs" (old Cammy Jammies equip_region, prior to the December 11, 2020 Patch). This explains as to why these items were unable to be worn despite being different equip regions. Does anyone have any idea of this shared thing? With this discovery, there might be other combinations that does not work due to this "shared" thing. - ▪ - 22:20, 29 July 2021 (UTC)

This is most likely a way to indicate which cosmetic regions that are specific to a class (E.g. "soldier_coat") overlap with another class' class-specific equip region (E.g. "heavy_hip").
GrampaSwood (talk) 22:33, 29 July 2021 (UTC)

That is most likely the reason, but the majority of them make no sense (but then again, the equip_region system as a whole is not very good). And... why even strict/share equip-regions per class if most of the time these are single-class only cosmetics? I think this is an old implementation that has been left in the game and never touched again. Anyway, should this be added in the page somewhere? Despite them making not much sense and having almost no cases for, there is at least a few cosmetics out there that has these limitations in (Gift Bringer + Sandvich Safe, for example). - ▪ - 16:42, 30 July 2021 (UTC)

Yeah, I'd add info about this.
GrampaSwood (talk) 17:00, 30 July 2021 (UTC)

The preceding discussion is preserved as an archive. Please do not modify it.