Talk:Community Spy strategy

Is this necessary?

Is it just me, or is this a completely unedited version of the normal strategy page? This just asks for becoming a huge mess. Do we really need this page? The Spy strategy page is already rather large and is technically a user guide in itself, unless the community as a whole agrees to everything on it. --Kurathedog 21:31, 6 November 2010 (UTC)

They're exactly the same page, the one you linked to will redirect to this one. --Firestorm 21:33, 6 November 2010 (UTC)

It is rather big, i would be surprised if too many people got all the way through. Mabye there would be a way for a veterain editor to fix it up a bit? make it more readable, or at least, seperate it up into colapsable sections, IE:kinfe's, watches ectCaptain Craven 23:27, 8 November 2010 (UTC)

I'm not a veteran editor, but I would like to give this a try. Judging from the length, it might take a while. My work will appear on my talk page, so we can compare against the original article. ShunyValdez 06:08, 10 November 2010 (UTC)

There are a few typos on this page such as, "Keep your Revolver at less [that] full ammunition and you will automatically pick up the weapon and hide all evidence of the stab." And reading the blocks of text is a very unappealing prospect to potential readers. Separation through titles such as "Offensive Play", "Defensive Play" and "General Play" or something of the like for weapons would be helpful. Hot Chips 02:46, 9 November 2010 (UTC)

There's also a lot of technical data on disguises, which doesn't fit the nature of a strategy page. I propose we move the data to the disguise page. ShunyValdez 06:18, 10 November 2010 (UTC)

Ironically, that data was actually removed FROM the Disguise page and moved here, as it was decided it didn't belong over there, but it was also asked that some of the removed strategy info be put here. Perhaps it ought to be removed altogether (or just completely re-written to be less cluttered - I think there are a few good points in there)? Will-T 21:57, 11 November 2010 (UTC)

Interesting. On my current draft, it looks better without the technical data. I'm going to try rewriting it after I'm done organizing the strategies. I don't want to remove it from the wiki because its interesting, but it has to be put in the right place. ShunyValdez 01:21, 12 November 2010 (UTC)

Request for feedback on my draft

I need feedback so I would know if I should continue or discard my work. Here's the link: http://wiki.teamfortress.com/wiki/User:ShunyValdez/Community_Spy_strategy

Some things to note:

• Instead of a huge list of general strategies, I tried to break the strategies into different sections. What do you guys think?
• I've removed the example weapon combination. Most of a spy's loadout is dependent on the situation. And yes, I know that the community strategy guidelines recommended them, but I wish to make a case that its unnecessarily.
• This is still a work-in-progress.

ShunyValdez 14:19, 24 November 2010 (UTC)

I've emulated this article's practice of adding icons for each of the weapons on some of the other Community Class Strategy articles; it makes the article a little easier to read as opposed to being a large mass of text. I have no opinion on removing the example weapon combinations, but either they or the following text might be redundant unless we just want to treat the example weapon combinations as a sort of quick suggestion for readers instead of them having to read each section in-depth. ButteredToast 14:24, 24 November 2010 (UTC)

Re-skins in example combinations?

Should we start using re-skins like Big Kill in the example combinations? I, personally don't find it necessary but people started putting them in. --HimitsuNoRyu 21:06, 22 April 2011 (UTC)

If someone mentions a reskin, replace it with the stock weapon, and if there's already such a combo, just try to append its content into the already-existing entry. -- LordKelvin 02:29, 23 April 2011 (UTC)

well someone made the primary in a combination Revolver OR Big Kill. I'm asking if we should remove the mention of the Big Kill and lave it at revolver.HimitsuNoRyu 04:03, 4 May 2011 (UTC)

Just remove any mention of the Big Kill. It's just a reskin, so there's no point in talking about it as if it's a different weapon. -- LordKelvin 16:48, 4 May 2011 (UTC)

Divide 'general' topic

What do you all think about dividing the "General" heading into several subheadings depending on the tip. I would probably be able to dramatically reduce the size of this page if it could be done. Atonement 20:59, 1 March 2012 (PST)

Eternal reward vs. sentry

Are you sure it possible to avoid the sentry locking on by stabbing an engineer with the eternal reward, without a disguise prior to killing the engineer? I tried doing so, and I failed miserably. I uncloaked with the cloak and dagger, stabbed the engineer, the sentry gun locked and turned. I tried to cloak when the sentry gun gave the audio cue, but it shot me anyway. Was the engineer supposed to be right between me and the sentry, or is there more to this? K-Raider NL 03:45, 4 July 2012 (PDT) As long as you're both behind the Sentry there should be enough time to stab him and take his disguise. It depends alot on how far around the Sentry has to turn. » Cooper Kid (blether) • (contreebs) 10:34, 4 July 2012 (PDT)

Regaining Cloak

The Letranger is a useful weapon for regaining cloak. Can this be added to methods of regaining cloak? Barack Obama (talk) 20:54, 31 May 2014 (PDT)

If a Medic hits a cloaked, undisguised Spy with a Ubersaw, does the Medic gain 25% Uber?

This is about this line: "If you know you will die to an Ubersaw, try to Cloak or disguise to deny the Medic extra Über."

I remember reading somewhere that the only way to deny a Medic Uber is to disguise, and that Medics still get Uber from hitting a cloaked but undisguised Spy with the Ubersaw.Anyar (talk) 18:48, 5 February 2017 (PST)

Extremely outdated guides

The last two links are to Spy guides from 2008, the video and post on GameFAQs is extremely outdated. Someone should make an updated Spy guide/link to a more up to date one