[NvPinder]

Hey man, was a bit bored so decided to watch a vod of yours and try to give some constructive criticism. Worth noting that I think this cast was actually great and i enjoyed watching it, these are just pointers for the sake of pointers cos I'm bored ^^. (Note that everything is from game 1 and in chronological order)

Originally Posted by System

VTAzz vs NvYoonYJ - Play

• I really like how you hype up yoon a lot, but you don't hype up Azz at all which is unfortunate, Azz has been around a long time and if you're going to hype up Yoon that much you need to saying something about Azz. Even if you didn't know much about him just mention how mski is a very strong team and Azz being there ace says a lot about how good he is etc.

• You're solo casting AND observing which makes missing stuff a lot easier, and you put two and two together and do realize that the scouting scv was blocked and somewhat denied by the sentry FF. As a general tip, as an observer you need to be basically watching the minimap 95% of the time, even during battles, and taking note of the production screen. Everything else is practically irrelevant to you since you just need to jump to spots on the minimap where any units are about to meet, or moving away from a base etc. or when you see something come up on the production tab and you might want to quickly select a building

• This is incredibly highly analytical and in no way a mistake in casting, but just mentioning it for future reference if anything of the sort happens in another cast (and note, if you're unsure, just don't try to mention things like this since mentioning it and being wrong is way way way worse than being 90% sure you're right and not saying it), both players builds leave a lot of options to them open, when Yoon scouts the double gas from Azz, and Azz scouts the gas from yoon, it leaves literally every possible 1-base all-in/aggression open. Yoon doesn't dare leave his main with his CC untill he scouts with his scv that Azz has himself expanded, and then safely lifts to the bottom straight after, but not before clearing the probe, leaving azz still completely in the dark, and whilst building an early robo is never really a 'bad' thing PvT, azz is forced to build it at the 6 minute mark because of this unknowingness of yoon's build, and has to have an obs by 7:30 for cloak banshees, as opposed to doing any sort of other early tech such as fast double forge or quick citidal or a big gateway all-in which would be risky given what he knows.

• You are also kind of 'asking yourself' why azz would forcefield, this is generally a bad thing to do as it comes across as either A) You practically showing off you dont have much knowledge, or B) You basically downtalking the player himself as in "Why would anyone ever do that in this situation", which is something you generally want to steer clear of, the best thing to do in any case where you a player has done something you dont fully understand is simply mention the pure basics of it, eg: "Azz threw down that forcefield, which denied yoon from getting full scouting infortmation, which is always beneficial" or w/e. In this case azz has done it purely so yoon cant see azz building the robo, if he sees the robo he can instantly rule out all the 'crazy' stuff that he would try to hide.

• You comment on "Might not be enough forcefields in time for him to stop it" or something along those lines, which is great, it builds tension and anticipation towards the big fight, but you kind of make it out like he's either going to have enough FF or wont and lose, I feel like saying something along the lines of "If yoon does decide to push here Azz is going to need great forcefields to hold", thus hyping up the players themself without them actually doing anything.

• Again you mention that Yoon is skirting around down the bottom of the map in a kind of "I wonder why he's doing this fashion". (To be honest i have no clue why he's doing this), It's almost always better to just play-by-play it in these situations as opposed to kind of asking the question to yourself or co-caster (unless you're casting with a great analytical, or high level player like you were with pig last night).

• Mentioning that a player is floating minerals at all (unless maxed or and banking on purpose etc.) is generally not a good idea, especially right before what could've been a crucial engagement is probably not a good idea :P

• "Over half-way ****" LOL! (obviously a word fuckup but i found it funny )

• You tend to say things like "Unfortunately yoon losing that medivac there" and "Unfortunately azz was supply blocked" etc. This is more my personal tid-bit that it's kind of weird when i hear casters say it because I feel like casters should be talking from a completely un-bias point of view (not that you were bias, you were doing it for both players), but something like like "Being supply blocked during this drop is really bad for Azz as it's allowing Yoon to do an amazing ammount of damage and he is able to now snipe the forges and delay azz's upgrades is this is going to put Yoon in a great position in the next big engagement"

• You say that the vikings are caught out of position, but really it was a great move by Yoon to go foward and pick off a collosus for free

Overall a great cast, I realize i put a lot of stuff in there but know that this is mainly to help you if you wanted to improve a few little things, not as a "YOU SUCK YOU NEED TO FIX THESE" kind of thing. The main things I'd work on would be trying to hype up the players as much as possible in terms of, if a player is winning the game in some fashion (ie: yoon at the end with a great drop and defense), talk about how great his multitasking is/was etc. And the other main point would be stop the rhetorical questions wondering what a player is doing

Quick Comments

	iMSystem:	Wow this is amazing, love feedback <3
	Nemo:	Awesome and very constructive feedback !
	iM yang:	awesome feedback
	|Erasmus|:	That jawline.... oh, and the feedback.
	TAEdgE:
	nirvAnA:	this is how your feedback should always be written, nicely done!
	TCPLemminks: