dflame is so nutty PogChamp
Account Details | |
---|---|
SteamID64 | 76561198077260471 |
SteamID3 | [U:1:116994743] |
SteamID32 | STEAM_0:1:58497371 |
Country | United States |
Signed Up | August 7, 2016 |
Last Posted | December 13, 2018 at 11:55 PM |
Posts | 84 (0 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
1920x1080 |
Refresh Rate |
60 Hz |
Hardware Peripherals | |
---|---|
Mouse | Logitech g402 |
Keyboard | ROCCAT ISKU FX |
Mousepad | Qck Heavy |
Headphones | |
Monitor |
wrong thread woops
Apparently, if you put the command "showpanel specgui" in console while alive in a match, you can see your whole team's health and uber as if you were in death cam and spectating your team. Found this out when I executed my autoexec which had that command in it.
Edit: After testing it in both casual and SOAPDM servers, it looks like this is merely a cfg exploit for some servers including ESEA match servers. The hud panel did not show up in casual or DM, but I noticed it was possible to see it in my most recent ESEA match on snakewater.
Edit #2: http://steamcommunity.com/sharedfiles/filedetails/?id=864347321 screenshot of the cfg exploit in ESEA server
An annoying bug I found when offclassing to heavy on last is that if you switch off of heavy while reved up, autoreload turns off. I think it fixes itself if you change teams or retry to the server. It's pretty annoying when you're trying to fight and you think you have 6 shots until you realize you only have 2.
What file corresponds to the player name and player health of the player you are spectating? What would I do if I wanted to get rid of it?
I can't believe they included the "I'm sorry I'm just European" meme in the trailer lmao
[*] one day the curse will be broken
Skyttle is a great person with a great attitude and work ethic to match. While she might now be the most experienced 6s player, she learns fast and would be a great pick up for a new team. 10/10 would bump again
@Paulsen I followed your directions to enable statusspec and entered the commands you told me as you described, including the directions in Github to launch TF2 in insecure mode.
PaulsenFirst you'll need to enter the following command: statusspec_localplayer_enabled 1
This will enable the feature... You can still use statusspec_localplayer_player just fine.
In order to use this command you need to enter the following into console: statusspec_localplayer_player x,
where "x" is the player index number...
So for example, if the player you wanted to highlight the killfeed for had an index number of "5" you'd first enable the localplayer feature, i.e. enter statusspec_localplayer_enabled 1 into console. Then you'd enter statusspec_localplayer_player 5 into console. The killfeed for that player should now be highlighted.
However, none of this worked. No matter what number I put for statusspec_localplayer_player, nothing in the killfeed would be highlighted. Do you have any idea what I could do to fix this?
@Paulsen thanks so much for the guidance, I never knew this was possible
capnfapnwho is "allany" and why is he on my friendslist xd
xd
well written post otherwise
My null movement script was working fine in casual as of last night.
https://soundcloud.com/dillistone/dillistone-lili-n-rude
https://soundcloud.com/nebbra/odesza-say-my-name-ft-zyra-nebbra-remix
gg to running from mustard; that was one of the closest games i've ever played, tons of fun