So far I've been testing my multiplayer map using the editor, with the debugger, etc. I created some basic AI so that I could test against an opponent as I got the basics of the map set up. Now I'm approaching the point where I'd like to start testing against other players. However, before I do that, I'd like to make sure that the multiplayer portion of it is working. By that I mean that there are several preliminary setup phases that each player has to go through before the match starts, and I'd like to make sure that part stays in sync and works properly before I invite others to try it out with me.
My question is: to do this sort of local, hands-on testing, is my only option going to be to purchase another copy of SC2?!?! Free accounts can't play custom maps (except StarJeweled), so I'm trying to see if there's another way. If you ask me the solution would be for Blizzard to implement sandboxing in their editor, which would allow you run multiple isolated instances of SC2 on your local computer (all connected to your locally hosted map). Another plus is that you would be able to have a debug window open during a multiplayer game, which to my knowledge is not possible right now.
Am I missing anything or I am really going to have to part with another $50-$60 just to do some basic testing?
EDIT: I just thought of another way to put it: I'd like to do basic testing on the multiplayer capability of my map before I actually publish it.
possibilities I can think of:
- fill slots with computer players and set the first human slot to the slot which you want to test
- remote control a computer player
- publish privately and play with someone on battle.net (check mapster's irc to find people that might help you)
- verify you code by staring at it or using something like Hoare Logic.
Thanks for the suggestions Ahli. They are good ones, but since it seems like you understand my situation, I'm sure you realize that even doing all of that doesn't quite cover everything (unless you have all the time in the world to sit there and analyze the code).
So I also take that answer as a "yes", I would technically have to buy another copy of SC2 just to do this sort of preliminary testing before publishing it for other testers. How disappointing -_-
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So far I've been testing my multiplayer map using the editor, with the debugger, etc. I created some basic AI so that I could test against an opponent as I got the basics of the map set up. Now I'm approaching the point where I'd like to start testing against other players. However, before I do that, I'd like to make sure that the multiplayer portion of it is working. By that I mean that there are several preliminary setup phases that each player has to go through before the match starts, and I'd like to make sure that part stays in sync and works properly before I invite others to try it out with me.
My question is: to do this sort of local, hands-on testing, is my only option going to be to purchase another copy of SC2?!?! Free accounts can't play custom maps (except StarJeweled), so I'm trying to see if there's another way. If you ask me the solution would be for Blizzard to implement sandboxing in their editor, which would allow you run multiple isolated instances of SC2 on your local computer (all connected to your locally hosted map). Another plus is that you would be able to have a debug window open during a multiplayer game, which to my knowledge is not possible right now.
Am I missing anything or I am really going to have to part with another $50-$60 just to do some basic testing?
EDIT: I just thought of another way to put it: I'd like to do basic testing on the multiplayer capability of my map before I actually publish it.
possibilities I can think of:
- fill slots with computer players and set the first human slot to the slot which you want to test
- remote control a computer player
- publish privately and play with someone on battle.net (check mapster's irc to find people that might help you)
- verify you code by staring at it or using something like Hoare Logic.
@Ahli634: Go
Thanks for the suggestions Ahli. They are good ones, but since it seems like you understand my situation, I'm sure you realize that even doing all of that doesn't quite cover everything (unless you have all the time in the world to sit there and analyze the code).
So I also take that answer as a "yes", I would technically have to buy another copy of SC2 just to do this sort of preliminary testing before publishing it for other testers. How disappointing -_-