Kynseed News

Welcome to Issue #53 of The PixelCount Post, a periodically released update from Kynseed's team. In today's issue: Charlie looks for bad apples, Neal dives into details, Tice goes off on a mission, and Matt humble brags about puns.
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ









Welcome to another issue of The PixelCount Post! As it happens, we just released a dev announcement mere hours ago for our optimisation update. So we'll be keeping today's issue short and sweet, like a small puppy. Preferably a pug.

This was our first optimisation update and it's really helped clean some things up on the back end of the game. You'd be surprised how much spring cleaning is needed when working on the same engine since the prototype. This proved to be a very useful update for us, so we're glad that we've made time to sprinkle a few into our roadmap. Next stop on our development journey will be a features focused update with an emphasis on running your own Goods Store, managing hired staff, and accruing shop reputation.

We'll be jumping on that first thing Monday, after we tie up any loose ends and bug reports for the current update. If you come across any bugs yourself, feel free to give us a shout or write us at [email protected]. Thanks folks, we'll see you again next week!









This past week has been document catchup and trying to finally get a good pass of the "Items Master" list finished. I was working 'til 1am on it the other night, then realised I didn't like it so started the "Recipes and Traits" doc again and made a lot more order out of it. I'm much happier with it now.

I was also testing the build a bit and just playing around. The seasonal items caught me out and I forgot that some ingredients go missing in certain seasons so I was complaining to Neal about the lack of apples in Spring. It turned out we ended up enabling apples in Spring anyway, so players have fast travel options still.

We also received some more excellent art from our artists: new UI, environment stuff from Matt Weekes (excellent as always), and monsters from Gary. I just saw a composition of all the latest monsters, and we really do have a fantastic line up. Colourful, detailed, and dripping with character. In the case of the big ones, their teeth dripping with your character most likely!

Next week I am back on the new Loverwood region and then I'll make inroads into Mellowfields, our third haven! Let's just say, I'm continuing a theme from a level I made for Fable Legends...





This last week I've been getting back some of my focus. It's a difficulty on a long project to maintain a consistent pattern of work and intensity. Oftentimes it comes with deadlines and this week was another update deadline. I feel like it's more than that though, where I've been trying to think about the work in a different way. Such as being more disciplined about working on detail instead of holding things off for some unknown future point.

It sounds simple and sensible when put like that, but I have found it easy to stray from and so it does feel like a big backlog exists to work on which I'm never sure when I'll get to. The details can be a problem as well when they mean too much time is spent on something that turns out wasn't necessary, but I think generally those things have tended to be rarer on this project at least.

Anyway, to get away from more general ramblings about process: I've been working on keybindings, skills in-game, and some editor screens. The keybindings took a good two days but am quite pleased with the general results. It was a nice standalone feature to get into the zone for with lots of details which seemed to keep popping up as I looked through the code. Skills in-game I had some trepidation about doing, but I think it's starting to turn out nicely in presentation.

One area I have held off for later is standardising the UI presentation more so that it's easy to reuse visual/audio flair without having to code it each time, but that did seem like a step too far in the circumstances so will have to wait 'til the next optimisation update. The editor screens are to help assist level design and placement of items/fish/growables, which have started to reach a quantity of data that would benefit from improving and, again, to avoid relying on code so much.

The rest of this week will be fixing any bugs with the new update along with more editor screen work and setting up more events in Festfield. Then it'll be on to the next major update with the Goods Store and business ownership. I'm looking forward to introducing more of the gameplay loop and getting stuck in their details!





I have to write this a bit sooner than usual because I'm about to go away on a mission to play percussion at a festival abroad. On the one hand it cuts into what I'm currently doing, and on the other it's a breath of fresh air. Literally, as it'll be out in the open air.

On the game front, the themes for all the shop purchases are done for Candlewych and Poppyhill. At the time of writing this the current update is pretty close to done, and after it releases it all starts again with the update after that. There's shop tunes still needed for the next town beyond Poppyhill, which will keep me busy for a bit.

All in all, we're going through the items on our roadmap pretty quickly. It's great to see things getting crossed off the list as 'done' over time. There's also only 2 weeks left before my trip to LA begins and, believe me, I'm counting the days!





Welp, that's our first optimisation update done then! It was the first update of this kind that we've tackled, so part of the challenge was determining exactly how flexible we wanted the update's focus to be. For the first week or so of the update we started off very flexible. The idea was that we'd give ourselves an opportunity to do some freeform collaboration on things that we've been needing/wanting to do but never found time for in other updates.

Though after a while, we found ourselves preferring a bit less freeform and a bit more balance - a sort of 'structured' flexibility. We've had a long time to work together as a team and learn what keeps us motivated and efficient. We like to stay pretty agile and reactive, but we also like to have a generally structured plan at the same time. A sort of underlying compass to follow behind everything we do.

That balance ended up being the special ingredient for making these optimisation updates pack the most punch. Plus, now that we've found that balance, we'll be able to hit the ground running even harder for when the next optimisation update rolls around. Though personally, I'm looking forward to getting back to focusing on features and content. I'm sure it goes without saying that back end optimisation is one of the least sexy parts of game development, despite being critically important.

For our next stop on our roadmap we'll be adding in Goods Store ownership, deeper staff management, and shop reputation. We're calling the update "A Song of Price and Hire", and I'm far more proud of that title than I should be.

ᅠ


Hello there Seedlings! We've just wrapped up our recent optimisation update and have dispatched it straight your way, primed and ready for downloading. These optimisation updates are focused more on behind the scenes background work for the engine so, unlike our prior updates, this one won't contain quite as many visual changes on the surface.

That said, we still snuck in a few surface additions here and there, including a new farm mailbox as well as some initial keyboard mapping options. As such, we've come to refer to this as the "Keyboard Cartography" update. Apparently our lack of shame with bad puns knows no bounds.







One of the more noticeable additions for this update is a quaint little mailbox that we've added to the farm. Over time this mailbox will likely intertwine with gameplay, but for now we're just using it as a quick and easy way to give you brief summaries of any recently released updates. This way players won't have to wade through these lengthier announcements if they don't want to and can instead get highlights of new content right in-game. So anytime you see a red ribbon on the mailbox, that means you'll have a new letter straight from us. (Each one is handwritten, so long as you count keyboards.)

This update has a few other bits and bobs as well (like keyboard remapping!), but the primary focus for our optimisation updates is making sure our engine stays nice and well oiled. Primarily this included work on a few of our developer tools to make them more efficient and streamlined. Tools like a new Skill Tree Editor as well as existing tools like our Cutscene Editor, the latter of which we'll use to add events and story moments into future updates.

For a more in-depth look at things like the Cutscene Editor you can check out Issue #51 of The PixelCount Post, which is our series of weekly dev updates written by the team. Though for a more cursory look at today's update, read on below!

• You'll receive a letter from us for each major update
  
• Look for the red ribbon to see when a letter has arrived
  
• (May break fourth wall)

• Set new keyboard bindings for both Primary and Secondary controls
  
• Also set shortcuts for hotbar items

• Initial 3 items on new cooking skill tree (first pass)
  
• Improvements to some internal dev tools (Cutscene Editor, items, & navigation)
  
• New internal dev tool: Skill Tree Editor
  
• Spring cleaning of unused textures & assets
  
• For a complete look at all changes, check out the full changelog

Next week, we'll be turning our attention back to working on some meatier content updates, starting with an update we've cheekily named "A Song of Price and Hire". That update will feature things like owning the Goods Store, managing hired staff, and a shop reputation system. We'll be pushing this update out the week after E3, so as to avoid releasing it during all that E3 hustle and bustle. As always, don't hesitate to check out our roadmap for a full rundown of what's to come.

Thanks to everyone who's been playing and providing feedback along the way, even for these less flashy optimisation updates. Speak again soon!

Love,
PixelCount

• Discord
• Official Forums
• Twitter - Kynseed
• Twitter - PixelCount
• Facebook
• YouTube
• Twitch
• Official Website
• Kynseed Media Kit

Welcome to Issue #52 of The PixelCount Post, a periodically released update from Kynseed's team. In today's issue: Neal dives into details, Matt interfaces with interfaces, Tice mellows out in a field, and Charlie speaks of an ill Quill wind.
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ









Another week rolls by and we're one step closer to finishing up our current optimisation update. Which as we've said before, isn't so much about 'optimisation' per se, but rather it's a flexible update to give us time to tend to longterm engine work - such as perfecting our developer tools like the Cutscene Editor discussed last week.

On that front, Neal has continued work on polishing up more Cutscene Editor bits in addition to doing some work on our UI Editor, which also received attention this week. Art has been pushing through some amazing things as well: Weekes has been preparing beautiful field tilesets for an upcoming region and Gary has been making adult sprites as well as a few horrifying monsters. All to come in future content and feature updates of course, which you can read about on our roadmap.

Though currently, we'll need to start winding down work on this update so that we can get it ready for release. Although there won't be as many flashy obvious changes on the surface, there's still a good deal of work that's gone on behind the scenes, so we'll be sure to share a full changelog when the update gets pushed out to everyone. For those of you anxious to check it out, you can expect the update to go live middle of this upcoming week!





This week I've improved some more on the Cutscene Editor, which turned out a little tricky. I've been trying to convert the Fairweather appearance sequence to use the Cutscene Editor because it was done via code originally (quite last minute to a deadline!) and so has always been a little painful to work with.

To do so required some new abilities for the Cutscene Editor (scaling objects and animating non-character sprites) and these turned out quite intricate to set up. I've also been working through Matt's feedback on the system which has been helpful in guiding the work. Otherwise I've been working on the setup for acquiring skills ingame with cooking (recipes) being the next one to get in. This went reasonably smooth, but does need clarity in its presentation.

The next step I'm taking a look into is keyboard mappings as an often asked for feature. It does feel a little like I'm getting buried in the details lately, but they do need filling in, so slowly the big picture will emerge...





Over here at Chateau Matt, my humble home across the pond from Castle PixelCount, I've been keeping busy with various odds and ends in support of the current optimisation update. Last week I focused on our Cutscene Editor tool, so for this week I switched over to focusing on our UI Editor tool.

The UI (User Interface) Editor is, as you imagined, an editor for UI. Shocking. However, there's a surprising amount of depth to the tool, if only because a game like Kynseed has literal thousands of individual UI elements across the entire game - with more to come even! There's the game's menus, item inventory, player toolbars, combat elements, dialogue interfaces, all the jobs, all the job ledgers, and so on.

Having a quick and efficient way for the team to make changes to these element's appearance and positioning is crucial for keeping the team's efficiency well lubricated. (Everybody likes a well lubricated dev team.) This is where the UI Editor comes in. Much like the Cutscene Editor, using a tool opens up the creative process to the entire team rather than having it all remain housed deep in the code where only Neal can find.

For now, the biggest difficulty with the UI Editor is that not all UI elements are linked to it. A number of elements were added before we had the UI Editor in place, so many are still hard coded in. This means we've got to go through and identify which elements aren't linked to the UI Editor and make note of them. From there, Neal will track them down and get to work on linking them up.

It's a fairly tedious task at the moment, but once done it'll make for modifying UI as we go much much easier. Kynseed is a game with lots of moving parts and new parts are getting added constantly, so the gobs of UI we have tend to be in a very constant state of flux during development. That'll continue to be the case for some time, but with the UI Editor we'll soon be able to polish it up as we go with far more efficiency.

Though for now, it's back to the grindstone. Literally. I'm working on the blacksmith UI.





Another week flies by. Does anyone else feel time is speeding up?

As I had hoped, I was able to hand in a couple of iterations of the leitmotiv I talked about last week. It won't be until the corresponding scenes can be made in the new Cutscene Editor that we can really test out these themes within the game itself, but even outside of the game you should be able to get a feel for what they're trying to communicate.

Meanwhile, I'm trying to get the most out of my MasterClass pass before it runs out. I'm learning a lot of technical things that should be transferable to many a situation. I'm also eager to get to work on additional cutscenes that can now be made with the new editor. I've also made a list of little adjustments I want to make to some tracks in the Mellowfields region.

The more I listen to previously made tracks, the more little things I notice. It never stops, and I don't think it ever will. But I take it as a sign that my ears are getting better at picking up tiny details.

Next weekend I'll be off to a medieval festival to do percussion. It'll be a nice change of pace and hopefully some fresh musical influences. Not too long after that it'll be time to get on a plane to LA! I'm SO excited about E3 this year!





This week I was on a bit of a dietary change to try and get myself back on order and it had the effect of giving me more energy. I waded into design docs, doing new ones and tweaking old ones.

One of the designs still not there was for the ailments the people of Quill can get. When you own the apothecary, you will get customers coming in and you can sell them 'off the shelf' items or go craft them there and then. However, the system was a bit of a mess and the shop side was lacking. So now, NPC's will come in and you ask what the problem is.

They'll give you between 1 and 3 symptoms. If just one, we call it a 'PickMeUp'. And if 2 or 3, it's a 'Malady'. Maladies have a visual effect to help identify them and add some amusement, and more info on them can be found in Medical Tomes and Proverbs. Each symptom has a cure and the player can select these in a notebook and create a prescription. This acts like an order book and can be passed to a staff member to mix or make yourself.

NPC's may also just want to buy a dye or perfume, and you can craft anything you want and the Traits will take care of it. Want the perfume to make them fart? Mix in ingredients with Flatulence Trait to one with Scent. You can make powders, creams, and potions, then store them in the shop cabinet or even take them with you.

We're hoping the player will get a lot of fun from the system and get a nice feeling from crushing, grinding, distilling, and mixing. "Oh hello sir, seems like you have a touch of Flamefart. I have just the thing..."

Welcome to Issue #51 of The PixelCount Post, a periodically released update from Kynseed's team. In today's issue: Neal notices nagging notes, Charlie gets ideas, Tice uses flashy vocabulary, and Matt has a keen scene machine.
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ









Issue #50 is still lukewarm off the presses, but we're back to our usual pace of things this week with another issue on your virtual doorsteps. As planned, work is happily continuing along on the optimisation update. The team's been keeping most busy with preparing new art assets and UI improvements. Meanwhile, Neal has moved on from working on bits of Prologue polish and is now sorting through team feedback on our developer tools, such as the Cutscene Editor and UI Editor.

Polishing and enhancing those tools will make a world of difference for speeding up development across the entire team. The more the whole team can use and access such tools, the less burden it will be on Neal having to do everything code side, thus freeing him up to work on higher priority systems and features. As a result, new cutscenes and UI tweaks are being worked on as we speak, though it might be an update or two before these actually show up in-game.

Lastly, for anyone who may've missed it, you should check out the recently released Special 50th Edition of The Post. It features a few extra appearances (like our character artist/animator and our icon artist) as well as a neat look at old Kynseed prototype screenshots. Though best we get back to work for now, as there's new sprites to make and new cutscenes to edit. So we'll see you all again in another issue soon!





For Week 2 of the optimisation update, I managed to get further into the little bits and pieces of nagging issues that affect the making of the game along with working on a skill tree editor and trying out the adult anims which are starting to come together. In our situation where the engine is custom, the editor is also custom. So it's effectively two engineering projects for the price of one! As the project has gone along I've been slowly iterating on the functionality for the editor to fill in shortcomings and improve the process of making the game, but there's always more to be done.

Often this leads to me making a mental or physical note and then trying to ignore it - which works to an extent. But it always leaves that question of how much time might be saved by improving the editor, both for iteration speed and for the removal of such thoughts needing to pop up and be ignored! That question can hopefully be answered a little after this update is complete, but it certainly feels satisfying to knock down some of those issues.

One aspect of it that is a bit of a crossover for editor and game is that I worked on improving text input. I've done some work to make the cursor movable to edit the text at any point, which turned out a little less straightforward when having to factor in how the DEL key works and using the CTRL key to jump between words. I've also been looking into fixing leftover placeholder images from changes in tiles over the last 2 years. That has proved a time consuming process but is coming to an end (down from 1,000 tiles to 100 or so left now).

It's tricky making changes like this because of having a live data set to work with. One which encompasses some 20 odd levels, meaning mistakes are quite costly to track down. If I was going it again I'd definitely look to plan for these kinds of situations more.

All in all, a better week than the last one though with more variety of work and the feeling of tidying up loose ends - all of which will prove handy in the coming months. For now I better get back to work on some bugs, along with the Cutscene Editor and a dozen other useful bits!





Games. We all love 'em (or we wouldn't be here). So many to choose from over a wealth of platforms. So many stores touting their wares and throwing super cheap or free games at you. Humble Store, Game Pass, Games with Gold, Epic Store, Steam, GoG, PlayStation Plus, itch.io, GameJolt, Uplay, Origin, and so on. My backlog grows and my desktop grows ever more full of icons. (Matt has a meltdown over my chaos.)

It really is a flooded market out there. There is good use to be found though, amongst this sea of games, for a developer. You can find inspiration even in titles that disappoint. Example: I have been playing Forager this week. It is quite moreish to start with, then unravels itself to be a glorified clicker game with no real point to it. However, the game gave me two huge jolts of inspiration.

The game is made with such love and the developer has his own story as a cartoon for you to read. There are also warm messages and a constant sense of it being a passion project. Secondly, it has lovely popping menus that feel lively, look colorful and clear, and even function well. We can learn from these things and one of our eventual aims is the UI to look, feel, and sound nice.

So many games, yet we can take something small from each one, even if it is not how we do things. Now excuse me, I just noticed a few more free games on Game Pass...





With the current optimisation not requiring new assets from me (so far), I've been able to focus on some prep work for E3 next month. Quite a bit of work goes into traveling to the states and making yourself ready to meet the developers of the world. There's also some music related to the shops that I hope to get done before I go state side.

There are two important themes in the game's soundtrack that I want to put in numerous places around the game. The thing about themes, or rather 'leitmotivs' as they're called, is that you need to repeat them quite a bit before the brain makes the right connection between the theme and the thing the theme represents. It then subjects it to memory. So I'm looking for all the places in the game where these themes can be repeated and associated.

The acquisition of shops is one such place. The theme I want to put there represents personal growth and development. I want the acquisition of each shop to have its own iteration of that theme, using the instruments that I also use in that shop's music. In turn, each shop is influenced by the instruments used in the region's music they're based on. So just from the music alone, you'll be able to hear what shop you're acquiring and where the shop is located. Plus they need to give you a feeling of personal accomplishment. I hope it works in practice as well as it does in my mind!





Dang, just thought of a better name for 'The Short Report'. I could've instead called it 'In a Nutshell'. Ah well.

Aside from lamenting missed naming opportunities, I've been busy spending time in the game's Cutscene Editor. This tool was initially put into the engine earlier this year, but there's been so many spinning plates for me to tend to in recent months that this is the first chance I've had to really sit down and sink some time into it.

Though for now, the goal isn't to create the cutscenes themselves. Not yet, at least. Right now the goal is to note down any problems, bugs, or quality of life improvements that the Cutscene Editor needs. I've already compiled a first pass list of feedback notes and have sent them on to Neal, who'll be sorting through them over the next day or so.


Here's how the Cutscene Editor currently looks. There's still work to be done on it, but soon I'll be able to use it to create scenes and story moments in the game. (Click here to enlarge.)


Something that I'm particularly fond of with the Cutscene Editor is that Neal and I worked together to make it behave and feel like a video editor. Specifically, Adobe Premiere Pro. It's the video editor I personally know best and I've been editing videos with it going back as far as when I joined the Lionhead community, if not longer. As a result, I tend to handle any and all video work needed on the team - our current trailer being one of the most recent.

So what this meant was that when Neal and I began the initial groundwork for the Cutscene Editor, I was able to give him a rudimentary design to follow which was, at its core, a very simplified version of a video editing interface. This included things like: a project timeline at the bottom, a moveable playhead marker to denote which frame the editor is on, timeline blocks/objects with expandable in and out points, a properties window on the side to alter the behaviour of timeline items, and so on. It also shares many of the same hotkeys as Premiere Pro, so I'll even be able to use all the little video editing shortcuts that have become muscle memory over the years.


Everyone does their layouts differently, but here's how my Premiere setup looks. You can see the basic similarities when compared to the Cutscene Editor above. (Click here to enlarge.)


There's still work to be done polishing up the Cutscene Editor for regular development use, but the recent round of feedback notes compiled this week will likely take care of the brunt of it. Once that happens, I'll get to start making some new cutscenes to be included in future updates!

Welcome to Issue #50 of The PixelCount Post, a periodically released update from Kynseed's team. In today's special issue: Gary talks character art, Caz chats icons, Charlie discusses issues, Neal notices boards, Tice gets effective, and Matt makes a scene.
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ
ᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠᅠ





Goodness, it seems our humble PixelCount Post has reached issue #50! We've been writing these so routinely that it very nearly snuck up on us. To help celebrate, we've included a few extra things for this week's issue. In addition to the usual crew that writes for The Post, we also brought along a couple of our other teammates to pop in and say hello. This includes Gary, character artist extraordinaire, as well as Caz, creator of lovely icons.

Another fun extra for this week's issue is that we thought it'd be fun to include some images from the earliest of early Kynseed builds that were ever made. We're talking extremely early here - ugly placeholder art and all. We've scattered these images throughout the issue and have included a small descriptive blurb under each one.

You can check all that out further down, but as for our game progress: last week we began our initial work on getting our first optimisation update underway. As mentioned in our trusty roadmap, this update will focus on refining some background systems and paving the way for future systems to come. For our first week of that update, we've taken some time for a bit of polish and clean-up of the game's Prologue.

Neal typically has to do the heavy lifting for these sorts of updates, but the plus side is this gives the rest of the team time to catch up on other areas of content creation in the meantime - such as making all the adult player animations. Those are especially time consuming to create, because it requires recreating every player animation over again but at a different age - and for both twins no less! So all in all, these optimisation updates are providing the team a nice change of pace while simultaneously allowing us to catch up on a fair bit of back end work.

Okay, so maybe this week's 'short report' is not so short. In fact, this entire issue is pretty hefty! Though we figure a 50th issue is reason enough to do a bit more than we usually do. Thank you to all of you who've been reading along since the very beginning as well as those of you who've just joined us. There's still a ways left to go on our journey and we're happy and grateful to have each of you with us.



This is one of the earliest screenshots of Kynseed's prototype that we were able to find. (The art is all generic placeholder, of course.) Even at this early stage we already had a few basics in, like finding dig spots, pets that follow, throwing items, and even playing catch with the pets.





When I joined the Kynseed team as character designer/animator, they already had a small demo up and running showing the first section of the game. My challenge was to take the established characters, along with concept art, and put my own twist on things.

The first thing that struck me when playing the game was how beautiful and rustic the environmental art was; lush fields, colourful flowers, tall imposing trees, and cosy cottages made up the world of Kynseed. To contrast, I wanted to make the characters a bit more iconic/cartoony and try to make them stand out on the rich detailed backgrounds.

The design process for these characters begins with a rough outline document from Charlie. We are very much on the same page when it comes to reference material and influences on our designs - in fact, our book collections and movie watching habits as kids are strangely similar.

When I was designing the monsters, I would think back to creepy sketches in old English folklore books or the Usborne Guide to the Supernatural World books from my childhood, crossed with an unhealthy dose of the Deadites from the Evil Dead movies.

A year and a half later, with around a hundred villagers, animals, monsters, Fae folk, and of course Mr Fairweather under my belt...all designed and animated. (The amount of animation frames created is scary!) I think we’ve done a pretty good job and it’s been a real pleasure working on the game.

I had an absolute blast designing the monsters of Kynseed and they are next on my animation list once I finish the grown up twin animations. I really hope you enjoy meeting/being stalked by these creatures and get a little creeped out by some of them!





Happy 50th issue, and it's such a pleasure to speak to you all! I'm Caz, and I'm a pixel artist from South Wales who's currently responsible for slowly replacing Kynseed's item icons with fancy new ones. With Fable being one of my favourite game franchises as a kid, you can imagine what an absolute honour it is to work with these guys and see all the hard work and love that gets poured into Kynseed.

Besides pixel art and games, my other biggest passion is food and baking, so naturally there's a lot of room for crossover between that and my art. Nothing makes me happier than being able to churn out all the different icons for the game, from Apple Pie to Bacon Surprise.

It's always a great joy to find creative and funny ways to express the same brand of unique humour that Kynseed possesses when it comes to drawing the icons, and I hope some of you eagle-eyed players out there will spot some of the references!

Thanks for letting me blab, and I look forward to seeing more of you enjoying the game's progress!



As prototype engine work continued, we began slowly adding our own art into the game. A few other features began to show up as well, ranging from lamp post lighting to shadows under sprites. The basic outline of the farmhouse began to also tentatively take shape.





Amazing to think that we have hit 50 editions of The Post. If we had stuck to our schedules we might have had 3,000 editions by now. Some weeks can be a challenge to think of what to write...while others just flow easily, like the results of Sipp & Winter's Go Easy Potion.

It is great to see that our readers really enjoy our periodical. We were thinking of having some more titillating content to add some sensation, but the thought of Tice wearing just a cloak as he cosplays Herbert Lemon was too ridiculous to consider. We thank everyone for sticking with us through 50 editions and look forward to creating the next 50 over the next 50 years. See you again next week, same time, same batty channel.





With the "Gnome Pun Intended" update out, I've been busy fixing bugs as they popped up. It feels like they are slowly shrinking in numbers but still lurking around just out of view. I've been trying to take it strategically in reducing them because they can be rather time consuming, as mentioned last time, when it takes a while to even get them to happen consistently enough to figure out.

Now that we're in our optimisation update we've been talking over potential candidates for work. For last week, those include some tweaks to the Prologue, introducing a few new items, setup of a noticeboard, and even a first pass of a mailbox. I can see the benefits to these but do find myself wondering if they are the best thing to be doing. My plan is to get them done quickly to move on to other items in subsequent weeks.



Eventually the engine was able to handle more layers and complexity, so we began adding in additional art like foliage and paths (and even insects, like the little bee on the far left). This still used our old player asset, although pet art did receive another update at this point. (And of course, there were a ton of new engine features not pictured in this simple screenshot.)





I can't believe we're at issue 50 already! It's been such a wild ride to get where we are today. Before writing this I decided to go back to the first issue and see where I was at back then. I remember how at the beginning I thought I was only going to be doing music, which is my 'comfort zone' as a composer. The first issue doesn't even mention sound effects, which I've had to learn to do since then.

I was very nervous about it, and felt mostly lost. Nowadays, I feel so much more confident about doing sound effects. With it I've gained new skills, new insights, and new familiarity. Lately I've been working exclusively on sound effects and ambient (environment) sounds. The fear is gone. When I'm asked to make a new one, I no longer automatically think "I don't know if I can pull this off...", and it feels very liberating to have that confidence.

That said, I'm still no SFX expert. Even in music I have a bazillion things to learn, but in sound effects I'm even further away from knowing everything. That first issue I spent talking about how I wanted the music for the game to be diverse, yet consistently 'Kynseed-ish'. So far, I'm quite happy with how much I've been able to reach that goal. Not that there's no room for improvement, but it's good to look back at goals you've set and see that you're on track to completing them.

I reckon my focus will remain on sound effects for a little while longer before work on new region music is required. It's a good learning opportunity. We're coming up against prioritization choices where we know certain adjustments are needed, but when to implement them isn't straight forward. Do we fix that ambient sound not being optimal but requires code to get the solution we want, or is that coding time better spent elsewhere right now?

So for now, I'm writing a list of changes for sound and music I'd like to see that'll require Neal to implement. Then I'll need to wait for the right time to get them implemented. 50 issues from now, I'm hoping to see a lot of "i's" dotted and "t's" crossed in the music and sound effects. It'll be interesting to find out 50 issues from now if that goal has been met!





When not waxing poetic about hitting issue #50, we've been otherwise busy with initial prep work for our optimisation update. The tricky thing with these updates is that they're a bit more free form than our usual updates, the latter of which typically have fairly clear cut goals pre-established as per our roadmap. However, for optimisation updates, we've intentionally left those blank ahead of time so that we can stay reactive and agile during development. So the very first thing we have to do for these updates is agree on some ad hoc development areas and then order them by priority.

One of the first areas of priority, which we began work on this week, was to polish up a bit of the game's Prologue experience. Though for the subsequent weeks, we'll probably switch over to improving and streamlining some of our developer tools. There's many areas of the game's development which require hands on the code - which essentially means only Neal is able to do them. However, whenever we're able to create game engine tools that the entire team can use, this democratizes the game's development in such a way that it frees Neal up to work on other areas of the code.

A good example of this is our cutscene tool. In earlier versions of our game engine, cutscenes were handled exclusively code side. So if we wanted to make even a minor change to a cutscene, such as repositioning a character, Neal would have to go in and make that change manually in the code. This proved to be extremely cumbersome, so to solve the problem Neal created a cutscene tool within the game engine that the entire team could use.

The other great thing about this method is it lets the more cinematic minded team members have hands-on access to creating and modifying cutscenes. Different areas of development require different creative instincts, so the creative strengths of one team member are often different than the creative strengths of the other. Thus, opening up access to the game's tools allows the team to accentuate its individual strengths.

This is surely one of the chief benefits of having a programmer on the team who has experience in creating tools. In fact, creating developer tools is one of the many areas that Neal worked on over the course of his 12 or so years on the Fable franchise. It's certainly coming in handy for us.

That's also why these optimisation updates will prove so important for our development. Working on back end things like our developer tools won't be immediately visible to players, but they end up significantly improving development speed and workflow long-term. In particular, I'm looking forward to putting on my director's cap in the next few weeks as I dive into our cutscene tools and start crafting a handful of cinematic moments for future game updates.

Lastly, I know we've already prattled on a fair bit about this being our 50th issue, but I do just want to take a quick minute to personally thank all of you who've been enjoying these little glimpses into our team. We've found that they're just as helpful for us as well. In some ways, it's akin to keeping a journal. Though to provide a bit of context and backstory:

Long ago, there was a chap at Bungie named Frank O'Conner who began writing weekly development updates for some little game they were working on called Halo 2. (Shout out to Mister Chief.) Up to that point in my life I'd only ever just played games once released, but this was the first time I found myself following a game's development before it was released - years before, even. O'Conner wrote those weekly updates in such a laid back accessible sort of way and he'd sometimes even include snippets written by other team members. I found the whole thing fascinating and, I suppose, it's what later inspired me to do something similar here with Kynseed. So the fact that there's so many of you regularly following and reading these is not only exciting and humbling, but it also means a lot to us. A big and hearty thanks to all of you who have enjoyed our silly rambling issue after issue. No doubt there's lots more rambling still to come.



This is a look at where the engine is currently. Player art is updated, there's now two twins to play as, all pets received a final round of new art (plus new breeds/colours), foliage was cranked to 11, there's bees and butterflies, and the father is there with his watchful eye. This little screenshot barely scratches the surface of everything that's in the game these days, but it is interesting to see how far Kynseed has come from that earliest of early prototype.