FOR THE ALLIANCE! jk, anyways guys, I've got this little problem that most of you have already solved I bet. So if I want to add a unit to player 1, you just put in the triggers Create 1 unit for player 1... blah blah. Right? BUT, in game, this changes, now if I want to give a certain player a unit, or anything. How do I this? Divide each player on Teams? At least that's what I heard. Or if you have another suggestion I'm all ears!
Problem: When you create a unit for player 1 in test document, it isn't the same as creating a unit for player 1 but playing WITH another user. Since it randomizes (I believe), the player numbers.
YES, EXACTLY! The second idea is the same that I was gonna do. Sorry for the excitement! Welp, anyways, should I do it? Should I use this idea? Because I don't know if it really randomizes, and if it doesn't I'll just be doing extra work. But I guess I'll do it just in case.
Yeah I tend to just use loops in my maps to search all or active players for certain conditions rather than storing player attributes in records. Because player counts can't be more than 14 anyway, there usually isn't a pressing need to keep things more efficient by using a direct designation and avoiding the loop. I find this helps avoid many bugs that may arise from improper player designations and other mistakes on my part. That's just my preference, though.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
FOR THE ALLIANCE! jk, anyways guys, I've got this little problem that most of you have already solved I bet. So if I want to add a unit to player 1, you just put in the triggers Create 1 unit for player 1... blah blah. Right? BUT, in game, this changes, now if I want to give a certain player a unit, or anything. How do I this? Divide each player on Teams? At least that's what I heard. Or if you have another suggestion I'm all ears!
Are you asking how to give a unit from one player to another?
If so, use the "Change Owner" action.
@Trieva: Go
Alrighty.
Problem: When you create a unit for player 1 in test document, it isn't the same as creating a unit for player 1 but playing WITH another user. Since it randomizes (I believe), the player numbers.
How do you get around this?
@joemart06: Go
It randomized players in SC1, but it doesn't in SC2.
@Trieva: Go
YES, EXACTLY! The second idea is the same that I was gonna do. Sorry for the excitement! Welp, anyways, should I do it? Should I use this idea? Because I don't know if it really randomizes, and if it doesn't I'll just be doing extra work. But I guess I'll do it just in case.
Yeah I tend to just use loops in my maps to search all or active players for certain conditions rather than storing player attributes in records. Because player counts can't be more than 14 anyway, there usually isn't a pressing need to keep things more efficient by using a direct designation and avoiding the loop. I find this helps avoid many bugs that may arise from improper player designations and other mistakes on my part. That's just my preference, though.