Starcraft II Editor — Second Look

Random fact: On the day of my last post, which was about a short story considered a brilliant piece of American literature, my blog received its lowest daily view count in more than three months (130 views). I guess the Internet is just that antagonistic towards American literature.

Today’s topic is much different: the StarCraft II map editor. Four months ago, during the beta, I was able to play around with the editor very basically, and wrote up a post comparing the SC2 editor to the SC1 and WC3 editors.

Recently I was able to mess around with the editor again, this time trying to create the basic gameplay for an AoS-type map. After all, I had plenty of experience with the WC3 editor, and the SC2 editor, as I mentioned in the linked post, is very similar.

That turns out less true than I thought. The truth is, the SC2 editor is not only far more powerful, as I had mentioned, but also far, far more complicated. Of course, diving into any new thing takes a while of getting used to, but on the SC2 editor, I spent eight hours just trying to make a hero system and setting up the map and triggers for an AoS, and didn’t even succeed in creating items or an inventory. To change even a single stat on a weapon took me a couple minutes of messing around the first time.

My new argument: While the WC3 editor and the SC2 editor look very much alike, the WC3 editor is in fact more like the SC1 editor than the SC2 editor. Actually, there is an important caveat here: I’m talking only about the Object/Data editor. For Terrain and Triggers, it still stands that WC3 and SC2 are closer.

The object editor in WC3 is essentially the unit editor of SC1 with significantly more fields, and also more tabs (not only units, but also abilities, items, doodads, destructibles, buffs). Suppose I wanted to change the damage of a Marine/Footman. In SC1 I would go to the Marine unit, and change the damage field from 6 to whatever I wanted it to be. For the WC3 Footman, the process is exactly the same.

SC2, on the other hand, is modular. So, to change the damage of the Marine, you can’t just go to the Marine unit. From the Marine, you have to find the link to the weapon, which in turn has a link to the damage. Once you’re at the damage, you can modify it.

Alright, it takes two more steps—so what? Well, this makes multi-object things WAY more complicated. Letsay I wanted to create an item that adds an aura in WC3. I would need an Item, Ability, and Buff. The Ability must known which Buff the aura uses, and the Item must know what Ability it is supposed to carry. Nice and simple. In SC2… let’s just say I haven’t figured it out yet.

Even supposing I could create an item, I would also need the inventory, which is incredibly difficult to make, at least without a very careful and detailed tutorial. Even looking at the source of another map (which was an excellent way to learn the WC3 editor) seemed to not help, because there were several inter-object links that I did not know how to make.

Anyway, I’m not saying the SC2 editor sucks or anything—I’m just saying it’s far, far more complicated than what I’m used to, and it will most likely have a long adaptation time. Even figuring out the basics is a challenging task. Right now, the editor just seems far more complex than it needs to be, but we’ll see.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s