Quote from 
Pyro682
Pyro682Cool the engines bud.
1) Giving an exact time to the due date is silly; don't pretend you know Blizzard's Game Creating Schedule.
2)The Solution you have is a good solution. That's my point. Use it instead of trying to find something better, because your search won't come up. You wont like any of the other solutions. "If it ain't broke, don't fix it." The solution you have "Ain't broke".
3) It makes sense. Just because you don't understand it, doesn't mean it doesn't make any sense at all. If it damages BOTH the computer that youre attacking, AND the player that you have, then obviously there is a 3rd player (or computer) that you are using the scarabs with. Use the Computer that the player is fighting to fix this.
4) If patches come out rarely, that means your map will be played for a longer time. I doubt you're going to make a map that lasts eternally. Eventually, players will forget it, or it will get edited so many times that it will end up being shitty, and people will stop playing it. Does it matter whether or not that the thing that kills your map is a patch or people editing it??
1) Giving an exact time to the due date is silly; don't pretend you know Blizzard's Game Creating Schedule.
2)The Solution you have is a good solution. That's my point. Use it instead of trying to find something better, because your search won't come up. You wont like any of the other solutions. "If it ain't broke, don't fix it." The solution you have "Ain't broke".
3) It makes sense. Just because you don't understand it, doesn't mean it doesn't make any sense at all. If it damages BOTH the computer that youre attacking, AND the player that you have, then obviously there is a 3rd player (or computer) that you are using the scarabs with. Use the Computer that the player is fighting to fix this.
4) If patches come out rarely, that means your map will be played for a longer time. I doubt you're going to make a map that lasts eternally. Eventually, players will forget it, or it will get edited so many times that it will end up being shitty, and people will stop playing it. Does it matter whether or not that the thing that kills your map is a patch or people editing it??
2) Again, you missed my point. You are considering only one application, which is weapon change, while neglecting other applications that just didn't exist or had very complex solutions, such as the item application that was mentioned previously.
3) The way you phrased that sentance was not really good. Most people would agree that it was a bit confusing. Now that you've made you point clear, I can comment that it is a logical thing to do atleast to save computer slots. However, I don't remember whether the AI'd scarabs deal damage to units owned by the same player as they are, so I can't comment on how useful your suggestion is to counter the computer-damaging problem.
4) You are making the assumption that the original will be lost, which is most probably a false assumption, since databases hosted by widely known websites exist. My point of view is that a map must be playable in any patch, thus it is unimportant how many patches come out: 1 or 100, since I might not have the time to edit it even once.
That's it. I've adressed your points, and I hope this off-topicness ends here. If you want to discuss something that is not directly related to the concept I've proposed, please PM me. If you have reliable information about the 3rd point, you are more than welcome to post it here.
ADDITION:
Quote
Technically if the player owned the scarab, and the other player was unallied, the damage would still apply.
None.
