dont think so no, that's one of the problems with replay buffers, there's no feedback unless you have the recording folder open and look at the files appearing (or write some external script to listen when a file is added)

https://clips.twitch.tv/CoweringSleepyHeronFailFish

dont install gfe, use obs replay buffers with nvenc as shadowplay

ez

https://twitter.com/SVIFTGAMING/status/953254372804349952

https://i.imgur.com/UQbmcXM.png

https://i.imgur.com/wRQi1sF.png

he says the words "team fortress 2" at https://youtu.be/iAvVbHzU-N0?t=1m58s if anyone's interested

! is for twitch chat flamers...

any (or at least most) !command in sourcemod can be replaced with a /command which is invisible in chat, if you didnt know

reminds me of the story sideshow told a few times on stream about him mentoring a low level team, their med dies so he says "right everyone needs to go die now" (get their med) and the pocket just shoots himself 4 times to kill himself

having done a bunch of CS school projects (including half of 2 separate undergrad dissertations) making a logs parser could be a cool project but you'll likely want your project's goals to be flexible (i.e. it's fine if you can't parse the whole logs file, just some bits that you need). this seems possible with logs (they basically look like this

https://i.imgur.com/ktV08DE.png

with different plugins having more events than others). you can download raw logs from logs.tf

parsing itself is kind of tricky sometimes but this seems reasonably simple just by splitting the string and looking for words in certain places. it might be too simple though (my concern is once you've figured out how to bring in a file and figure out how to parse each line it becomes pretty boring, just adding more events and shit) but that's probably for your teacher to decide

i believe gjon's stats used on eu streams are done by parsing logs but im not 100%. instead of just aggregating stats, how about some cool visual representations of a match? stuff like showing capture point progress against time on a graph or maybe something showing damage done for each team against time

i wouldnt worry about getting the logs themselves. if you want you could build in a way to automate downloading a file from http://logs.tf/logs/log_LOGID.log.zip, unzipping it and putting it through your program but i dont think that's the important bit

budget? the XL2411 is the best of the cheap entry level 144Hz, though you might want to shell out more for better colours or resolution

it seems all you get extra on the viewsonic is inbuilt speakers (puke) and freesync which you said you didnt need

slower sens and less flicking is more consistent, try that. you might think you need to take your shots quickly but by keeping your crosshair near where you're going to aim you barely waste any time. it's a good habit to get into

go London Spitfires (don't recognise any of those players but im glad i have a physical location to tie the team to that i am connected to thanks OWL administrators)

do yourself a favour and run the 1.3.0 dev snapshot version of mumble. it's very stable but idk when that shit will get released. some of the new features dont work on 1.2.x servers but changing levels individually works fine

you probably mean the dev snapshot version https://wiki.mumble.info/wiki/Main_Page

and a different map. getting kinda boring playing process 6 or so times a season