I really like the game's look. Did you try alternative styles before settling on this one?
The game started off with a very simplistic style due to the 48-hour time limit of the game jam it was made in; there are some stylistic shortcuts I tend to take when I need to hurry, and as a result the first version of Baba (still available via itch.io) uses a black background and default Windows palette. Once I started making the full version, I momentarily worked using the sprites of the game jam with updated colours, then made a couple mockups of what the game could look like and ultimately fairly quickly settled on the current wobbly style (looking at some pics, settling on the final style took about 1½ months). I've used a wobbly style like this in multiple previous games, so it was a relatively easy pick for me.
I've been consistently worried that the simplistic/pixelated look will drive people away, and as such it has been very encouraging to hear that people like the looks of the game. Thank you!
Aside from the music and visuals, have the mechanics and scope of the game changed much between the early version and the new one?
The scope of the game has inflated very heavily over time. At the beginning of development I added a lot of words that I felt could be interesting, and while I've retired a couple (Slip and Grab) for various reasons, most of the words have been left in. An older notebook scribble tells me that I initially estimated for there to be some 60 or so levels in total, if even that, which is amusing considering that I ended up with 200+ of them. I've been afraid that the game might become too exhausting to play, but at the same time the inflating scope has allowed me to really think through the systems of the game and figure out certain mechanics that really explore the concept deeply - the game would have been a much narrower experience had I gone with early concepts only. Of course other people have given lots of ideas and inspiration as well.
Is there a backstory to the game? Who and what is Baba?
There is a backstory of sorts and the game features a couple cutscenes (only in the form of intro- and ending-type events, though); however, the narrative of the game is very much more concerned with the rule system and the structure of the game world than with Baba or
the other beings seen in the game. As far as the game's concerned, Baba is a cutesy sheep/cat/goat/dog who just happened to be settled with ‘Youness’ or a consciousness of sorts. In the jam version Baba was intended to be a robot with antennae, but a colleague, Jason Boyer, made some really sweet fanart of Baba, interpreting them as a humanoid goat creature (with the antennae becoming horns), and I decided to change Baba's looks more to that direction as I updated the sprites.
Could Baba is You have been a horror game, do you think? It's a game about warping the rules of reality, after all, which could be quite scary in a different context.
I don't think I would've been able to turn Baba into a horror game; there would've been many pitfalls of accidental cheesiness and I think I would've fallen into them had I thought to try. I suppose even as the game is now there are some creepy elements in it, though, at least for some players, considering how meddling with the rules can alter and remove consciousnesses of beings.
Do you think Baba is You will help people better understand how games work? The way you push around rules in the game reminds me a little of Scratch, where you can plug scripts together in blocks.
It's very hard to say at this point. The syntax Baba offers is quite unlike that of actual programming, so in that sense it might not be overly helpful, but on the other hand Baba could offer someone the spark to start studying actual programming languages in case they find the rule-shuffling similarly exciting.
What's been the most challenging aspect of developing the game so far?
Depends a bit on how we define "developing"; marketing in today's environment is exceedingly tough and scary, for example. But if we deal with purely game design -related issues, I'd say that two things come to mind first and foremost: composing of certain songs and writing code for the cutscenes. The former is purely an inspiration-related issue - some tunes in the game took me a long time to come up with, which made the process quite stressful. Somehow a musical theme for a forest area just didn't show up until after waiting for it half a year or so. The latter is partially inspiration and partially coding-related issue; Baba's basic engine is fairly rigid in order to accommodate all the rule-changing shenanigans, so implementing a more flexible system for cutscenes was very tough. Partially as a result of that figuring out the contents of the cutscenes was also difficult.
What's your process for testing the game? Is it time-consuming to come up with the puzzles, and make sure they're solvable?
Baba's basic concept offers so much food for puzzle ideas that I mostly haven't had to struggle to come up with them, with some notable exceptions. I've tried to follow a principle of having every level have as unique an interaction/gimmick as possible, both to keep the amount of levels down and to explore the concept more deeply. Looking at the level folder, it'd seem that there have been around 70-80 levels that have somehow not made it into the final game, so some ideas have definitely been stinkers. Generally the most common issue
hasn't been that a puzzle wasn't solvable, though, but rather that it had excessive unintended solutions (or that it was just frustrating/boring.)
As for testing, I've been lucky to have a bunch of friends and colleagues and helpful people who've kindly offered feedback throughout development. It's easy to test that a level can be solved at all by myself, but said unintended solutions are way harder to spot and as a result some levels have gone through many many iterations of fixing and testing. Closer to release I've tried to approach testing in a bit more organized manner and that has been very helpful - watching a video of someone playing allows spotting oddities very easily.
Similarly, do you have to constantly check to make sure the player can't break the game altogether?
As mentioned in the answer to the previous question, this has definitely been the more common issue with the game's levels. In many cases I've gotten a nice alternative variant out of an unintended solution, though, in cases where a tester finds a way to solve a level that's not what I had in mind but novel in a different way.
The game's concept might be difficult to describe verbally; do you think the advent of YouTube and streaming have made unusual game concepts easier to show to people?
Depends very much on the nature of the unusualness. Slow-paced, turn-based, difficult puzzle games are some of the hardest games to stream/make videos of in terms of garnering an audience, I feel, because the optimal way of playing them is usually very slow and non-flashy, and the satisfaction of solving a level might not be conveyed very well to an audience. I'd say that media formats like gifs (and gif-equivalents) have been very useful in sharing unusual concepts, though, since those allow cutting off the buildup and thinking and just displaying whatever the unusual element actually is. This isn't to say that streaming/videos wasn't helpful and useful, even to a game like Baba Is You.
I'm super looking forward to seeing someone stream Baba; I very much want to see their reaction to some of the twists of the game! Streams have been a very neat source of personal encouragement for me.
Have you thought about how the game could be localised into different languages, given that language is quite a big part of the game's rules?
This has been given a lot of thought, and at this point it seems clear that the game is pretty much impossible to localise entirely to most languages without actually changing the puzzles. At this point we're planning to eventually translate the UI, but unless we figure out something the actual game elements will have to remain as they are. To give an example, Russian doesn't have a present tense "be" verb in the same way English does, so just the sentence "Baba Is You" isn't translatable while keeping the word count and not resorting to more outlandish options.
What's it been like when showing Baba is You to players at expos and festivals? Are you surprised at how quickly they pick the rules up? Or are there times when you're surprised at how hard they find it?
I enjoy talking and presenting my stuff so my experiences at events have been mainly positive. I've definitely had both kinds of experiences - I think my general expectation has been that the game is hard to "get", and in many cases I've been surprised at how quickly
people grasp the idea, while in others I've noted that people have intuitions about the game's mechanics that differ enough from my own that I've wanted to clarify some of the implications of the game mechanics.
How much of a boost is it, as an indie developer, to have the support and interest of Nintendo?
In more business-y terms that is very hard to gauge, but there's a lot of excitement about the Switch so I'd definitely assume that it has given a boost to the attention the game has gotten. On a personal level the impact has been very real, in any case - I've been a fan of Nintendo games my whole life so getting to release a game on a Nintendo console has been very cool. On top of that, I had an extremely sweet experience showcasing Baba at Nintendo's Nindies booth during Gamescom last year, the crew at the booth was very kind and encouraging.
Baba is You releases on Switch and Windows on the 13 March.