However, the data editor was incredibly daunting, and at the time there was little info on integrating Galaxy script (as well as some random limits on it). A lot of things were very similar in mechanics to the Warcraft III editor so it was not too difficult to jump in. I liked discovering things-and the editor was not that bad. I never got into the Starcraft games (too preoccupied with Warcraft, although I'm sure it is fun), so my interest in the game hung on how the modding was.Īt first, it was very interesting. When I had the beta, the only thing I was really concerned about was the galaxy editor. I've never created models or textures, but I think the vast database of warcraft 3 models vs the tiny fraction of starcraft 2 models is proof that something is wrong. I hoped after jass they would have finally outsourced this part to professionals (lua, python, javascript). Why blizzard still insists on creating their own scripting languages is a mystery to me. Blizzard has clearly mistaken "complexity" for "complication".
Every bad thing about world edit's data editor has only been amplified in the galaxy editor. Editing a single field on multiple objects is a hassle.
Instead I get 200 fields, with simple values like "gold cost" and "lumber cost" being half a screen apart. There are maybe 10 fields that I frequently edit in the data editor. You get a giant blob of data fields, some of which I still don't know what they do. The doodad properties now include X/Y/Z and custom colors in addition to the scaling we know from world edit. Texture splatting simply looks better than tiled textures. Galaxy editor is (mostly) an improvement. My problem is that the galaxy editor takes a lot of joy out of modding. Still, a lot of people are modding this game. I don't really see Arcade that much as a problem. It appears blizzard has learned *nothing* from world edit. I recently came back mostly out of nostalgia.
First note that I left Wc3 modding for a few years, exploring both SC2 modding and other games.
0 kommentar(er)
