Skip to main content

Idle WitchCraft Sprint 6

Farmer Sprite

The next character joining our roster of hand-drawn sprites is the Farmer!



You may notice that this sprite is only a 32 by 32 resolution headshot of the character, rather than the full-body treatment that the Knight got. This is because we as a team have decided to pivot from doing 128 by 128 full body character art to smaller scale headshots that I can complete much faster. I would love to do full body artwork for all of the characters, but sadly the time we have left to finish this project wont allow for it.


Pivoting to headshots is overall easier, but it also presents its own unique challenges. Before, I was able to convey a character’s personality and profession through a depiction of their entire body, but now I have a much more limited space to try and depict as much as I can about a character. This is proving to be a challenge as I work on the Scholar and Maiden sprites currently, but for the farmer I actually didn’t have too difficult of a time.



After reviewing some reference images, I settled on a few details to start out with when drawing the farmer: A straw hat and a piece of wheat sticking out of their mouth. These features do an excellent job of utilizing the limited space available to me because they’re very exclusively associated with the concept of a farmer.



As I continued with the lineart, I did something that I usually don’t like to, which is introduce a third color into the palette. I think it was justified though, as distinguishing the wrinkles from the other facial features like the eyes and mouth really assists the readability of the sprite, since those elements are so close together. I also tried to recreate that frayed-edge look of many straw hats.



Finally, during the coloring and shading process, I added a little pink ribbon around the Farmer’s hat, just because it felt like something she would have! I feel that this character really came to life as I drew her, which really sped up the whole process. I experimented with adding some more texture onto the hat using a second off-white shade, but I wasn’t very happy with those results, so I opted to just leave it as a solid color. I feel that the silhouette of the hat alone is enough to sell the idea of the straw hat.

Scenario Customer Sprites

Now that I had my fancy Knight sprite all done, it was time to put him in the game! 



Getting him to be the right size on the phone screen took some playing around, but I eventually got him taking up as much space as he could without cutting anything off horizontally. It works at different resolutions too!


This implementation was mostly done so that the artwork would be in the playtest. Now that we’ve pivoted to smaller character portraits, I’ll have to go back and revisit this next sprint. Although it shouldn’t be terribly hard.


Comments

Popular posts from this blog

CAGD 373 Blog Post 4

This sprint I was assigned a modular set to create the basic interior rooms out of, with three different textures for the walls. (a Square Brick Texture, a Cement Texture, and a Metal Wall Texture) The actual modeling itself was as basic as it gets, I just made a few different shapes and sizes of wall along with a doorframe, with a couple floors and ceilings to complete the set. The interesting stuff this week was the textures, all of which I made in designer! The brick texture was probably the most complicated, and the one I’m most proud of. Starting with a brick generator, I used some gaussian spots to add some variance to the shape of bricks (using the spots to “cut out” chunks of the perfectly square bricks) and that worked pretty well! After that, I used a grainy looking noise map to fill in the black part of this mask to add in the noisy texture of mortar between bricks Next, to add some color variation to the bricks, I used a flood fill node, which was able to identify all the...

Video Game Production Sprint 1

  After a long time spent away from Unreal Engine, I’m getting my hands dirty once again as a programmer for the Kill Everything in Sight team! KEIS is an endless action FPS roguelite where you play as a killer robot tasked with exterminating the remains of the human race. Despite your incredible movement and combat abilities, you are severely limited by a timer ticking down during the entirety of your run. Killing enemies will add precious grains of sand to your cruel hourglass, so the player must focus on speed just as much as precision! I was brought on the team as a programmer, and I started off very nervous since it's been a while since I last programmed in Unreal. On top of that, my first task was to create the foundation of our enemy AI, probably the most critical gameplay element after the player and level design, and I haven’t touched AI in Unreal outside the absolute basics! However, I was determined to make my team proud and confident in my ability to learn quickly...

Idle WitchCraft Sprint 4

  This sprint, I started by implementing alternate success conditions for certain scenarios. This means that for some scenarios, there will be multiple different stat checks that can lead to different outcomes, and potentially different scenarios down the line. Two different outcomes of the scholar’s exam scenario. One for high intelligence, and one for high charm! This was an interesting programming challenge, as I had to figure out how to associate these alternate conditions with the data table that is currently holding all the scenario information. The interesting thing about these alternative outcomes is that they function as almost half a scenario. They have no intro dialogue, but they do have a unique stat check, outcome dialogue, and list of scenarios to unlock on success. Because of this, I decided that I would copy the current scenario into a new struct. That way, I could “swap out” certain pieces of data at runtime without having to fill my data table with duplicate inf...