|
|
Vatican City State1872 Posts
On April 20 2017 03:58 Mohdoo wrote:Show nested quote +On April 20 2017 03:49 rand0MPrecisi0n wrote:On April 20 2017 03:43 Mohdoo wrote:On April 20 2017 03:40 rand0MPrecisi0n wrote:On April 20 2017 03:37 Mohdoo wrote:On April 20 2017 03:35 Drake wrote:
this 1.18 is to early ... to much shit needs fixing why they do this ... More people to test --> faster improvements. vanilla 1.18 isn't the goal here. Remastered 1.18 is the goal. That is what likely has a deadline, not this. Your reasoning goes out the window once you see how many problems have already been reported in the PTR and are still in this version Problems reported on PTR does not mean they are a top priority. In the end, the vanilla version of BW is likely of very little importance to Blizzard. I mean, this is kind of a matter of fact rather than up for interpretation. When else have we ever seen Blizzard shove stuff out the door in a giant mess? Bug here, gamebreaking bug there is normal for Blizzard, but this is like an alpha version. Either they don't have a QA team (unlikely) or this is an intentionally aggressive method of meeting their more important deadline. They most likely don't have a QA team for this project, as can be seen by the state of the first PTR. They could also have a terrible one. Regardless, remastered success lies very close to vanilla, so releasing a mess of a patch is not a good idea. Surely it is an 'intentionally aggressive method', but it's also a 'horrendously retarded method' All sources close to or in anyway involved with Blizzard's classic game development have said they have a surprisingly large team. Blizzard has done QA for a long time and if the team is already large, I doubt the QA team is small or nonexistent. When you consider how much BW has been on Blizzard's radar the past 5 years, it makes sense that they would be brazen with their patching for the sake of the holy grail: BW remastered. The people Blizzard are trying to reach with BW remastered are not likely to give 2 shits about playing classic BW. I played BW on ICCUP years ago, but I don't give 2 shits about classic BW when remastered is right around the corner. I don't see any reason to waste time with 1.18 classic when 1.16 is solid and 1.18 remastered is on the horizon. There is going to be very little reason to ever play classic BW once remastered is in full gear. This is a step towards something greater.
You realize they are going to use the same code for bw 1.18 as they do for remaster, right?
If it's fucked up in "classic" bw it will be in remastered as well.
|
the input eating is still there and they launched lmfao. they might as well launch without the ability to actually load the game
|
On April 20 2017 04:59 Endymion wrote:
.... they might as well launch without the ability to actually load the game
They are working on this feature but it isn't ready yet. I'm sure they'll release it in the future though.
|
i cant launch starcraft 1.18 any ideas?
|
On April 20 2017 04:36 CrownRoyal wrote:Show nested quote +On April 20 2017 03:58 Mohdoo wrote:On April 20 2017 03:49 rand0MPrecisi0n wrote:On April 20 2017 03:43 Mohdoo wrote:On April 20 2017 03:40 rand0MPrecisi0n wrote:On April 20 2017 03:37 Mohdoo wrote:On April 20 2017 03:35 Drake wrote:
this 1.18 is to early ... to much shit needs fixing why they do this ... More people to test --> faster improvements. vanilla 1.18 isn't the goal here. Remastered 1.18 is the goal. That is what likely has a deadline, not this. Your reasoning goes out the window once you see how many problems have already been reported in the PTR and are still in this version Problems reported on PTR does not mean they are a top priority. In the end, the vanilla version of BW is likely of very little importance to Blizzard. I mean, this is kind of a matter of fact rather than up for interpretation. When else have we ever seen Blizzard shove stuff out the door in a giant mess? Bug here, gamebreaking bug there is normal for Blizzard, but this is like an alpha version. Either they don't have a QA team (unlikely) or this is an intentionally aggressive method of meeting their more important deadline. They most likely don't have a QA team for this project, as can be seen by the state of the first PTR. They could also have a terrible one. Regardless, remastered success lies very close to vanilla, so releasing a mess of a patch is not a good idea. Surely it is an 'intentionally aggressive method', but it's also a 'horrendously retarded method' All sources close to or in anyway involved with Blizzard's classic game development have said they have a surprisingly large team. Blizzard has done QA for a long time and if the team is already large, I doubt the QA team is small or nonexistent. When you consider how much BW has been on Blizzard's radar the past 5 years, it makes sense that they would be brazen with their patching for the sake of the holy grail: BW remastered. The people Blizzard are trying to reach with BW remastered are not likely to give 2 shits about playing classic BW. I played BW on ICCUP years ago, but I don't give 2 shits about classic BW when remastered is right around the corner. I don't see any reason to waste time with 1.18 classic when 1.16 is solid and 1.18 remastered is on the horizon. There is going to be very little reason to ever play classic BW once remastered is in full gear. This is a step towards something greater. You realize they are going to use the same code for bw 1.18 as they do for remaster, right? If it's fucked up in "classic" bw it will be in remastered as well.
Yes. The fact that they are going to use the same code is *the reason* classic BW is a shitshow. The best way to fix issues is to have more people testing.
I am not saying this is not shitty. I am saying that all the outrage and shit about how fucked up BW is right now is not making front page of video game news or anything like that. This is a truly minor issue within the realm of actual marketing and image and whatnot. Die hard fans who still play BW 300 years later are not enough to get an outrage thread to the top of reddit. This isn't no man's sky or something like that.
If I am a program manager and I have a really strict deadline to meet, am I really worried I will lose the TL crowd? Are any of the people complaining really at risk of throwing away the game? Let's be real, I and all of you will be playing BW 10 years from now. If I have a way to get an insane amount of QA data such that I can meet my deadline, I'm gonna pull that trigger. The spotlight will be on Blizzard in a more mainstream sense once remastered is released.
This decision sucks for us. But it is fantastic for Blizzard.
|
Netherlands5218 Posts
On April 20 2017 03:32 Airhead86 wrote:
Some weird stuff going on.. just played a 4v4 hunter on europe and i was terran and started with 3 scv and one drone. one of my allys could even move my units around ?
You probably have been playing Team Melee mode, not top vs bottom or melee.
|
Norway28739 Posts
I really don't understand how they failed to implement observer chat. Like from what I understand it's actually impossible for observers to only talk to each other.
Aside from that I actually have very few issues. Latency is super low for me, no input issues, I hope servers are combined but it's not a big deal if we end up with a useast/fish split. Hope hotkey rebinding is brought back, but no rush.. Mostly I'm just super excited about bw being revitalized, so much fun to run into people I haven't seen for a decade, and really awesome to meet people who never tried it before, but who absolutely love it now.
|
On April 20 2017 05:30 Mohdoo wrote:Show nested quote +On April 20 2017 04:36 CrownRoyal wrote:On April 20 2017 03:58 Mohdoo wrote:On April 20 2017 03:49 rand0MPrecisi0n wrote:On April 20 2017 03:43 Mohdoo wrote:On April 20 2017 03:40 rand0MPrecisi0n wrote:On April 20 2017 03:37 Mohdoo wrote:On April 20 2017 03:35 Drake wrote:
this 1.18 is to early ... to much shit needs fixing why they do this ... More people to test --> faster improvements. vanilla 1.18 isn't the goal here. Remastered 1.18 is the goal. That is what likely has a deadline, not this. Your reasoning goes out the window once you see how many problems have already been reported in the PTR and are still in this version Problems reported on PTR does not mean they are a top priority. In the end, the vanilla version of BW is likely of very little importance to Blizzard. I mean, this is kind of a matter of fact rather than up for interpretation. When else have we ever seen Blizzard shove stuff out the door in a giant mess? Bug here, gamebreaking bug there is normal for Blizzard, but this is like an alpha version. Either they don't have a QA team (unlikely) or this is an intentionally aggressive method of meeting their more important deadline. They most likely don't have a QA team for this project, as can be seen by the state of the first PTR. They could also have a terrible one. Regardless, remastered success lies very close to vanilla, so releasing a mess of a patch is not a good idea. Surely it is an 'intentionally aggressive method', but it's also a 'horrendously retarded method' All sources close to or in anyway involved with Blizzard's classic game development have said they have a surprisingly large team. Blizzard has done QA for a long time and if the team is already large, I doubt the QA team is small or nonexistent. When you consider how much BW has been on Blizzard's radar the past 5 years, it makes sense that they would be brazen with their patching for the sake of the holy grail: BW remastered. The people Blizzard are trying to reach with BW remastered are not likely to give 2 shits about playing classic BW. I played BW on ICCUP years ago, but I don't give 2 shits about classic BW when remastered is right around the corner. I don't see any reason to waste time with 1.18 classic when 1.16 is solid and 1.18 remastered is on the horizon. There is going to be very little reason to ever play classic BW once remastered is in full gear. This is a step towards something greater. You realize they are going to use the same code for bw 1.18 as they do for remaster, right? If it's fucked up in "classic" bw it will be in remastered as well. Yes. The fact that they are going to use the same code is *the reason* classic BW is a shitshow. The best way to fix issues is to have more people testing. I am not saying this is not shitty. I am saying that all the outrage and shit about how fucked up BW is right now is not making front page of video game news or anything like that. This is a truly minor issue within the realm of actual marketing and image and whatnot. Die hard fans who still play BW 300 years later are not enough to get an outrage thread to the top of reddit. This isn't no man's sky or something like that. If I am a program manager and I have a really strict deadline to meet, am I really worried I will lose the TL crowd? Are any of the people complaining really at risk of throwing away the game? Let's be real, I and all of you will be playing BW 10 years from now. If I have a way to get an insane amount of QA data such that I can meet my deadline, I'm gonna pull that trigger. The spotlight will be on Blizzard in a more mainstream sense once remastered is released. This decision sucks for us. But it is fantastic for Blizzard.
Lose the TL crowd you say... Instead they'll lose the progamers, which means they'll lose all their fans, which is the entire reason for this patch and remake in the first place.
|
Remember when Blizzard used to "it will be done when it's done"? Like, as recently as last year?
They didn't even have a release date that they shared with the public. The pressure is entirely internal.
Afreeca may be forced to walk back their ASL 4 = Starcraft Remastered statement. Blizzard has time, but they need it perfect or the progamers will not want to play it.
|
On April 20 2017 06:35 B-royal wrote:Show nested quote +On April 20 2017 05:30 Mohdoo wrote:On April 20 2017 04:36 CrownRoyal wrote:On April 20 2017 03:58 Mohdoo wrote:On April 20 2017 03:49 rand0MPrecisi0n wrote:On April 20 2017 03:43 Mohdoo wrote:On April 20 2017 03:40 rand0MPrecisi0n wrote:On April 20 2017 03:37 Mohdoo wrote:On April 20 2017 03:35 Drake wrote:
this 1.18 is to early ... to much shit needs fixing why they do this ... More people to test --> faster improvements. vanilla 1.18 isn't the goal here. Remastered 1.18 is the goal. That is what likely has a deadline, not this. Your reasoning goes out the window once you see how many problems have already been reported in the PTR and are still in this version Problems reported on PTR does not mean they are a top priority. In the end, the vanilla version of BW is likely of very little importance to Blizzard. I mean, this is kind of a matter of fact rather than up for interpretation. When else have we ever seen Blizzard shove stuff out the door in a giant mess? Bug here, gamebreaking bug there is normal for Blizzard, but this is like an alpha version. Either they don't have a QA team (unlikely) or this is an intentionally aggressive method of meeting their more important deadline. They most likely don't have a QA team for this project, as can be seen by the state of the first PTR. They could also have a terrible one. Regardless, remastered success lies very close to vanilla, so releasing a mess of a patch is not a good idea. Surely it is an 'intentionally aggressive method', but it's also a 'horrendously retarded method' All sources close to or in anyway involved with Blizzard's classic game development have said they have a surprisingly large team. Blizzard has done QA for a long time and if the team is already large, I doubt the QA team is small or nonexistent. When you consider how much BW has been on Blizzard's radar the past 5 years, it makes sense that they would be brazen with their patching for the sake of the holy grail: BW remastered. The people Blizzard are trying to reach with BW remastered are not likely to give 2 shits about playing classic BW. I played BW on ICCUP years ago, but I don't give 2 shits about classic BW when remastered is right around the corner. I don't see any reason to waste time with 1.18 classic when 1.16 is solid and 1.18 remastered is on the horizon. There is going to be very little reason to ever play classic BW once remastered is in full gear. This is a step towards something greater. You realize they are going to use the same code for bw 1.18 as they do for remaster, right? If it's fucked up in "classic" bw it will be in remastered as well. Yes. The fact that they are going to use the same code is *the reason* classic BW is a shitshow. The best way to fix issues is to have more people testing. I am not saying this is not shitty. I am saying that all the outrage and shit about how fucked up BW is right now is not making front page of video game news or anything like that. This is a truly minor issue within the realm of actual marketing and image and whatnot. Die hard fans who still play BW 300 years later are not enough to get an outrage thread to the top of reddit. This isn't no man's sky or something like that. If I am a program manager and I have a really strict deadline to meet, am I really worried I will lose the TL crowd? Are any of the people complaining really at risk of throwing away the game? Let's be real, I and all of you will be playing BW 10 years from now. If I have a way to get an insane amount of QA data such that I can meet my deadline, I'm gonna pull that trigger. The spotlight will be on Blizzard in a more mainstream sense once remastered is released. This decision sucks for us. But it is fantastic for Blizzard. Lose the TL crowd you say... Instead they'll lose the progamers, which means they'll lose all their fans, which is the entire reason for this patch and remake in the first place.
You're saying progamers will stop playing BW because of the issues with this patch? Even if it gets worked out a couple months from now?
|
so all the old accounts were deleted?
|
On April 19 2017 21:21 MildCocoA wrote:Show nested quote +On April 19 2017 21:18 TT1 wrote:On April 19 2017 21:17 RedW4rr10r wrote:On April 19 2017 21:10 TT1 wrote:On April 19 2017 21:05 CadenZa wrote:
fish server announcement: [시스템 공지] 현재 본서버에 1.16.1 클라이언트로 접속이 가능하게 수정되었습니다.
[시스템 공지] 현재 1.18 클라이언트로 블리자드 서버 접속 장애로 인해 서버 접속이 원활하지 않은 상태입니다.
fish is using 1.16.1 Fish server announcement: [System Notice] This server has been modified to be able to connect as 1.16.1 client. [System Notice] Currently 1.18 client is not connected to the server due to Blizzard server connection failure. Fish is using 1.16.1 google translate is pro. Haha, yea. This is literally the first time google translate (and naver translate) had such a good translation. Usually, if you have them more than 2 words to be translated, you get non-sense xD But ... is it true that Fish upgrades back to 1.16.1? im on fish right now, still using 1.18 4.19 20:00 부터 1.16.1 버전의 서버 접속을 허용하였습니다. (Fish allowed 1.16.1 connection)
How do you connect using 1.16.1? When I enter Fish server it forces the update.
|
On April 20 2017 06:57 Sero wrote:Show nested quote +On April 19 2017 21:21 MildCocoA wrote:On April 19 2017 21:18 TT1 wrote:On April 19 2017 21:17 RedW4rr10r wrote:On April 19 2017 21:10 TT1 wrote:On April 19 2017 21:05 CadenZa wrote:
fish server announcement: [시스템 공지] 현재 본서버에 1.16.1 클라이언트로 접속이 가능하게 수정되었습니다.
[시스템 공지] 현재 1.18 클라이언트로 블리자드 서버 접속 장애로 인해 서버 접속이 원활하지 않은 상태입니다.
fish is using 1.16.1 Fish server announcement: [System Notice] This server has been modified to be able to connect as 1.16.1 client. [System Notice] Currently 1.18 client is not connected to the server due to Blizzard server connection failure. Fish is using 1.16.1 google translate is pro. Haha, yea. This is literally the first time google translate (and naver translate) had such a good translation. Usually, if you have them more than 2 words to be translated, you get non-sense xD But ... is it true that Fish upgrades back to 1.16.1? im on fish right now, still using 1.18 4.19 20:00 부터 1.16.1 버전의 서버 접속을 허용하였습니다. (Fish allowed 1.16.1 connection) How do you connect using 1.16.1? When I enter Fish server it forces the update.
If you click cancel on the update notification you can log in.
|
Anyone having problem with disconnection while playing multiplayer? I'm getting disconnected 4 out of 5 games while playing and I know it's not my internet connection. 5 to 10 mins into the game I got disconnected.
|
Dominican Republic627 Posts
how can i revert this to 1.16.1?
|
On April 20 2017 06:57 Sero wrote:Show nested quote +On April 19 2017 21:21 MildCocoA wrote:On April 19 2017 21:18 TT1 wrote:On April 19 2017 21:17 RedW4rr10r wrote:On April 19 2017 21:10 TT1 wrote:On April 19 2017 21:05 CadenZa wrote:
fish server announcement: [시스템 공지] 현재 본서버에 1.16.1 클라이언트로 접속이 가능하게 수정되었습니다.
[시스템 공지] 현재 1.18 클라이언트로 블리자드 서버 접속 장애로 인해 서버 접속이 원활하지 않은 상태입니다.
fish is using 1.16.1 Fish server announcement: [System Notice] This server has been modified to be able to connect as 1.16.1 client. [System Notice] Currently 1.18 client is not connected to the server due to Blizzard server connection failure. Fish is using 1.16.1 google translate is pro. Haha, yea. This is literally the first time google translate (and naver translate) had such a good translation. Usually, if you have them more than 2 words to be translated, you get non-sense xD But ... is it true that Fish upgrades back to 1.16.1? im on fish right now, still using 1.18 4.19 20:00 부터 1.16.1 버전의 서버 접속을 허용하였습니다. (Fish allowed 1.16.1 connection) How do you connect using 1.16.1? When I enter Fish server it forces the update.
You can simply use two BW folder; I've my 1.18 BW on my C drive, and the 1.16 on my D hard hard drive. I'm pretty sure you can do the same on the same HD.
|
Everyone’s bitchin and complaining while I am completly satisfied with this patch  Best patch ever. No more shitty 3rd party launchers, no need for windowed mode, perfect mouse movement, everybody can host games, UTF-8 in bnet, … the list goes on and on.
|
On April 20 2017 08:11 Biolunar wrote:Everyone’s bitchin and complaining while I am completly satisfied with this patch Best patch ever. No more shitty 3rd party launchers, no need for windowed mode, perfect mouse movement, everybody can host games, UTF-8 in bnet, … the list goes on and on.
You are blizzard's target demographic. Now we just need to clone you hundreds of thousands of times and we'll have a successful launch.
|
how do we play iccup now?
|
|
|
|
|
|
|
|
EPT![[image loading]](http://i.dailymail.co.uk/i/pix/2014/12/16/2417611800000578-2875787-image-a-44_1418730438222.jpg)
