So I was trying to explain the difference between using Triggers/Script and using Data in the SC2 Map Editor but I couldn't give a good explanation of what data represents really. I said using a Data approach instead of a Scripting approach meant I just modified preexisting game data to fit my purposes. I feel this doesn't adequately explain Data and utility over Scripting/Triggers. Are any of you able to give a good explanation of what the Data Editor is, how it compares to Scripting/Triggers, and what its advantages or disadvantages are to someone who knows some programming (Python MatLab and maybe dabbles in some other programming languages) but has no knowledge of the SC2 Map Editor? I use both Data and Triggers quite a bit but I can't seem to give a good, easy to understand explanation of data use. Thanks for the help!
That is a hard question to me that I'm not able to answer. However, I can tell you that IN MY OPINION that there is nothing the trigger editor can't do that the data editor can. Many data editor's will argue the same for the vice versa - which I will object, as they will object what I just said.
Again, in my opinion, it comes down to personal preference I believe. A good mix and balance is obviously the best route to go. For example, there are things you can manipulate a unit in triggers that would take you seconds, but to get the same effect in data would take minutes/hours. And of course, vice versa. There are certain things you can just do in a matter of seconds in data, but it would take forever in triggers.
Rollback Post to RevisionRollBack
Project Rise of Nigma
To post a comment, please login or register a new account.
So I was trying to explain the difference between using Triggers/Script and using Data in the SC2 Map Editor but I couldn't give a good explanation of what data represents really. I said using a Data approach instead of a Scripting approach meant I just modified preexisting game data to fit my purposes. I feel this doesn't adequately explain Data and utility over Scripting/Triggers. Are any of you able to give a good explanation of what the Data Editor is, how it compares to Scripting/Triggers, and what its advantages or disadvantages are to someone who knows some programming (Python MatLab and maybe dabbles in some other programming languages) but has no knowledge of the SC2 Map Editor? I use both Data and Triggers quite a bit but I can't seem to give a good, easy to understand explanation of data use. Thanks for the help!
@Imperfect1987: Go
That is a hard question to me that I'm not able to answer. However, I can tell you that IN MY OPINION that there is nothing the trigger editor can't do that the data editor can. Many data editor's will argue the same for the vice versa - which I will object, as they will object what I just said.
Again, in my opinion, it comes down to personal preference I believe. A good mix and balance is obviously the best route to go. For example, there are things you can manipulate a unit in triggers that would take you seconds, but to get the same effect in data would take minutes/hours. And of course, vice versa. There are certain things you can just do in a matter of seconds in data, but it would take forever in triggers.