|
Hello! I play a lot of custom games and I have noticed since 3.13 (maybe before but I don't recall) that it seems spawn locations are no longer randomized.
For example, on Ascension to Aiur , if you create a custom game and are in the top slot in the lobby, you will always be in the top left position on the map. This seems to hold true for all maps in Melee settings. Even in old 4 player maps. Since every ladder map is currently 2 player it's not a huge deal for balance. But, from what I understand, starting positions used to be randomized and didn't correlate 1:1 with lobby slots. You could spawn in either top or bottom independent of your lobby slot.
I just wanted to put this out there. I am not sure if it impacts 2v2 or ladder play as I haven't had a huge sample of that.
Thank you! I am made a copy of this thread on the battlenet forums: https://us.battle.net/forums/en/sc2/topic/20754805551#1
|
Is that on every Map? If so, this would be a big deal, at least for terran. On Abyssal for instance, your whole strategy can be influenced. If you spawn top your add-ons are "outside" of the wall and are easier snipable. Kind of a biggie. Can anyone confirm?
|
I have gotten both spawns. Just tested it.
If you go to the twitter thread, I also tested cacuts valley.
|
thanks for checking man. i guess that is why we post these things to check with others. ill try to see if i cant figure out what is happening to me...
edit:
I checked. I did about 20 games with a buddy. The first 15 of em we were locked starting spots and he was believing me. Then i got stuck, couldn't make a game. I had to relog, and when I did, we stated getting mixed spawns. I am now thinking something was wrong with my client. Odd.
thanks guys (previously, i had about 100 games in Aiur that I was top left. all in a row.)
|
Funnily enough my client locked when I was getting them all in a row, then after I had to relog it was fixed...
|
I was just labbing a build vs AI when I realized I must have spawned in the upper left at least 2 dozen times :p
Something must get stuck. May only be a "solo" game issue.
|
|
|
|