|
Author |
Thread Statistics | Show CCP posts - 5 post(s) |
Lurchasaurus
SVER True Blood Public Disorder.
895
|
Posted - 2013.08.21 08:05:00 -
[1] - Quote
0bi wan-jacobi wrote:CCP Cmdr Wang wrote:When we want you to? Now go back to killing clones please. It'll be out soon enough either this week or the next at the latest. Wow this better be good. Or your going to get hated on like never before. People dont like being told to wait. Not when a games in this state. I have my hope, don't let me down i still have faith (very very very very very small but hey lol).
he actually gave a time when he asked.....im pretty sure the dev is being pretty awesome here....and trying to be funny.
loosen your belt a little and chill |
Lurchasaurus
SVER True Blood Public Disorder.
895
|
Posted - 2013.08.21 09:54:00 -
[2] - Quote
this boggles my mind. i feel bad for ccp, the dust community must be the biggest group of whiny entitled brats ever. Wang, i applaud you for speaking your mind in a funny, yet true manner.
CCP has a game that they are trying to make and its funny how people demand change after change only to get them and then blast CCP for not bringing new content....they only have 24 hours in their day people...
frankly, while it would be unprofessional for CCP to tell people to **** off, this is a game community and i think it is fine here and there are certainly many people who think they are the bees knees and they just need to be put inot a locked basement with the key destroyed |
Lurchasaurus
SVER True Blood Public Disorder.
896
|
Posted - 2013.08.21 10:07:00 -
[3] - Quote
Anmol Singh wrote:CCP Cmdr Wang wrote:When we want you to? Now go back to killing clones please. It'll be out soon enough either this week or the next at the latest. :( i cant kill anybody... i accidentally speced into vehicles...
lol....im sorry.....so much yes |
Lurchasaurus
SVER True Blood Public Disorder.
898
|
Posted - 2013.08.21 10:36:00 -
[4] - Quote
Another Heavy SOB wrote:Lurchasaurus wrote:Anmol Singh wrote:CCP Cmdr Wang wrote:When we want you to? Now go back to killing clones please. It'll be out soon enough either this week or the next at the latest. :( i cant kill anybody... i accidentally speced into vehicles... lol....im sorry.....so much yes Maybe you should talk to a good Vehicle specialist like Mary Sedillo? He doesn't seem to have a problem killing anything.
youre pretty funny. i do pretty fine in tanks thanks. never heard of this mary sedillo guy, n im one of those good vehicle specialists your talking about from over a year ago in beta...w/e welcome to the forums |
Lurchasaurus
SVER True Blood Public Disorder.
899
|
Posted - 2013.08.21 10:53:00 -
[5] - Quote
Another Heavy SOB wrote:Lurchasaurus wrote:Another Heavy SOB wrote:Maybe you should talk to a good Vehicle specialist like Mary Sedillo? He doesn't seem to have a problem killing anything.
youre pretty funny. i do pretty fine in tanks thanks. never heard of this mary sedillo guy, n im one of those good vehicle specialists your talking about from over a year ago in beta...w/e welcome to the forums Maybe if STB actually fought their own battles instead having AE ring you'd have had your tank destroyed by him. At a 7.2 K/D I'd say he's pretty damn good, especially considering vehicles can't kill anything....
thats all he has? look, i havent played dust for a while now but while i was active i never had someone else fight my own battles for me, quite the opposite. in fact i have steamrolled enemy tanks while being outnumbered more times that not. I welcome you to watch the videos we have of the open beta tourney. on film, you know....youtube and all that.
dont get uppity with me kid, your barking up the wrong tree. im one of the orginal tankers. |
Lurchasaurus
SVER True Blood Public Disorder.
899
|
Posted - 2013.08.21 11:04:00 -
[6] - Quote
Acturus Galaxy wrote:TEXA5 HiTM4N wrote:CCP Cmdr Wang wrote:BARDAS wrote:What are these patch notes that people speak of? Do you by chance mean the arcane scribble that magically appears 24 hours before a change takes place thus preventing any meaningful feedback from the community which could potentially prevent problems before they occur? If so yeah I may have heard about those once a while back. Its a shame we don't see them sooner for the aforementioned reason. How are you going to give us meaningful feedback before you even try the changes? Or is your brain so awesome that you can look into the future? And while we are on the subject of feedback, guys, a few one liners and a catch word here and there really doesn't help. If you really care about improving the game, then please structure your feedback in a way that will: 1. List specific issues and the circumstance when it happened. We then put these in a weekly report and discuss them with the dev team on ways to address this. 2. Provide insight on why you think this is happening, if you can. Translation, explain as best as you can on how to reproduce the error/bug you encountered. The patch notes are there to let players know what changes are coming so they can plan their gameplay accordingly, not so that people can theory craft before hand on how things will work before they actually try it. Sometimes the changes yall make look pretty bad on paper and usually translate into something very stupid ingame. example would be the core flaylock. a lot of hassle could have been avoided if yall showed us the stats before you released that super OP weapon. We all know that took nearly 2 months to fix. Honestly, did yall look at that weapon and go "Oh yes this weapon seems balanced"? even though it had the most dps out of every weapon, less pg and cpu to use, more splash damage and radius than a proto missile launcher or mass driver, and above all it was a sidearm. You're real close to being called "BLAM 2" The flaylock was not OP until the explosion hit detection was fixed. The weapon probably seemed fine during testing and there was no problems with this being OP until the explosion fix. The explosion fix also changed the MD from being UP to being good. You are too quick to make conclusions on this matter. I am confident that CPP does playtest new content. I would suspect the biggest problem is anticipating player behavior. There would be no problems with current tanks if only few skilled into proto AV. How should they balance it properly before release, not knowing our behavior? Should tanks be balanced around all players having access to proto AV, to 10% having proto AV? This can vary greatly from match to match. One match having unstoppable tanks while the next getting tanks destroyed shortly after they are deployed. I would say the best option is to try and balance it on paper and during their playtesting. And later update its characteristics if needed depending on how it is deployed in pub matches. And I believe 1-2 months of real testing is needed to properly gather statistics and seeing if it finds a proper use not being OP or UP.
more importantly, CCP has a vision of the game and develop it as such. the problem comes when you get the basement dwelling 20 hours a day gamer who would rather exploit the same op mechanic over and over again, sacrificing fun for a stat. this is where you get the crazy remote explosive spam like in the E3 build, where they were basically high splash radius grenades. dont underestimate the power of a guy looking for a way to exploit ****. you cant make a game based on the one ****** guy....well....maybe.... |
Lurchasaurus
SVER True Blood Public Disorder.
899
|
Posted - 2013.08.21 11:23:00 -
[7] - Quote
TEXA5 HiTM4N wrote:Acturus Galaxy wrote:TEXA5 HiTM4N wrote:CCP Cmdr Wang wrote:BARDAS wrote:What are these patch notes that people speak of? Do you by chance mean the arcane scribble that magically appears 24 hours before a change takes place thus preventing any meaningful feedback from the community which could potentially prevent problems before they occur? If so yeah I may have heard about those once a while back. Its a shame we don't see them sooner for the aforementioned reason. How are you going to give us meaningful feedback before you even try the changes? Or is your brain so awesome that you can look into the future? And while we are on the subject of feedback, guys, a few one liners and a catch word here and there really doesn't help. If you really care about improving the game, then please structure your feedback in a way that will: 1. List specific issues and the circumstance when it happened. We then put these in a weekly report and discuss them with the dev team on ways to address this. 2. Provide insight on why you think this is happening, if you can. Translation, explain as best as you can on how to reproduce the error/bug you encountered. The patch notes are there to let players know what changes are coming so they can plan their gameplay accordingly, not so that people can theory craft before hand on how things will work before they actually try it. Sometimes the changes yall make look pretty bad on paper and usually translate into something very stupid ingame. example would be the core flaylock. a lot of hassle could have been avoided if yall showed us the stats before you released that super OP weapon. We all know that took nearly 2 months to fix. Honestly, did yall look at that weapon and go "Oh yes this weapon seems balanced"? even though it had the most dps out of every weapon, less pg and cpu to use, more splash damage and radius than a proto missile launcher or mass driver, and above all it was a sidearm. You're real close to being called "BLAM 2" The flaylock was not OP until the explosion hit detection was fixed. The weapon probably seemed fine during testing and there was no problems with this being OP until the explosion fix. The explosion fix also changed the MD from being UP to being good. You are too quick to make conclusions on this matter. I am confident that CPP does playtest new content. I would suspect the biggest problem is anticipating player behavior. There would be no problems with current tanks if only few skilled into proto AV. How should they balance it properly before release, not knowing our behavior? Should tanks be balanced around all players having access to proto AV, to 10% having proto AV? This can vary greatly from match to match. One match having unstoppable tanks while the next getting tanks destroyed shortly after they are deployed. I would say the best option is to try and balance it on paper and during their playtesting. And later update its characteristics if needed depending on how it is deployed in pub matches. And I believe 1-2 months of real testing is needed to properly gather statistics and seeing if it finds a proper use not being OP or UP. I understand what hes saying. There is no way to predict how we are going to end up playing, but I think some player feedback on stats would help out tremendously the headache when they release new features and updates to our inventory. Look at what team grit did when they first announced PC. they had nearly full transparency and the community pointed out a flaw that would have a corp make endless isk. as for the proto av vs tanks. In my opinion having vehicles without its proto counter part seems like a decision that was not made with good foresight. Think of releasing proto weapons and only having standard suits.
fully aware of the vehicle thing. fact of the matter is this:
1 - predicting player interaction is impossible, therefore build game to internal vision for game 2 - playtesting inside CCP is plenty. enough to make sure thins dont clip and guns fire, but why waste internal time testing balance with a subpar sample group when a single hour of a patch being out provides thousands of hours of data. trust me, they want to know balance on a new wep? put it our for a couple minutes and they get essays telling them what they did wrong along with a nice death threat or two. 3 - transparency is nice when they are working on new stuff. problem is, th dust community is pouting so much CCP has been forced to put all they stuff they want to do aside just to sate these whiny entitled kids. balance passes dont require transparency, they are just new numbers that come when they come. if we are getting a new suit, you can bet we will get a dev blog on it. |
|
|
|