I wrote an entire nerd essay about why I'm stupid for spending half my TF2 career playing sniper when sniping is actually the most boring thing in TF2 for me now and then my internet went down so I lost the nerd essay and now I'm more frustrated than I was before

I'll be adding those to the list of further customization.

I'd like to set it up with a basic vpk and a more in-depth one.

The Basic vpk will have the basic commands but will include a readme explaining every command. There will also be sections in the readme on more advanced commands + how to open console because many players don't know how to.
examples:
A Hitsounds section will go over killsounds, dingaling_volume, min_pitch, max_pitch, etc
A Damage Numbers section will mention batching, batching_window and I'm probably also going to include an optional Huddamageacount.res for readable damage numbers so Default HUD users can have readable damage
With the basic vpk it's up to them how they customise things

The in-depth vpk will have settings such as combattext_batching enabled by default and more visible damage numbers. Probably something like b4nny's damage numbers. Bigger and yellow (or maybe white). This is for very new users that want the more in-depth settings but don't want to go through the process of figuring out how to customise everything

Making a list of basic commands. Give feedback

Though some people might not like m_rawinput 1 and cl_autorezoom 1 I think it's fine to keep those in. If they don't like it and remove the vpk for that reason the other commands will remain at the correct values unless they change them back. And if they stick with it they'll realise these commands are better than the values they were at before

The end product will include a readme.txt with all the commands and a short description for all of them + further customization (stuff like tf_dingaling_volume)

One mistake in there is that hud_combattext_batching_window has a max value of 2. Also lots of people don't even know console is a thing so I recommend putting in a couple of methods for enabling the console
(with ~, with launch options, binding a button to "toggleconsole", some custom huds also give you the option to toggle it in the main menu. Some keyboards can't open console with ~. German keyboards and Belgian keyboards are an example)

I can also make a vpk that people can just put in Custom and it execs all the basic commands like fov_desired 90, m_rawinput 1, etc without people having to go through the process of putting a folder within Custom, adding a cfg map, making an autoexec.cfg etc. Might make that later. Should be very easy but I have exams so I'll do it during a later break today

edit: nvm making it now

also it's tf_dingalingaling 1, you misspelled it

https://www.youtube.com/watch?v=P4BFy2K5wQU

Probably the encoding. Recording at 1080p might help. If you record at 720p and then render/encode to 720p you'll lose detail no matter what you do. If you record/encode at 1080p 720p should look better and there'll be a 1080p option for those who want to watch it in 1080p. I currently record/encode at 720p as well but I'm going to try using Sourceres for future videos which should help. You can go even higher than 1080p with this if you feel like it

Solution 1: mat_mipmaptextures 0. Be sure to look at your graphics cfg if you use one and change it there

Solution 2:
alias weaponfix "mat_managedtextures 0; mat_managedtextures 1; hud_reloadscheme; snd_restart"
bind [key] weaponfix
(Put both commands into your cfg, replace [key] with an actual key so you can use it in-game. This command should lag your game for a bit if you press the key you bound it to but after that it should hopefully be fixed)

I don't have this issue so I have no way to test if these actually work but they've worked for others in the past apparently

necroing 2 threads for the same question without even providing the right information. And neither thread has to do with the problem you have. nice

http://puu.sh/qC7ib/2c7a0c35ed.png

What black thing? Need to be more specific. Screenshots please.
Some people see black weapons/props. I think mat_bumpmap(?) is the cause of that. Not sure if that's the command but I don't feel like digging for the right command when I don't even know what the problem is

https://clips.twitch.tv/sideshow/CuriousBoarCoolCat

https://carbed.files.wordpress.com/2009/06/race_car_bed.jpg?w=450

Lost all my saved quotes but these are 2 of my favorites from a friend's stuff

* Mr. Jelly changed name to just got 144hz
giv me money for 144hz : ;(

TomTheTurtwig : 1500 houra i knoq what a hacker looks like

I think ruwin used chris' dx9frames. That's what I remember from when people asked in chat. not 100% on this though
https://chrisdown.name/tf2/

No. That's just command lines in the autoexec using the Echo command. It's raysFox https://twitchemotes.com/emote/37757

If you really want it just ask and I'm certain someone will post the pastebin

From the discord

AnAkkk works fast though so I'm confident invites will be enabled again within a couple of days :)

Nothing you can do to stop it sadly. Just some 12 year old playing around with his wasted 10 dollars or however much a viewbot subscription costs these days.

Don't worry. Twitch won't ban you for it. I've known a couple of people who had it happen to them. Twitch Support always told them they definitely won't get banned for it but there's not much that can be done about it.
This was before the lawsuits though. And someone told me Twitch recently changed some backend stuff to combat viewbotting so maybe there are things they can do about it now. You can contact Slin about it and maybe he knows more

Unless it's someone you know I highly doubt this viewbotter will keep doing it

Custom > whateveryoucalledthis > [scripts and materials folder here]

weapon txt files go in scripts. you edit these to change the crosshair for each weapon. crosshair section can be found near the bottom of txt file

VMT and VTF files go in materials > vgui > replay > thumbnails. the VTF is the image, the VMT tells the game where to find the VTF and how the VTF behaves (you can use VMTs to make rotating crosshairs and stuff for example but it's useless)