Ooh! I figured out how to make my game look like crap!

Until I work on the shaders, every new thing I add will probably make my game look shittier.  But whatevs.  Over the course of the weekend, I managed to make a whole bunch of changes that manifested themselves in this amazingly beautiful train-wreck of progress:

Yes, those are untextured archers shooting spheres with trail-renderers slapped on them for good measure, untextured trees that I just said "make them green", that skybox texture with the paste on clouds, and a bunch of low-poly plants that, you can't tell from here, I actually made out of origami, photographed, and slapped onto a model.  They will be so super cool.  You know, when they stop being shitty.

See?  You can see the potential here, right?  I swear this will look way better when it has a quality looking texture on it and not GREEN.  UNITY DEFAULT SHADERS MAKE ME GREEN NOW.

And this is the untextured-but-otherwise-finished animated book.  Depending on how much processing power it takes to make this sucker go, I might want to use this for pretty much all of the menus ever.  And maybe just make some interactive books on the iPad for mad cash (zero cash).

STOP... ... ... Pause Menu Time!

I started labeling my images with the date, and then if I had more than one from one day sticking the time on there.  This makes things mildly depressing.

I made this mockup at 9:45.

Aaaaaand this one that's actually in the game says 11:15.

But hey, I've got a PAUSE MENU that WORKS.

Saturdays are pretty much the best.

I got a bunch of real life stuff done today, and still had plenty of time for game work. I don't, however, have time to demonstrate it in an exciting way. But my bears now move and attack properly, they look like bears, and they drop coins in the correct locations, and knights cost money to summon. That's the basic functions of the battle system mostly done. Now I all I need is a GUI, a story mode, a kingdom editor, a system for procedurally generating content, and like a bazillion more models and units!

Also sounds. Lots of sounds.

I don't know about U, but I have got some stuff done.

Some UI that is.  I started it.

Right now, all it does is display how many coins you have collected from bears, but I'm working on a mockup for the general UI design for the battle screen.

Cropping is for losers.

I also did a lot of behind-the-scenes fixing.  I spent a lot of time bashing my head against Unity's physics engine.  It's kind of hard to be like "No, I don't want any of these features, I just want these guys to move left and right and do shit when you click on them or if they smash into eachother.  I don't care about realistic physics in any way shape or form."  Also coroutines were sent by the devil to torment me.

Dear whoever wrote the Unity documentation,
The following is really difficult to understand:


using UnityEngine;
using System.Collections;
public class example : MonoBehaviour {
 IEnumerator Do() {
 print("Do now");
 yield return new WaitForSeconds(2);
 print("Do 2 seconds later");
 }


 IEnumerator Example() {
 yield return StartCoroutine("Do");
 print("Also after 2 seconds");
 print("This is after the Do coroutine has finished execution"); } }

The following is not:
using UnityEngine;
using System.Collections;


public class SelfDestroyingObject : MonoBehaviour{


void Start(){
 Debug.Log ("Object Created");
 transform.position = new Vector3 (0,0,0);
 StartCoroutine(WaitThenDestroySelf());
}


 IEnumerator WaitThenDestroySelf(){
   yield return new WaitForSeconds(2);
   Debug.Log ("Object Destroyed");
   Destroy (gameObject); 
 }


If you run this code, it will Debug the phrase "Object Created", move the object to (0,0,0), wait 2 seconds, Debug the phrase "Object Destroyed", then destroy itself!




Oh hey! Look! I just wrote up a freaking example that in some basic way describes a thing that a game object might do, then afterwards I SAID WHAT THE CODE DID. WOW THAT WAS REALLY HARD. WAY HARDER THAN WALKING MY BRAIN THROUGH SEVERAL LINES OF METHODS NAMED "Do Stuff".

Sorry... I get mad when techy people make simple things totally indecipherable.

Very important update.

You know, I think I'm just going to leave this here, and instead of explaining what I've been up to for the past few days, just let you wonder what on earth it is trying to indicate about my progress on this game.

Things move!

I am so excited that things move that I am posting a video of moving things.



It definitely has its problems.  I need to implement a cursor object, rather than putting OnMouseOver code on all the squares, and I need to pretty much implement everything as a finite state machine, rather than plopping everything in the update function, but I just want to get things moving and doing things!  And they move and do things!

IT'S ALIIIIIVVEEE!!!!

Well, not really, but the pieces move!

Yesterday I spent a ton of time scripting a bear that walks to the right and attacks and dies, and a knight that walks to the left and attacks and dies, and then I realized how stupid that was and that it's actually possible to make something inherit from a monobehaviour and still function as a monobehaviour.  So I refactored my code so that "MovableUnit" is a class, and Bear and Knight both inherit from it.  Now it works exactly as it did yesterday except it's organized better.  Yeah, welcome to the glamorous world of indie game development.  Today my Bear cubes look exactly the same, but they're WAY BETTER.  Trust me.  And this means that adding a lumberjack cube that chops down trees, and adding functionality to the bear so that he sleeps until someone tries to chop down a nearby tree etc. etc. will all be SUPER EASY.

No pictures.  Just imagine the old one but with a teal cube and a white cube next to eachother, occasionally Debug.Logging "Knight Attacks Bear!" or "Bear attacks Knight!" until one disappears, and the other moves off the screen and says "I WIN!"

GRASS!

One of the best things about doing an entire game by yourself is that you can switch between different tasks when one gets frustrating.  All of yesterday's behind-the-scenes work was getting grating, so I started playing around with borders.

I think I want territories next to you but that you aren't actively currently interacting with to really obviously look like what kind of area they are, but not actually render every thing that exists there.  Both for hiding the Goblins' secret battle plans from the player, and saving processing power.  So I think I'm going to have a 3-deep cutout border that pops up from the edges every time you switch from map view to kingdom view.

I know that probably means nothing to anyone but me, but trust me it will be super-adorable when the textures/meshes don't look like shit.  I extruded a zig-zaggy line and called it a grassland.

This looks like way less progress than it is!

I'm not even going to bother posting a picture, because it is exactly the same, but scroll down to that post where I was like "Oh hey, I made an ugly prototype in Unity".  But except this time, I made the ugly prototype in unity that MAKES ITSELF when you click a button, then you can click a different button to change the grid to orange.  This seems less exciting, except it means that I figured out how to affect every square on that stupid grid individually (I know they look like stripes, but they're actually a grid of very thin 1x1 cubes) through scripting.  Which means I'm only one step away from being able to say "put a bear on this square and an archer on this square" but that's actually like a thousand steps because I need to model an archer and a bear.  But I'm like one step away from "put a cube on this square and a capsule on this square" and two steps away from "and as soon as it starts, all cubes move forward and attack anything they hit, and all capsules spawn smaller capsules that travel forward quickly in a straight line until they hit the cube".  Well, you know...

I'm posting more pictures of blender progress because it is way more obvious than Unity progress.  I have a walk cycle done.  Like all other things I "finish" it is a super crappy walk cycle, but it is way more useful to have a crappy model with crappy textures and a crappy walk cycle than a really pretty eyeball.

Your Gender can be Wicker or Leather

Is my prototype character customization screen super progressive or did I just not get around to making all the necessary assets yet?

THE WORLD WILL NEVER KNOW.

I have way too much to do to ever sleep.

Well, I'm about to turn in for the night.  Progress for the day:

Some pretty sweet-looking leggings, some awful-looking metal that doesn't look at all like aluminum foil, and a tutorial changing room that lets you swap out weapons and character meshes.

Complete with man lanterns!

Good morning!

I was up until 2, then up again at 6, but I think I'm getting better at this whole UV unwrapping thing.  It didn't take me 6 hours just to unwrap the shirt, so I'll call that progress.

The hair, boots and belt are all just messing around with throwing a really basic paper texture on an object.  But I really like the shirt, where I took my time and shaded it and drew on some creases.

The belt and shoes look totally crappy, but I'm not going to rework them until later in the process.  It'll do for now.  Refining is for when you have a product to refine.

I have a prototype in unity.  Looks so good right?  I'm also going through the BurgZerg Hack and Slash tutorials to go through that process of making and refining a game (plus I'm totally cobbling parts of this in shamelessly.) and that one has floating man-lanterns because I was too lazy to hunt through the internet to find a free lamp mesh to steal to make timed lighting.

And I made a skybox that looks like paper.  I need to smooth out the edges, but hey, that's my rule.  Get everything working before you start refining.