SC2Mapster

Let me preface that my current arrangement is somewhat unsual.

I work as part of a team. I'm a programmer by hobby and by profession. I occasionally submit ideas for consideration to my designer and we do talk about things and discuss concepts. However, I primarily do the game logic and implementation. I've implemented the UI, according to mockups, data and triggers. I created a template for my designer when creating classes and enemy units so that he filled out the necessary details. The designer implemented the terrain. All custom model work is done by a 3rd person.

As for ordering, there really isn't one for me, I simply have a specification and implement it accordingly, while giving feedback on technical difficulties or concerns while implementing things.

Since I'm horrible with regards to data: I just let the pros deal with that mes, and I just worry about the terraining aspect.

I generally do it as so: little bit of terrain, vague tileset brushing, throw in every doodad that I think I may need in one of the corners of the map, select a few to get an idea/feel for the map, continue with terraining till satisfaction (I reframe from using cliffset). Additionally: continue with doodad placement till I feel confident with adding more tileset bushing, add the final touches of aesthetic doodads, and then final touch ups with tileset brush.

I've had maps that I've nearly completed, then completely scrapped since the final idea wasn't appealing enough to share.

An example of my latest map for another user: http://imgur.com/a/uWXIO

I make all of my maps based on a technical idea. I just want to see if something can be done with the editor, and the editor is powerful enough that most of the time, it can be done. And its very fun to get a technical idea working. A lot more fun than actually playing it.

For example in my last few maps. I made a Time Wars map, the idea is to be able to click back in time and replay the current battle from that moment on. It was an incredible triggering feat to pull that off, pretty proud of it.

Also had another idea about playing on a 3d Earth map instead of flat 2d. Made a simple Risk boardgame gameplay for it. The technical aspect is pretty immense. The map uses a lot of art animations and triggering to pull off the 3d map.

Also had an idea of a 3d ship game like Dreadnoughts. Also used a lot of combined art and triggering to get it working. The ship moves in 3d with height adjustments. And each turret has its own arc of fire and can rotate to track the target. Pretty neat.

Also just finished another map a few days ago. Its based on the idea of using real images as terrain. It was first used in World War 3, but I thought of an improvement for it. Instead of just one image, why not combined multiple hi-res images into one gigantic map? The end result is awesome. One giant map made up of lots smaller images.

Even my early maps are all based on some technical idea. Kingdom Rush was actually based on the idea of recording achievements in game and display them with the tooltips. It was one of my first maps that was made a few months after WoL release. Back then, it was quite an achievement to be able to do something simple as that. :)

I got tons of technical ideas and its so fun to get it working and see it in action. I release most of my maps once done, but they don't get played so usually I just remove them awhile later.

I devise a gameplay idea, add details till it work in my head. I can literally close my eyes and play the game as if it was already done.

Then I work on programming aechitecture. Again, I'm thinking through each detail from high abstract scale to the functions and variables.

Then I just implement everything, in order of independency. If a system requires no other systems to work, I start with it. Because independent things are easier to debug, so they become reliable, and safe for other systems to depend on them.

So, terrain usually go first. Then data. Then triggers and ui.

This way I created 6 big maps, zero of them are unfinished. The same way I go while creating standalone games with Unity. But code architecture in case of Unity is more important, so before starting to code, I create a bunch of lityle prototypes of subsystems, and pick the best way to code for each peace of functionality.

What is the most important thing to guarantee the map/game won't be abandoned halfway? Being obsessed with the gameplay idea. "This is a fun mechanics, I wanna try it" - may motivate for a week. You need an idea of "fuck, this is so perfect and ginus! I want it to be done si had!" - this may keep you motivated longer.

So, it may have a sense to collect a bunch of ideas until you come up with the one. Instead of rushing into the first one you got.

Turning books into playable campaigns:

1) I find a story with enough scenes that could be turned into playable maps, preferably with a story I like.

2) I divide the story into sections that will make up the playable maps and also come up with general gameplay ideas for each map and the theme for the entire campaign. I don't really go into details for any map until I start with a map. I rarely move on to another map until I am done with a work-in-progress map.

3) Work on data and triggers until I have a playable prototype with very basic gameplay, but lets me test all basic ideas.

4) Work outside the editor: Come up with content and the map design. Lately I use photoshop more and more for the map layout. Come up with mission objectives and create a transscript for all cinematics, loading screens and other text. This does not include ingame transmissions or tips that are only there to teach players how the map works.

5) Work solely on the gameplay inside the editor. I work iteratively, meaning I constantly change elements of gameplay and map layout until I am satisfied. I try to get others to play the map.

6) When the gameplay is finished I work on terrain and cinematics.

7) I repeat steps 3 to 6 for all maps of the campaign. Once they are done I continue to finetune each map until I am exhausted and fed up ;) (In theory I could work on any map for decades and still not be 100% satisfied).

Bonus) I take a very long break, gather feedback and then update the campaign. I prefer few big updates over many small ones, as I believe they are a better incentive to re-experience a campaign. The exception is when I find very annoying/game-breaking bugs.

I don't make maps, but I do make something so I have several thought processes similar to everyone here, just not as technical. I think the most important things you need to plan for are fluctuations in motivation. Odds are, when any of us start making whatever it is we're making, we are super motivated and excited. Utilize these high points to plan for the inevitable dips of when you'll feel like not doing anything. For me, it's quite easy because I have a schedule and there are people who expect certain types of videos on certain days. I've found it's very easy for inspiration and motivation to slip away if you succumb to that first big dip of "Nah, not today". Obviously, not having time is one thing, but it you're very bored, but still lack the motivation to keep working on a project you were very excited about a week ago, you'll need to think hard on if you want to just completely abandon it and not stress yourself out months later as you realize you've gotten nowhere. Otherwise, setting milestones for yourself helps a lot - mine are easy to follow with an upload schedule, but mapmakers would require more robust objectives that I'm not really well-versed enough to make.

Next, don't make promises to people you can't keep. I have not fully fallen into this trap, but have come very close. Luckily, pretty much all content creators here are very friendly and understanding, but be wary of expectations set on you by others, especially if you are part of a team. It's good to set those milestones, but don't over-commit to something that you can't complete within a reasonable time frame for a hobby of yours. In fact, set your own milestones according to your own schedule of free time and be transparent with others. This sets their expectations and will incentivize you to keep working!

For example, I occasionally get miscellaneous asks to make videos for things. Rather than saying "Sure, I'll do it eventually", or just never responding, I will try to explain my Monday, Wednesday, Friday upload schedule, why it's important to not upload more than that per week due to long term limited content, why I need more time than the day after a map is released, and give at least a general time frame in terms of weeks (give or take) of when they can expect to see their stuff. You can set these expectations for yourself, or for the team you are on. Anyway, I hope this wasn't too off the rails!

I've only made one map, and this is the process I used: Make a document file, create core trigger systems, make very basic terrain, make functional data-work, continue work on data & triggers, make first gameplay prototype, polish data & triggers, polish terrain, and lastly put final touches.

Of course, there were quite some flaws I made in my process (such as not thoroughly thinking some things in my documentation and many times deviating from it). I think my process would be much smoother now, after having finished my first semester in college. Learned more about software engineering, which can be applied here.

Though I don't think I'll be making any maps in the near future, so I probably won't be putting my new process to practice anytime soon. :P