- Joined
- Feb 9, 2015
- Messages
- 108
So the skeleton archer arena went through? I love it already heh.
Please go and finish that murloc map aswell, give it some love!
Please go and finish that murloc map aswell, give it some love!
(4 ratings)
So the skeleton archer arena went through? I love it already heh.
Please go and finish that murloc map aswell, give it some love!
Thanks for the ratingJust played a quick game with my friend, we were able to "obtain" the item by "killing" the drake.
Was a fun quick 1v1, you have excess inventory slots (as only 1 obtainable item exists if I'm not mistaken). You should remove players who aren't playing. Other than that the map was a blast. Also why is the skull uspide down?
Imho, I find it quite embarrassing that blizzard left this issue in the game for over half a year already since they acknowledged it, especially when it should be so easy to fix (if it's not easy, I'd love to hear why). I watched Abelhawk's stream on youtube and seeing him struggling and unable to start this map was very frustrating for me to see.Please fix the team 1 for everybody issue so it can be started in multiplayer.
Great map, congrats on 3rd place!
Imho, I find it quite embarrassing that blizzard left this issue in the game for over half a year already since they acknowledged it, especially when it should be so easy to fix (if it's not easy, I'd love to hear why). I watched Abelhawk's stream on youtube and seeing him struggling and unable to start this map was very frustrating for me to see.
This isn't even the only map that is affected. Another recent example I came across is Forest Party. And before you say this isn't an issue because map authors can easily fix it themselves, or that it is their responsibility, be aware that older maps with this same problem may be protected and its authors unreachable.
I'd also like to mention that the workaround for mapmakers of making a second force can affect gameplay, for example you are unable to share control through the F11 menu with players from a different force, even when everyone is intended to be on the same team.
In conclusion, it is my opinion that blizzard should deal with this issue, not mapmakers.
I don't remember the time when you could actually start 1 team only maps in multiplayer.And before you say this isn't an issue because map authors can easily fix it themselves, or that it is their responsibility, be aware that older maps with this same problem may be protected and its authors unreachable.
I'm sorry but we can't just leave stuff in Maps which isn't playable. We'll set it to awaiting update until either Blizzard or the author fixes the issues.In conclusion, it is my opinion that blizzard should deal with this issue, not mapmakers.
I don't remember the time when you could actually start 1 team only maps in multiplayer.
I'm sorry but we can't just leave stuff in Maps which isn't playable. We'll set it to awaiting update until either Blizzard or the author fixes the issues.
As someone who started playing this game around 2013, I don't remember the time when you could NOT start 1 team only maps in multiplayer. This issue only resurfaced because blizzard got rid of hosting bots.I don't remember the time when you could actually start 1 team only maps in multiplayer.
I don't know... Just tried local area network on 1.27 with one team only and it says: "All players are currently on the same team; You must have at least two team setup to start the game."As someone who started playing this game around 2013, I don't remember the time when you could NOT start 1 team only maps in multiplayer. This issue only resurfaced because blizzard got rid of hosting bots.
I've always been playing on the latest version. The reason I never ran into this issue before patch 1.30.2 is because I always played using hosting bots, with which you can start a map even when there's only one team.I don't know... Just tried local area network on 1.27 with one team only and it says: "All players are currently on the same team; You must have at least two team setup to start the game."
It's the same thing as with 1.31.1. I have no idea what version you've been playing, maybe 1.26?
Bottom line is, the game wasn't made for 1 team only multiplayer launch. That was possible by external means. I don't consider this Blizzard's fault then. They didn't break their own game regarding this matter.I've always been playing on the latest version. The reason I never ran into this issue before patch 1.30.2 is because I always played using hosting bots, with which you can start a map even when there's only one team.
This may be true for melee maps, but I don't see why this limitation should exist for custom maps.the game wasn't made for 1 team only multiplayer launch