“Kill your darlings” is a bit of writing advice heard rather often in writing. In short it means to be willing to destroy elements of your have worked hard to create. To be willing to discard even your most cherished creations. This does not mean that you will get rid of those elements, but you must be willing to do so. This is because otherwise we can be blind to the problems that our “darlings” create in relation to the whole project.

So, why do I bring this up? Simple. “Kill your darlings” applies to much more than writing.

Programming Darlings

Early on in my project I created the randomized levels. With that I of course created the controls. A drop down window for difficulty and simple “New Level” button. But I also added a “Custom” difficulty that allowed the player to input their own target number. This, the “Custom” setting, was my “darling”. It has stuck around for far longer than it should have. I have for quite some time that the dropdown menu would need to be changed. But doing that would necessitate a significant rework of the “custom” setting, and so I put it off.

But eventually, I recognized that the “custom” difficulty setting had outlived its usefulness. And so, I removed it. And in doing so, removed the last thing holding me back from removing the dropdown menu and converting it into a spinner design.

In any creative endeavor, from writing to programming, to painting, and beyond, one must be willing to remove our favorite parts of a project. All in service of making a greater whole.

Changes are happening in my game. Lots of those changes are minor UI layout tweaks that are uninteresting to talk about. Bit of experimenting, little movements to make big differences, that type of things. But I have been making some more substantial changes too.

First Biggish Change

For the pre-made levels mode, there is a visual indicator of if you have previously completed a level before and if you have solved the level optimally. At first the indicator was a big “X”, but that had always been a placeholder. Next I tried a star shape to go with the twinkling star effect I put in the background, but that didn’t mesh as well as I had hopped. Then I settled on a circle that was filled with a dot when the appropriate condition was true. But recently an idea was suggested that I should have tried much sooner.

The idea was simple: Just have the word disappear and appear as needed. Having the entire word showing up and disappearing will draw the user’s eye, showing the change. I may add a few subtle effects to the appearing (very subtle animations to help draw the eye), but just goes to show that I should always strive to follow the K.I.S.S. principle. Keep It Simple Stupid.

Upcoming Change

The next change will take a bit more untangling and reworking than the last one. I am reworking the difficulty select for the randomized puzzles. Currently it is a drop down with the options of: easy, medium, hard, or custom. The rework is three fold.

First and foremost I am changing the dropdown to a spinner design. Originally I didn’t know what platform I would be releasing on, but now I have narrowed down to a mobile release. I light of that, I am trying to eliminate dropdown boxes wherever feasible, to avoid people fat fingering the wrong option.

Next is to remove the “custom” difficulty option. I liked the option at the start, but in light of various design decisions I have made, I have decided to scrap it. Which leads to the third change.

Up to this point when you selected a easy, medium, or hard difficulty puzzle it would give you a puzzle with a preset number of moves needed to complete it. This change is to add a small randomized element. So instead of always giving a puzzle that needed 4 moves to complete an easy puzzle will need between 3-5 moves to complete. This will be reflected in the Target # the player can see, so they know how many moves they are expected to make.

Beyond All That

Those are the immediate changes I am making to my game. But some other things are in the pipeline that I have planned. But I can’t talk about everything all at once. Besides, if this project has taught me 1 thing it is this: Plans need to be fluid and you can’t stubbornly hold onto one idea.

After another review of my game (and more importantly its UI layout) a few things were found to change. Some of these are a result of recent changes, some were ideas I had before but either never implemented or changed to something else.

First Change

The first change I made which led to some of the other changes was actually a programming change. In the play scene for pre-made levels there is a level select element. The up and down options could be held down to cycle through the levels without constantly clicking/tapping. But it only went at one speed. I changed that so that it sped up as time progressed. Took a bit of coding to get all the proper flags in place, but now you can get much farther much faster than the old version, without sacrificing accuracy for short jumps.

Knock on Changes

The first big change that the improved level select caused was to the “Next Level” and “Previous Level” buttons. Previously I had those two buttons in the lower corners of the screen so you could jump to new levels freely. But back then the level select was… clunky. Now that level select is more smooth those buttons don’t need to be available all the time. But I did still have a use for a “Next Level” button. It now shows up during the “Level Complete” state of the game, around the center of the screen. This is to give the player a direction to go after they complete a level.

Planned Changes

A few other minor changes have also been made, but two major changes/reversions are also being considered. First is one likely to happen and stick around: auto level changes from the level select. Right now, after navigating to the desired level number the player must press another button to actually go to that level. The proposed change will cause the level change to occur as soon as the level up/down button is not being pressed. The second change is a bit less likely, removing the Main Menu level select.

Right now I have a level select screen in the main menu before starting pre-made levels proper. But that screen also has some useful info about uncompleted levels that can guide the player on what level they want to do. So I am very reluctant to remove it. More likely is that I will change the select method to match the one in the play area scene.

Sometimes in design you can’t just jump in and see what works. And for me, that is a bit hard. When people are standing around deciding the “best” way to do something, arguing the merits without seeing the result, I will often just go and do the thing. That way we have something tangible to compare, change, and discuss rather than abstracts. So finding something where that approach is… counterproductive, is a bit like hitting my head on a low beam: startling, annoying, and gets my attention.

So if I can’t just jump in and mess with things, what do I need to do instead? Simply put: I need to make a “prototype”. By which I mean, I need to make a rough draft of what I want the final product to look like. And that leads to three possible ways of doing it.

First is the option I use most often, make a mock up in program. For my game projects that would mean either making a new scene or rearranging an existing scene in Unity. The big advantage is that this is like putting paint on canvas, if it works no further work is needed. The two big downsides are that it can take a lot of time and suffers a lot from “good enough” syndrome, where you have it in place so it is “good enough”.

Next up is to make a mock up outside of the development software. My first instinct would be to make a Power Point “presentation”. This would mostly be an artistic representation of the final product, sometimes with screenshots of the game itself. Upsides are that it is fairly easy to edit a “completed” idea and doing repetitive images is as simple as copy/paste. Downsides are that, again, it can take a while to get things in the positions you want them. And once you have invested that much effort you might say “good enough”.

Finally is the solution I was resistant to trying, but now embrace: paper prototyping. Simply put it is drawing out the ideas on paper. Even if it is just prototyping a part of the UI design, it is so much faster and cheaper to test things in paper. That is the primary advantage of paper prototyping: the speed of being able to try things. So long as you can put aside the idea of needing the prototype to “look good” and simply accept it as “functional” it works wonders. But on the downside, if you need to wow someone with the looks… this isn’t going to do it. But that isn’t the point anyway. The point of paper prototyping is to get lots of ideas out rapidly. Then you can see what works and what doesn’t.

To loop everything back to the start, and my method of “just try it and see if it works”. I think I have come around on the idea of paper prototyping actually fitting that idea. It isn’t just debating ideas, but seeing how they could work. And doing it much faster than most other methods.

So I got some feedback from my playtest build. Several bits of feedback where simple bug fixes or graphical mistakes that were easily fixed. But there was one big bit of feedback I didn’t expect: people didn’t know what to do with the game.

Now I had kind of seen this coming. Several times I started making a tutorial level, only to abandon it as the design left the tutorial behind. I figured if I needed it I would get back to it when I was sure of the rest of the design. Well… turns out I need something.

So a simple plan formed: basically make a slideshow explaining the mechanics of the game. Each game mode would have its own collection of images to describe how that mode functioned, and the player could advance through them at their own pace whenever they want. No forced tutorial or “Now you do the thing” hand holding. Know what your doing? Get straight to the puzzles. Want to figure it out yourself? Go for it. Need a hand figuring out the new mechanics? I got you covered. Completely lost? Simple explanation just a click/tap away.

When I was first making my tutorials I was doing “all the things”. Slowly introducing concepts and elements so as to not overwhelm. Showing patterns in the puzzle without going “Here: see this!” But in all that I forgot one of the first design principles I was ever taught: K.I.S.S. Keep It Simple Stupid. And that is what the new design is: simple and too the point.