Hey everyone. I have created this Multitasking Trainer map which I'm now trying to publish on b.net.
The map works fine when I test it through the editor but when I try to run published versions through battle.net, the loading screen freezes when the bar is about 3/4 full for about 5 minutes or so an then the map is loaded, instantly giving me a "You have been Dropped" message.
Has anyone encountered this problem before or have any tips on how to fix it?
I suspect it may have to do with how players and/or game variants are set up even though I have followed all the instructions on this thread.
(In case anyone wants to check the map, v0.941 is the last working version with no b.net settings at all and v0.95 is the version I'm trying to publish with game variants set up)
I would really appreciate any help since I've been stuck trying to fix this for a couple of days T_T
If you look for mistakes you'll probably find quite a few since I learned how to use the editor making this map :)
Still, the map works perfectly fine when I test it offline... And deleting these action doesn't fix the problem unfortunately, I just published it without them.
It is public on EU so you can try it for your self if you have an EU account.
You also need to not touch the controller in the attributes. You can set those in the player properties.
Don't touch (Player Controller)
instead:
Player Properties -> computer
Also don't touch (Premade Game)
Easiest way to troubleshoot your map btw is to publish an alternative version with all the triggers disabled. It'd be nice to know where exactly the problem lies. You can narrow it down step by step.
Don't be surprized when it turns out to be your map's name. It happens. (In which case unpublishing and republishing could help, but first try the alternate solution)
Hey everyone. I have created this Multitasking Trainer map which I'm now trying to publish on b.net.
The map works fine when I test it through the editor but when I try to run published versions through battle.net, the loading screen freezes when the bar is about 3/4 full for about 5 minutes or so an then the map is loaded, instantly giving me a "You have been Dropped" message.
Has anyone encountered this problem before or have any tips on how to fix it?
I suspect it may have to do with how players and/or game variants are set up even though I have followed all the instructions on this thread.
(In case anyone wants to check the map, v0.941 is the last working version with no b.net settings at all and v0.95 is the version I'm trying to publish with game variants set up)
I would really appreciate any help since I've been stuck trying to fix this for a couple of days T_T
Taking a look at it now, presuming its the map in your Maps list.
Thanks! I just uploaded v0.95 that contains all the game variant settings I'm using.
Why are those melee actions in there? Your map is not a melee map. If you don't initialize it as melee, it won't have defeat conditions.
Melee - Disable Defeat melee option for player 1
@Siaon: Go
If you look for mistakes you'll probably find quite a few since I learned how to use the editor making this map :)
Still, the map works perfectly fine when I test it offline... And deleting these action doesn't fix the problem unfortunately, I just published it without them.
It is public on EU so you can try it for your self if you have an EU account.
Under Game Variants, you need to give your Variant a description, it can't be empty.
Under attributes, you need to not touch Game Mode.
Under Player properties, why is one player set to none? Get rid of it.
@Siaon: Go
Thanks so much for your time Siaon. Unfortunately I made all the changes you suggested and it still doesn't work. Any other ideas?
I'll upload the new version with said changes right now in case you want to have a look at it.
@stettcl: Go
You also need to not touch the controller in the attributes. You can set those in the player properties.
Don't touch (Player Controller)
instead:
Player Properties -> computer
Also don't touch (Premade Game)
Easiest way to troubleshoot your map btw is to publish an alternative version with all the triggers disabled. It'd be nice to know where exactly the problem lies. You can narrow it down step by step.
Don't be surprized when it turns out to be your map's name. It happens. (In which case unpublishing and republishing could help, but first try the alternate solution)