Paladins

I've started my next Level Design and I wanted to share it. I'm designing and building a Paladins payload map in Unreal 4.

I haven't played that much Paladins, so I started by pulling up as many overhead pictures and blueprints of current payload maps as I could. I looked through them, counting tiers of elevation, corners, cutoffs, ect... until I got a sense of what the Paladins LDs considered viable for the game.

After this I sat down to brainstorm some locations and concepts that I didn't see in any Paladins map. I settled on Swamp pretty quickly. I wanted to do something interesting the map so I started to poke at what I could add (in terms of interactive environment). Swamps make me think of poisons and sinking into the muck so I thought I'd make some sort of poisonous environment piece.

Of course swamps aren't actually that toxic on their own. They could also be a bit monotonous. So I put a big sci-fi factory in the middle of the swamp, pumping out toxic sludge, and making for a nice visual contrast. After brewing up a few concepts and set piece ideas, I went to Draw.io to make a sketch. I have and love my whiteboard too, but I'm trying to be modern.

This was the first attempt:

The stuff on the right in a hill with ridges marked. The big curves are a river path. The payload itself is an oversized airboat that's big enough for multiple players. There is a very tiny little human shape on the boat for size.

I looked at this and thought "Meh, it's ok." I felt like the factory was too far out of the way, and would only be a visual not a playable space. I didn't like that. But the factory was BIG; how could I get it into the map? So I put it in the middle.

I liked it, a lot. It was still a simple Paladins map, but it took one simple rule and twisted it, it was no longer back and forth along a line. Instead, we're going back and forth through a circle we can cross.

I don't know how it's going to be different, but I have no doubt that this small shift is going to make for some very different game play. We'll see what it looks like in grey box.

New Frontiers

This is a short post simply to declare, I'm finally starting to seriously study C#. It's awesome.

It started a few weeks ago when I was cleaning up Flux Firefight, I top-down shooter I made with Lukas Nikola in grad school. There were a few bugs inhibiting me from getting a clean play through video, so I said, "I'll fix them."

And I did. It wasn't easy. Some simple tasks took hours, but I did it. It was really satisfying.

Now I'm programming a text-based RPG while following this tutorial: https://scottlilly.com/learn-c-by-building-a-simple-rpg-index/. It's been great. I've been changing things up too, both to experiment with what I'm learning, and to fit the story inspiring the game.

I'm going to finish the tutorial at least, we'll see about finishing the game. Rick Hall suggested that if I'm going to learn to program, I should do something ambitious. I'm thinking about programming a pass&play version of Settlers of Catan. I think that's attainable, and it's definitely more ambitious than a text-based rpg. 

Shepherd of Shepherds

I know it's been a long time since my last post, color in your own excuses.

I'm a a design lead now on a lovely little game called Oracle. We're more than half way through production and I'm working with a team of just one other designer. Still, being the lead means that I do a lot of design with the rest of the team, and it has really reformed my understanding of the people and the types of people who work in this industry.

I am a designer. Through to the core I put things together or take them apart constantly. It shapes my worldview and my understanding of life. But when something is so core to your system, it's often hard to realize that the same way of looking at the world does not, necessarily, go double for the people around you. This is one of the most important things I've come to understand in my position as lead designer, NOT EVERYONE IS A DESIGNER.

I keep thinking, "Oh, we need some animations. I bet the animators would love to concept some cool flips and attacks." But they don't. They're still creative -I have no doubt about this- but they don't want to design things. They're Builders. Their creativity comes in execution, not conception.

And the whole industry is filled with people who's great creativity is somewhere other than design. I know this as a general point of knowledge, but It's so far from my conscious thought that I tend to forget. In my mind it makes sense that an animator would design animations because I assume that everyone uses thought processes similar to my own. I assume everyone is a designer in addition to whatever it is they do. And I need to stop that.

Today, my co-designer and I were talking about the world map and we were trying to fill a design hole involving backtracking through the map without backtracking through the story. I kept trying to prompt him for an idea as I didn't want to trample on his map design, but after a few minutes he just flat out said, "I need an executive decision." He isn't a high concept designer. He's a builder with design sensibilities. He doesn't want a big blank slate, he want's someone to draw the outline so he understands what he should build. And that's more than ok, that's great. We couldn't survive without him. But it means I need to be more conscious of when I'm heaping blue sky design onto people who are, for lack of a better word, agoraphobic.

So I'm going to do just that.

Modular Design

I've been putting together a level using Bethesda's Fallout 4 Creation Kit. It's my first time using the Kit and my first time using modular pieces to make something, needless to say, it's been a learning experience.

Modular stuff is great in it's own right, I feel like to could pump out level at an incredible speed this way. That being said, I've run into a few problems typical of modular kits. While I won't list the others here, I've just discovered that somewhere in the level, a piece got tilted about 0.9 degrees. Every piece placed afterwards followed the trend because when you're snapping things together, you really only care if they are snapping together. Now that I'm doing some more precise work, I'm trying to duct tape a solution that doesn't leave holes or cause noticeable Z fighting.

The lesson here. Check the transform details every once in awhile. Probably every time you save.

BP Homework 2

So the homework had some ups and down. I managed to put together a pretty night scene, but a some of the terrain ended up rough, and it took a lot longer than expected. This was my first real foray into making rocks from smaller rocks. Honestly, that was a lot of work, or time at least. The finesse that goes into making them smooth and realistic looking is significant. Overall, I was pleased with the blueprints I put together, and I learned a lot about getting different blueprints talking to each other, in addition to getting rock blending experience.

A glow light you can throw that illuminates dark areas. You only have one, so the BP destroys your old light if you throw it again.

Allows Mushrooms to be picked up.

Spawns a bounce mushroom if the hit surface is "mushroomable."

All of the Player Blueprints for throwing things, making the HUD, and others.

Color Picker

I know I'm a few posts behind, but I'm up to my arms in work, you'll see it soon.
I just wanted to pop in to say that Photoshop can color pick from anything, including an open UE4 project. Fantastic. Very useful when your sky sphere won't tell you what color it is (because it's hooked to the sun height).

Blueprint Homework 1

So, this week I'll be working on a level design homework that is all about blueprints. The requirements are simple. Make a level with 2 areas, and 5 different functions blueprinted, that's it. I've decided to make a level where the player traverses a tropical forest by collecting and deploying bouncing mushrooms.

BP 1 will be something like a grenade, except it will spawn a bouncing mushroom.
BP 2 will be that mushroom
BP 3 will allow the player to pick up these mushrooms.
BP 4 will display the number of reserve mushrooms on the UI
and BP 5 will be a light source that floats up into the air and illuminates an area after it hits the ground

The trickiest part, so far has been the grenade component for which the tutorial I followed was severely lacking. So, instead, I'm going to start from scratch and steal bits and piece from the premade FPS level that Unreal has. The gun projectiles are similar enough that if I reimagine the blueprint with my new mechanic in mind, I should be able to make something work.

Wish me luck.