The next logical step is to make a 24/7 twitch channel that plays tf2 videos from this site and does requests. Kind of like tempustv but for fragvids
Account Details | |
---|---|
SteamID64 | 76561198010239925 |
SteamID3 | [U:1:49974197] |
SteamID32 | STEAM_0:1:24987098 |
Country | United Kingdom |
Signed Up | August 20, 2014 |
Last Posted | April 30, 2024 at 9:39 AM |
Posts | 1624 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | nice |
Windows Sensitivity | the princess |
Raw Input | 1 |
DPI |
over |
Resolution |
a picnic |
Refresh Rate |
luigi? |
Hardware Peripherals | |
---|---|
Mouse | of |
Keyboard | to |
Mousepad | invite us |
Headphones | for |
Monitor | eh |
Valves business model is just passive income. They make most of their money from the steam store where they can sell other peoples games, and then a lot of the content for their games is user created and they pay them commission.
Valve's got ~300-400 employees which is a tiny fraction of the number that some other games companies with similar annual turnover have. It makes sense though because why pay people's salaries (expensive) when you can automate the thing that brings the money in, that's pretty much always in a company's interest if they want to maximize profits.
This guys gonna hit some big airshots at lan.
honestly I think the 6v6 community needs to give koth_nippletwister a chance every time I've played on it I've enjoyed myself heavily.
Ok so I've been thinking about some of the stuff you could do with this over the past couple of days.
I really think it would be cool if you could get information from the demos.tf demo parser which is what I was referring to earlier (https://demos.tf/viewer to see it in action). This provides a wealth more data that logs don't. There are an unbelievable amount of dimensions to the data you could theoretically get at each tick from stvs, it would probably be possible to map things like uber locations, average player health at different parts, sentry spots on last, tracking where individual players stand in their esea matches etc etc.
Your other option is logs which are a lot easier to extract data from but as people have said there's limits to what you can do with them.
I briefly played around with trying to make a heatmap of kill locations (i.e. where the person getting the kill was standing) for individual matches. The hardest part was tying image coordinates from a map overview to ingame coordinates and I could only find overviews for snakewater and badlands where I could do this easily (and I'm not sure that the mapping is totally accurate but it works well enough). I didn't combine multiple logs for this because I didn't have the time but here's a map of Mix^ and iM's kills respectively in (the non golden cap part of) their famous snakewater game:
This players worst crime is he stole my hat. He clearly cannot be trusted. Ban him I say.
Would be pretty cool if you could create 2 teams by inputting steam ids and generate an entire predicted log from those ids.
hayesWhile I think there are a lot of good ideas being thrown around, how you statistically define those parameters based off the information that logs.tf provides is the main problem. I was thinking specifically about stalemates, and I am not sure what would be the absolute best way to define it (and I'm not sure what logs.tf is capable of). For example, how about something like net kills during a certain time interval? We would expect it to be low, but during times that would not be traditionally a stalemate, this could also be true (rolling out to mid, the moments following a complete wipe of the other team, etc.). How about if both medics have uber, is it always considered a stalemate? There are definitely plenty of circumstances where that is not necessarily true. I've no clue but it would be super neat to know.
I think there is actually a way of doing this. I don't think it's possible through logs.tf, but there was a site that took data from demos.tf and showed an animation locations of the players in the map. I think a really cool project would be to take these demos (or if you wanted a smaller but perhaps more useful dataset you could use only invite/prem stvs) and produce a heatmap of player location density. (Each tick from each demo would effectively give you 12 datapoints for this, so you get a pretty big dataset). I imagine maps that are famous for stalemating will have concentrated high density regions (e.g. badlands in lobby and at last). I think this would be more beneficial than heatmaps of deaths which is something valve has already done e.g. with dustbowl.
Also finding cheaters with outlier analysis would be good too.
whens the rky fragvid coming out
if u have to be looking at a player to do damage to them then u probably just suck lmao.
Asia isn't too bad, Africa is hard mode and Oceania is impossible.