potatohTo minimize the chances of misunderstandings, each person should read the file on their own and not
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).[/quote]
They generally prioritize security, exploits, and crash-related bugs the most
anyone from valve wanna explain why party chat has lagged and crashed (when spammed) everyone's games since it was released in 2016?
Valve feels that even if they did become fully transparent, it’s not what the community ultimately wants. Valve thinks that talking more won’t make the community that much happier, but in fact might even cause a storm of people to become angry
transparency is never bad unless youve got something to hide
anyone from valve wanna explain why party chat has lagged and crashed (when spammed) everyone's games since it was released in 2016?
[spoiler]oh, right
[quote]Valve feels that even if they did become fully transparent, it’s not what the community ultimately wants. Valve thinks that talking more won’t make the community that much happier, but in fact might even cause a storm of people to become angry[/quote][/spoiler]
transparency is never bad unless youve got something to hide
TF2 is not one of those projects that’s important to Valve (right now at least) so any “future TF2 update” work is considered low priority.
yeah no shit
man i wish somebody would make a tf2 6v6 ripoff, just like all those quake 3 ripoffs spurting out
Lastly, Valve is not aware of every single bug the community complains about. Occasionally people
complain about a bug but nobody ever ends up sending a proper bug report email to Valve, so they never
learn about it. It’s actually surprising how much noise people make in unofficial channels yet never send
that noise to Valve through official means (which is usually an email).
You'd think those countless emails people have sent Valve regarding bugs like the sticky det delay/ubers being built during pauses and exploits like editing the spy's decloak sound would have made a difference by now if they really did read their emails. I mean I'm pretty sure some even included step-by-step instructions on how to recreate the problem or even how to fix it. Like how long has it been?
complain about a bug but nobody ever ends up sending a proper bug report email to Valve, so they never
learn about it. It’s actually surprising how much noise people make in unofficial channels yet never send
that noise to Valve through official means (which is usually an email).[/quote]
You'd think those countless emails people have sent Valve regarding bugs like the sticky det delay/ubers being built during pauses and exploits like editing the spy's decloak sound would have made a difference by now if they really did read their emails. I mean I'm pretty sure some even included step-by-step instructions on how to recreate the problem or even how to fix it. Like how long has it been?
bleghfarecpotatohTo minimize the chances of misunderstandings, each person should read the file on their own and not
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).
this warning is incredibly ironic given that the entire document is a summary based on their "recollection"
i dont understand the reasoning behind doing this and not just recording audio
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).[/quote][/quote]
this warning is incredibly ironic given that the entire document is a summary based on their "recollection"
i dont understand the reasoning behind doing this and not just recording audio
I dont believe theres a way to 100% verify a VPK archives file contents, at least in a timely and non-resource hungry way. There are checksums for the VPK archive as a whole but from (very extensive) fucking around in titanfall 2 where its generally more locked down than tf2, as long as the raw file names (vtf/vtm) match their original you can do just about fucking anything. For those who have played it, you can make cloak pilots bright ass pink with maybe 15 minutes of looking through the files and a couple of trial runs. Wanna remove recoil? Done. Want additional gun-perks that you shouldnt have access or be allowed to have x amount? No problem.
Just about anything that can be changed inside one of those VPK files flys, but alias and other shit outside of bind key (no togglebind, from what ive tried) and very simple and cosmetic settings/commands are locked down.
This is all anecdotal, sadly. I haven't decompiled source nor have a private repo of any source-ran game that i can really break down and dive into it.
Just about anything that can be changed inside one of those VPK files flys, but alias and other shit outside of bind key (no togglebind, from what ive tried) and very simple and cosmetic settings/commands are locked down.
This is all anecdotal, sadly. I haven't decompiled source nor have a private repo of any source-ran game that i can really break down and dive into it.
Mankyman i wish somebody would make a tf2 6v6 ripoff
Blizzard already did
Blizzard already did
ShearsMankyman i wish somebody would make a tf2 6v6 ripoff
Blizzard already did
Wwait.. thats true
Blizzard already did[/quote]
Wwait.. thats true
gibusbleghfarecthis warning is incredibly ironic given that the entire document is a summary based on their "recollection"potatohTo minimize the chances of misunderstandings, each person should read the file on their own and not
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).
i dont understand the reasoning behind doing this and not just recording audio
The tours and conversations Valve employees have with guests are entirely done in good faith, and multiple times that good faith been exploited to leak information, such as internal issue lists for Source 2 among other projects. Since long ago, Valve has never allowed video recording and/or photography inside their offices (with certain promotional exceptions), and I highly doubt they'd allow audio recording either.
In addition, if such audio were released of the developers speaking, whether by accident or purposefully, it would be a potential risk to the employee themselves in cases where they say something they shouldn't or they become harassed by the community.
Also, it's important to note:
PotatoDo not read too much into any single thing; you should read the file with a 10,000 foot view.
listen to other people’s summaries (tl;dr’s are quite dangerous here). Reading what other people say about
my experiences has the risk of them injecting false information in their summaries (intentional or not).[/quote][/quote]
this warning is incredibly ironic given that the entire document is a summary based on their "recollection"
i dont understand the reasoning behind doing this and not just recording audio[/quote]
The tours and conversations Valve employees have with guests are entirely done in good faith, and multiple times that good faith been exploited to leak information, such as internal issue lists for Source 2 among other projects. Since long ago, Valve has never allowed video recording and/or photography inside their offices (with certain promotional exceptions), and I highly doubt they'd allow audio recording either.
In addition, if such audio were released of the developers speaking, whether by accident or purposefully, it would be a potential risk to the employee themselves in cases where they say something they shouldn't or they become harassed by the community.
Also, it's important to note:
[quote=Potato]Do not read too much into any single thing; you should read the file with a 10,000 foot view.[/quote]
gibustransparency is never bad unless youve got something to hide
Do you shit with the door open?
transparency is never bad unless youve got something to hide
[/quote]
Do you shit with the door open?
This answered a lot of my questions. Thanks, potato.
ShearsMankyman i wish somebody would make a tf2 6v6 ripoff
Blizzard already did
I dont think a game full of stun mechanics and all kinds of bullshit is similiar to team fortress 2
Blizzard already did[/quote]
I dont think a game full of stun mechanics and all kinds of bullshit is similiar to team fortress 2
Mankyman i wish somebody would make a tf2 6v6 ripoff, just like all those quake 3 ripoffs spurting out
yeah and look how many players each of those have now, same shit with tribes games
yeah and look how many players each of those have now, same shit with tribes games
gibustransparency is never bad unless youve got something to hide
I would disagree very much with that. When a developer states something or promises an update or whatever, you are resigning yourself to fulfil that promise. While that seems like a good thing, it becomes extremely limiting and for a company as volatile as Valve, change is a constant. By becoming more transparent, you risk a larger amount of your player base will become hostile to the changes put forward.
People freaked over "Neato" for Christ's sake, let alone a insight into the developers' mentality and goals. If Valve came out with "We're working on a MvM update", the competitive scene would believe that they have completely abandoned competitive. If competitive is the focus, casual players will claim that the focus is killing off what made the game popular. By not speaking at all, they ideally could listen to what people are saying or reading feedback from emails, etc and work on delivering that through updates and such, which has been the method of communication from Valve for the entirety of the games history.
Nowadays though, the TF team don't have the manpower to sustain that method and because of that, the game feels abandoned and crucial fixes seem like they haven't been patched in years (Det Bug). You can't blame Valve for focusing on more lucrative or innovative ideas, especially due to their transition from Games to Hardware/Software.
Transparency only works when there are enough people there...and even then can do more harm than good. See: Overwatch.
I would disagree very much with that. When a developer states something or promises an update or whatever, you are resigning yourself to fulfil that promise. While that seems like a good thing, it becomes extremely limiting and for a company as volatile as Valve, change is a constant. By becoming more transparent, you risk a larger amount of your player base will become hostile to the changes put forward.
People freaked over "Neato" for Christ's sake, let alone a insight into the developers' mentality and goals. If Valve came out with "We're working on a MvM update", the competitive scene would believe that they have completely abandoned competitive. If competitive is the focus, casual players will claim that the focus is killing off what made the game popular. By not speaking at all, they ideally could listen to what people are saying or reading feedback from emails, etc and work on delivering that through updates and such, which has been the method of communication from Valve for the entirety of the games history.
Nowadays though, the TF team don't have the manpower to sustain that method and because of that, the game feels abandoned and crucial fixes seem like they haven't been patched in years (Det Bug). You can't blame Valve for focusing on more lucrative or innovative ideas, especially due to their transition from Games to Hardware/Software.
Transparency only works when there are enough people there...and even then can do more harm than good. See: Overwatch.
DrHappinessgibustransparency is never bad unless youve got something to hide
I would disagree very much with that. When a developer states something or promises an update or whatever, you are resigning yourself to fulfil that promise. While that seems like a good thing, it becomes extremely limiting and for a company as volatile as Valve, change is a constant. By becoming more transparent, you risk a larger amount of your player base will become hostile to the changes put forward.
People freaked over "Neato" for Christ's sake, let alone a insight into the developers' mentality and goals. If Valve came out with "We're working on a MvM update", the competitive scene would believe that they have completely abandoned competitive. If competitive is the focus, casual players will claim that the focus is killing off what made the game popular. By not speaking at all, they ideally could listen to what people are saying or reading feedback from emails, etc and work on delivering that through updates and such, which has been the method of communication from Valve for the entirety of the games history.
Nowadays though, the TF team don't have the manpower to sustain that method and because of that, the game feels abandoned and crucial fixes seem like they haven't been patched in years (Det Bug). You can't blame Valve for focusing on more lucrative or innovative ideas, especially due to their transition from Games to Hardware/Software.
Transparency only works when there are enough people there...and even then can do more harm than good. See: Overwatch.
i was exaggerating a bit, and i was mainly talking about bug reporting. it would be nice if they at least acknowledged game breaking bugs in their game or replied to some of the numerous emails theyve been sent (since theyre supposedly reading them). i would be less mad at them if they at least explained why they havent fixed some bugs (e.g. lack of staff, hard to implement) instead of their usual silence.
I would disagree very much with that. When a developer states something or promises an update or whatever, you are resigning yourself to fulfil that promise. While that seems like a good thing, it becomes extremely limiting and for a company as volatile as Valve, change is a constant. By becoming more transparent, you risk a larger amount of your player base will become hostile to the changes put forward.
People freaked over "Neato" for Christ's sake, let alone a insight into the developers' mentality and goals. If Valve came out with "We're working on a MvM update", the competitive scene would believe that they have completely abandoned competitive. If competitive is the focus, casual players will claim that the focus is killing off what made the game popular. By not speaking at all, they ideally could listen to what people are saying or reading feedback from emails, etc and work on delivering that through updates and such, which has been the method of communication from Valve for the entirety of the games history.
Nowadays though, the TF team don't have the manpower to sustain that method and because of that, the game feels abandoned and crucial fixes seem like they haven't been patched in years (Det Bug). You can't blame Valve for focusing on more lucrative or innovative ideas, especially due to their transition from Games to Hardware/Software.
Transparency only works when there are enough people there...and even then can do more harm than good. See: Overwatch.[/quote]
i was exaggerating a bit, and i was mainly talking about bug reporting. it would be nice if they at least acknowledged game breaking bugs in their game or replied to some of the numerous emails theyve been sent (since theyre supposedly reading them). i would be less mad at them if they at least explained why they havent fixed some bugs (e.g. lack of staff, hard to implement) instead of their usual silence.
bleghfarecThe tours and conversations Valve employees have with guests are entirely done in good faith, and multiple times that good faith been exploited to leak information, such as internal issue lists for Source 2 among other projects. Since long ago, Valve has never allowed video recording and/or photography inside their offices (with certain promotional exceptions), and I highly doubt they'd allow audio recording either.
are you suggesting that valve had editorial input over what potato.tf said in their summary to prevent leaks? if so, why could they not do the same with an audio recording?
bleghfarecAlso, it's important to note:
PotatoDo not read too much into any single thing; you should read the file with a 10,000 foot view.
so basically this entire document is useless because any part of it may or may not be true?
The tours and conversations Valve employees have with guests are entirely done in good faith, and multiple times that good faith been exploited to leak information, such as internal issue lists for Source 2 among other projects. Since long ago, Valve has never allowed video recording and/or photography inside their offices (with certain promotional exceptions), and I highly doubt they'd allow audio recording either.[/quote]
are you suggesting that valve had editorial input over what potato.tf said in their summary to prevent leaks? if so, why could they not do the same with an audio recording?
[quote=bleghfarec]
Also, it's important to note:
[quote=Potato]Do not read too much into any single thing; you should read the file with a 10,000 foot view.[/quote][/quote]
so basically this entire document is useless because any part of it may or may not be true?