keke the based tabby cat
Account Details | |
---|---|
SteamID64 | 76561197999779383 |
SteamID3 | [U:1:39513655] |
SteamID32 | STEAM_0:1:19756827 |
Country | Fiji |
Signed Up | June 24, 2012 |
Last Posted | January 9, 2022 at 11:21 PM |
Posts | 2136 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 3 |
Windows Sensitivity | 6 |
Raw Input | 1 |
DPI |
1800 |
Resolution |
1920x1080 |
Refresh Rate |
120 |
Hardware Peripherals | |
---|---|
Mouse | Xai |
Keyboard | Das silent |
Mousepad | Icemat v2 |
Headphones | ATH-M50s |
Monitor | Alienware aw2310 |
KalkinKillertomatoOur game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.We are aware of and are working on fixing this bug. What crashes you is if you use the quick loadout swap hotkeys or buttons in the loadout menu. If you manually change individual weapons by themselves it will not crash you. For now please be aware of that until we get this fixed.
This bug has been fixed. You should no longer crash.
RakareiKalkin will you show us a picture of the trophy? I asked in stream chat for you to show us the trophy and you didn't.
The trophy is at my folks place. I'm down in San Diego at the moment while I finish up school so I didn't have it on me.
KillertomatoOur game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.
We are aware of and are working on fixing this bug. What crashes you is if you use the quick loadout swap hotkeys or buttons in the loadout menu. If you manually change individual weapons by themselves it will not crash you. For now please be aware of that until we get this fixed.
fosterApparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.
This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.
SneakyPolarBearIf you join a match server and find it to be very glitchy/stuttery, is there a way to get a new server within the same timeslot or withing 15ish minutes?
You can always open a support ticket or message Killing or myself. We will usually switch it over to a new server for you.
Thanks for having me on! One criticism was that I felt we weren't able to get to a lot of the questions people asked. That was probably more due to time constraints however if we were keeping this thing within an hour. I went ahead and answered every question in the other thread that we were not able to get to.
PlatinumI'm thinking it's very simple to code, you have damage coded in. Healing acts like negative damage (see heal numbers?) I'm guessing. I'm no coder, but if the other parser sites can handle it I'm pretty sure ESEA could if they spent a couple hours doing it. I'll talk to Lange and see if he knows anyone who could help.
I don't really know anything about how stat parsing works myself either so it's not something I have any authority on. I appreciate it; I figure if we have something to go off of it will make it easier for them to implement.
Platinumwhat about HEALING STATS
Several questions in this thread are about people wanting heal stats. It is a possibility that we might be able to get that implemented in the future. What would definitely help speed along the process is if someone could get the source code for those stat gathering programs to Killing then Killing can work on getting it implemented. A gigantic overhaul of the ESEA stats system for TF2 is unlikely, but we will try to get healing stats implemented as soon as we can.
zigzterWhy didn't they unban Swatt?
I tried to get Swatt unbanned. The problem is that ESEA takes a hard line approach to account security. If your account gets compromised ESEA views it as your fault, and anything that anyone did on your account as a result of it being hacked are actions that you will be held accountable for.
ClankHow is their day going?
Going great. I just need to finish my senior research project for my PSCI major and I'll be done with college for good.
OdissiusWhy can't they be more open-minded/progressive regarding the use of plugins?
ETF2L allows the use of plugins in their divisions, whether they be transparent viewmodels or increased FOV (and they have had zero impact on the way the game is played).
ESEA will never allow plugins. Things like increased FOV do give players advantages over other players and are outside of developer intent. If TF2 will not allow you to it do within the engine by default then ESEA does not want you to do it either. We may balance the game through things like class limits or weapon bans, but we won't actually change what you are able to do within the scope of the engine.
If you believe that allowing players to have 120 FOV has zero impact on the way that the game is played I believe you you should play on 75 FOV for a week.
PYYYOURDo you guys see teamfortress.tv becoming the main connection between ESEA and the TF2 community?
I do. TF.TV has effectively taken over the role of then gotfrag and natf2. This site has much better functionality than the previous two sites and is run by someone who is entrenched in both the TF2 community and ESEA-Invite. I see TF.tv through streaming even being a better way to connect the comp TF2 community to the pub TF2 community. Our streamers are pulling pretty solid numbers and our casts even better than that.
crumpetwhen will the client taking a shit on the first match of the season stop being acceptable
Usually updating the client is a simple matter that doesn't take much time. However, sometimes there are TF2 updates that make substantial changes to the engine; In this case the change to fix the DX8 crash quite possibly. When stuff like that happens it can screw things up in the client pretty nicely and take a while to fix. That's what happened this season and I apologize for it. We tried our hardest to get it updated as fast as possible and did manage to save the Invite cast for that game at the last minute.
MR_SLINTF2 has a record number of teams signed up for Season 13.
When do they see there being a TF2 Main Division?
I would love a Main division, but in order for us to have a Main division we would need an even larger IM division. One of the problems that I try to combat every season is the epidemic of IM teams dying en masse. If we can manage to continue growing in TF2 and get a semi-large IM then I could feasibly get ESEA to implement a Main division. I would say that the bare minimum amount of teams that I would require to have in IM before I would gut IM to make a Main division would be 36, so that we could have at least 12-16 Main teams. Even then though I think that 36 is possibly too small of a number if we end up having similar levels of attrition that we see in Main currently in IM.