was there any time you decided that hey, maby we should adress this issue in DOCKING FIXED BUILD:
Or was it never concidered a "Critical docking exploit", since u fixed all those apperantly...
Maby its held back for a final third Qlimatic fix in 265, where we all can play docking as we used to?
This has been attempted to be fixed multiple times, I'll make sure it's fixed correctly this time.
"B265 - Bilebomb removed from game"
There, fixed! :P
Just give Samus n the rest of the crew some yellow. Otherwise, some people won't realize that people ARE working on the bugs/game, and they do, in fact, respond. Just not many of the devs.
It doesn't work that easily, as then everything a person like me says, is officially interpreted as UWE saying it, and extra attention. While I wouldn't decline if I was offered it, it would mean I would have to be more careful to what I say and how I say it so it doesn't reflect poorly on UWE (which I do anyways)
K green color. IDC! Your post proves that people don't read some of the mods notes... so you should get some type of color as a mod. Yellow, green, purple (?!?!), IDC lol
So I wonder if this will be the build we get until PAX is over.
They'll probably release the patch tomorrow, later in the day, and have something go wrong. And since people are going to PAX they won't be able to "fix" it for 4-5 days. This is how UWE usually delivers.
The problem here is that seemingly simple fixes for severe issues are not being hot fixed (or fixed at all in a reasonable timeframe), choosing to leave the bugs in for an extended amount of time... It's normal people are not happy. Especially since we've had the same issue twice in a row. First docking, now mineshaft.
I want next patch bring back UWE server and have ASEAN server so china,thailand,hongkong players could play this game with out lag when fire shotgun againts multiple enemies
Jesus christ guys, STARCRAFT IS KOREAS NATIONAL SPORT. Those little guys are like thousands of players that are more likely than the Yanks to actually stick with a complicated game like this!
This thread makes me lawl. Can this b closed cuz we obviosly aren't talking about this build anymore? Maybe the new patch (????) will close the thread eventually... just... give a hotfix for now if the build is gonna take forever. Someone post a picture with some boobies so the devs see this!
Just give Samus n the rest of the crew some yellow. Otherwise, some people won't realize that people ARE working on the bugs/game, and they do, in fact, respond. Just not many of the devs.
It doesn't work that easily, as then everything a person like me says, is officially interpreted as UWE saying it, and extra attention. While I wouldn't decline if I was offered it, it would mean I would have to be more careful to what I say and how I say it so it doesn't reflect poorly on UWE (which I do anyways)
Oh man, so true, that's why I decided to step down when I was handed moderation on our own CoD: WaW forums too. Particularly when you are hot headed like I am, people associate a person with an entity, sadly that's how it works and not many can see past that. Good luck though, and man if I was in charge, you'd be in the house already. *raises pint*
Jesus christ guys, STARCRAFT IS KOREAS NATIONAL SPORT. Those little guys are like thousands of players that are more likely than the Yanks to actually stick with a complicated game like this!
Because that's a game where presses per minute exceed 9000 in tourneys, and unfortunately, NS2 doesn't have us do that.
Unfortunately again, our marine underlings expect us to do just that with medpaks during pubs.
The problem here is that seemingly simple fixes for severe issues are not being hot fixed (or fixed at all in a reasonable timeframe), choosing to leave the bugs in for an extended amount of time... It's normal people are not happy. Especially since we've had the same issue twice in a row. First docking, now mineshaft.
Come now, be reasonable mendasp.
If they fixed mineshaft, tram would bug out. And when they go to fix eclipse, mineshaft will break again. You can't just go fixing things willy nilly. Look what happened when they fixed docking in the first place.
Although I've been super busy working on Subnautica, after seeing the last few patches not be up a high standard due to many factors (non of which are due to the work of the PTS or Samus) I've been back taking personal interest in the next patch and the patching process.
I've been working with the PT Leads and Samus on making sure the next patch is as solid as possible. It will not be released soon, it will be released when it is ready and has been playtested for weeks after a code lockdown to help ensure it's quality and stability.
I've been working with the PT Leads and Samus on making sure the next patch is as solid as possible. It will not be released soon, it will be released when it is ready and has been playtested for weeks after a code lockdown to help ensure it's quality and stability.
I appreciate the "test until it's solid" approach.
But as that may take some weeks to complete, please release a hotfix for the most pressing issues (especially Mineshaft) first.
The build has been taking a while to get out due to the amount of work needed for it. It's a big update and we all want it to go as smoothly as possible. The patch is being tested and worked on daily and will be out once it's golden brown on top. The Steam beta Hugh mentioned will help give feedback.
Did that sound familiar?
Instead of insane promises like "under my watch, there will never be a bug again" (seriously, just read this out aloud)
While playtesters are not perfect and we occasionally do miss things, I can assure you one thing, I will do everything in my power to make sure that things are done correctly, things get done when they should, and ultimately, released bug free, no more silliness.
I've got huge respect for all contributors and their work, but this is the very definition of an unfulfillable promise. You never go full Molyneux!
Making errors is human. Everybody can oversee something (insert unfunny heartbleed joke here), this shit happens.
The question is how you deal with the inevitable.
Do you just wish it away or pretend that you are somehow above it so it doesn't apply to you?
Or do you take errors into account and put measures into place to contain and - ultimately - deal with them?
I'd much rather see a mindset that does take errors into account instead of vacuous promises which can only fail miserably.
THIS would be a promise you could actually keep:
Release a patch on a monday, then promise to wait and listen ~ 2-3 days for feedback (which should be plenty of time for things to crop up and be reported on the forum),
then release a hotfix on thursday that only contains fixes for really easy things with a huge impact like that mineshaft navigation bug.
Set aside a bit of time to deal with the easiest-to-fix-but-biggest-pain-in-the-butt stuff (basically what Matso said).
That's all I ask for.
I've been working with the PT Leads and Samus on making sure the next patch is as solid as possible. It will not be released soon, it will be released when it is ready and has been playtested for weeks after a code lockdown to help ensure it's quality and stability.
I appreciate the "test until it's solid" approach.
But as that may take some weeks to complete, please release a hotfix for the most pressing issues (especially Mineshaft) first.
I want to be clear, I never promise that a patch will be without bugs. Then there would hardly be a need in patching anymore! What happened with 263 and 264 was unfortunate and due to a number of uncontrollable factors. While I cant say the next patch will be bug-free, I will say it will be a damn sight more tested to the max than those patches.
The thing that I don't understand is why we need a new build instead of a simple hotfix for one map. Push it in to steam and end of story....
You see, the Universe needs to stay in a certain balance to retain it's cosmical harmony. Rushing to fix a map without caution will break this balance; thus, another map (by default docking) will feel the existential hole and slip into it, breaking. It takes weeks of concentrated effort for the mages at UWE to push the limits of this balance to the next level, allowing for an overall more fixed universe. (As this opposes entropy, everything is only temporary in the long term, of course. The trick is to move on to NS3 before entropy snaps back and destroys everything.)
The thing that I don't understand is why we need a new build instead of a simple hotfix for one map. Push it in to steam and end of story....
You see, the Universe needs to stay in a certain balance to retain it's cosmical harmony. Rushing to fix a map without caution will break this balance; thus, another map (by default docking) will feel the existential hole and slip into it, breaking. It takes weeks of concentrated effort for the mages at UWE to push the limits of this balance to the next level, allowing for an overall more fixed universe. (As this opposes entropy, everything is only temporary in the long term, of course. The trick is to move on to NS3 before entropy snaps back and destroys everything.)
in 10 billion years, Alien races will find b265, it will run as well as the engine test. Why? ENTROPY.
The thing that I don't understand is why we need a new build instead of a simple hotfix for one map. Push it in to steam and end of story....
You see, the Universe needs to stay in a certain balance to retain it's cosmical harmony. Rushing to fix a map without caution will break this balance; thus, another map (by default docking) will feel the existential hole and slip into it, breaking. It takes weeks of concentrated effort for the mages at UWE to push the limits of this balance to the next level, allowing for an overall more fixed universe. (As this opposes entropy, everything is only temporary in the long term, of course. The trick is to move on to NS3 before entropy snaps back and destroys everything.)
in 10 billion years, Alien races will find b265, it will run as well as the engine test. Why? ENTROPY.
They'll start playing it and call it 'Kharaa vs Aliens'
Comments
"B265 - Bilebomb removed from game"
There, fixed! :P
Thnx for the confirmation, Now I can stop creeping these forums waiting for a new patch for a few days :P
K green color. IDC! Your post proves that people don't read some of the mods notes... so you should get some type of color as a mod. Yellow, green, purple (?!?!), IDC lol
They'll probably release the patch tomorrow, later in the day, and have something go wrong. And since people are going to PAX they won't be able to "fix" it for 4-5 days. This is how UWE usually delivers.
You won't stop creeping around here. You can't help it!
Jesus christ guys, STARCRAFT IS KOREAS NATIONAL SPORT. Those little guys are like thousands of players that are more likely than the Yanks to actually stick with a complicated game like this!
Literally.
Oh man, so true, that's why I decided to step down when I was handed moderation on our own CoD: WaW forums too. Particularly when you are hot headed like I am, people associate a person with an entity, sadly that's how it works and not many can see past that. Good luck though, and man if I was in charge, you'd be in the house already. *raises pint*
Because that's a game where presses per minute exceed 9000 in tourneys, and unfortunately, NS2 doesn't have us do that.
Unfortunately again, our marine underlings expect us to do just that with medpaks during pubs.
So win
If they fixed mineshaft, tram would bug out. And when they go to fix eclipse, mineshaft will break again. You can't just go fixing things willy nilly. Look what happened when they fixed docking in the first place.
Are you calling UWE liars?
I've been working with the PT Leads and Samus on making sure the next patch is as solid as possible. It will not be released soon, it will be released when it is ready and has been playtested for weeks after a code lockdown to help ensure it's quality and stability.
But as that may take some weeks to complete, please release a hotfix for the most pressing issues (especially Mineshaft) first.
Lemme quote a certain Obraxis, re: build 263
Did that sound familiar?
Instead of insane promises like "under my watch, there will never be a bug again" (seriously, just read this out aloud)
I've got huge respect for all contributors and their work, but this is the very definition of an unfulfillable promise. You never go full Molyneux!
Making errors is human. Everybody can oversee something (insert unfunny heartbleed joke here), this shit happens.
The question is how you deal with the inevitable.
Do you just wish it away or pretend that you are somehow above it so it doesn't apply to you?
Or do you take errors into account and put measures into place to contain and - ultimately - deal with them?
I'd much rather see a mindset that does take errors into account instead of vacuous promises which can only fail miserably.
THIS would be a promise you could actually keep:
Release a patch on a monday, then promise to wait and listen ~ 2-3 days for feedback (which should be plenty of time for things to crop up and be reported on the forum),
then release a hotfix on thursday that only contains fixes for really easy things with a huge impact like that mineshaft navigation bug.
Set aside a bit of time to deal with the easiest-to-fix-but-biggest-pain-in-the-butt stuff (basically what Matso said).
That's all I ask for.
I want to be clear, I never promise that a patch will be without bugs. Then there would hardly be a need in patching anymore! What happened with 263 and 264 was unfortunate and due to a number of uncontrollable factors. While I cant say the next patch will be bug-free, I will say it will be a damn sight more tested to the max than those patches.
I ♥ you guys
You see, the Universe needs to stay in a certain balance to retain it's cosmical harmony. Rushing to fix a map without caution will break this balance; thus, another map (by default docking) will feel the existential hole and slip into it, breaking. It takes weeks of concentrated effort for the mages at UWE to push the limits of this balance to the next level, allowing for an overall more fixed universe. (As this opposes entropy, everything is only temporary in the long term, of course. The trick is to move on to NS3 before entropy snaps back and destroys everything.)
in 10 billion years, Alien races will find b265, it will run as well as the engine test. Why? ENTROPY.
They'll start playing it and call it 'Kharaa vs Aliens'