Where were we before we were so rudely interrupted by my extreme laziness? In my last post, we went over the basics of how shadows operate in Where Shadows Slumber. This week, we’ll pick up where we left off, and I’ll describe the way I actually implemented shadows, and the reasons for doing so.

Last time, I described two different ways to think about objects changing in shadow. Unfortunately, I did so in a sentence that, in retrospect, looks simply confusing:

[Things] can always change when put into shadow, or they can only change when you move around the object casting the shadow, so you’re on the other side of the casting object, relative to the changing object.

Yeah, that’s no good. So let’s figure out what this means, in a way that’s a little longer, but easier to grasp. We’ll use the classic pillar / bridge problem, where the pillar is casting shadow, and the bridge is changing with that shadow.

If I walk past the pillar, the shadow will overcome the bridge. If I continue walking, the shadow will move, the bridge will be revealed, and at this point, it should have changed. This is exactly what we want.

Not only is the pillar / bridge problem less violent than the trolley problem, it’s more relevant!

Now consider the scenario where I start to walk past the pillar again. The shadow overcomes the bridge again, but this time, I stop walking, leaving the bridge in shadow. Instead of continuing forward, I turn around and go back. The shadow moves, so we can see the bridge again, but we’re on the same side of the pillar as we started. Now the question arises – should the bridge have changed?

This is a very important question when considering this mechanic. Thinking about it from a ‘pure’ standpoint, of course the bridge should have changed – it was in shadow. After all, that’s the rule, right?

This was exactly my thought process, and is why I implemented the mechanic in the way I shared in my last post. The early prototype we made behaves in exactly this way. However, as I got further into level design, I realized that this is not what we want. In order for many of our level designs to work, the above scenario would need to result in the bridge not changing.

When designing levels for a game like this, there are a number of considerations to make, but one of the most important is to remember that the player will not always do what you want. I may want the player to walk around the pillar, but the player may instead decide to walk behind the pillar, and then turn around. If I need the player to end up on the far side of the pillar (for a story event, part of the puzzle, etc.), that becomes hard to accomplish with the current version of the shadow mechanic.

So, it seems that we need to update the implementation of our mechanic. The way we want it to work has more to do with what side of a shadow-casting object we’re on – the bridge can only change when we move around the pillar.

Fortunately, this is actually an easier problem than the previous one. When we think about it this way, we don’t even need to use shadows – what we’re really checking is when we pass the object. When the light (player), the blocking object (pillar), and the shadow object (bridge) are all in a row (collinear), we can simply know that the object is in shadow rather than checking. This is true when we make a few assumptions:

• Both the pillar and the bridge are about the same size. This means that we may have to break the bridge up into a number of 1×1 ‘shadow objects’.
• Each light involved originates from a single point (so point/spot lights, not directional lights).
• The bridge is further away from the player than the pillar.

When all of these conditions are met, we can ignore the shadow itself, and just change the bridge when the player passes the pillar. It’s a little hard to conceptualize, but a picture is worth a thousand words!

Alright, maybe like 500…

At the moment the player passes this ‘collinear point’, we trigger the shadow object to change (note that at that moment, the shadow object will be entirely in shadow). But the shadow is just there for cosmetic purposes, like a magician’s illusion – it’s so you don’t see the trick!

As I said before, this problem is much easier to solve – every frame, we simply compare the angle from the player to the blocking object with the angle from the player to the shadow object. When those angles switch, it means that the shadow object is in shadow and should change.

In this way, we can easily keep track of when a shadow object should change. There are a few ways in which this situation can become more complicated – if there are multiple lights or blockers that should affect a single shadow object, if there are multiple shadow objects that should use a different set of lights or blockers, etc. These are all very important things, but they’re all things that can be implemented by carefully extending the system we laid out above. As such, implementing them is left as an exercise to the reader : )

There are still ways we can use the previous implementation to help out with the shadow system. There are a few cases where we might need to actually know if an object is in shadow, rather than just making the assumption that it is. Thus, our shadow system includes a sort of ‘back-up’ shadow-detection – in certain cases, we fall back on the more accurate, more expensive shadow detection we worked on in my last post.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

That finishes up our high-level overview of our implementation of the shadow mechanic – I hope you enjoyed it. Let us know if you have any questions or feedback! As always, you can find out more about the game at WhereShadowsSlumber.com, find us on Twitter (@GameRevenant), Facebook, itch.io, or Twitch, and feel free to email us directly with any questions or feedback at contact@GameRevenant.com.

Jack Kelly is the head developer and designer for Where Shadows Slumber.

Throughout this blog, I’m planning on doing a number of posts which outline the mechanics of Where Shadows Slumber, and how they work. Now, there are plenty of very interesting mechanics that I can (and probably will) go over. However, there are probably a lot of blog posts and tutorials out there describing path finding, object pooling, shaders, and everything else. So, the mechanic I’m going to start with is the one that is the most unique to Where Shadows Slumber – the mechanic behind the shadows.

A quick disclaimer on the nature of this post – please note that this is not an in-depth description of the exact code we used for the shadows, nor is it an attempt to tell you the correct way to think about or implement such things. I’m sure a seasoned veteran of coding and game design will be able to point out a few inconsistencies or inefficiencies in our shadow system. Rather, this is meant to be a high-level overview of my thought process while I created this system, and how those thoughts changed throughout the process. Also, since we have been working in Unity for the production of this game, I will probably be mentioning how Unity does stuff pretty often.

When playing Where Shadows Slumber, you may have noticed that sometimes, things change when they’re in shadow. In fact, you shouldn’t have been able to beat the game without figuring that out.

I think I’m just gonna use this GIF in every post…

Things change when they’re hidden by shadow and then revealed, but there are two (basic) ways to think about it – they can always change when put into shadow, or they can only change when you move around the object casting the shadow, so you’re on the other side of the casting object, relative to the changing object. One of these methods ended up making more sense to use in the game, but I implemented both of them on the way there, so I think it only makes sense to go over them both (even if it means stretching this post into two parts).

Now, these are both pretty simple problems at their cores, but there are a few interesting lessons. Let’s start with the first type of shadow, using the naive approach, which is exactly where I started a year or so ago.

So when an object is covered in shadow, the next time you see it, it should be different. The steps involved should look something like:

• Detect if the object is in shadow now
• Check if it was in shadow before (last frame)
• If it wasn’t, change it!

Using these steps, the object will change every time it’s put into shadow and then revealed. So, clearly, the most important thing to be able to do is detect when an object is in shadow.

Since the light in the game comes from the player’s lantern, everything that’s in shadow is essentially ‘blocked’ from the player’s view by some obstacle. Thinking about shadows in this way leads to the first pass at detecting when an object is in shadow – basically, just draw a line from the player (or the lantern) to the object. If it hits anything along the way, that means that the light isn’t going to reach the object, which means it’s in shadow.

Looks like Unity’s ray casting…

This process is pretty much the description of Unity’s ray casting: draw a ray from a point until it hits a Collider. So we just add a Collider to any object that might get in the way, and we have a simple ‘IsObjectInShadow’ function!

However, you may have noticed that there are a couple of reasons this won’t work, the most important being that it doesn’t behave correctly. Since casting a ray will only target one point, the shadow detection will only work for the exact position of the object. Anything with any amount of width or depth (so, anything) will say it’s in shadow when the center is in shadow, but the edges are not. This happens when the object is at the edge of the shadow, when it’s only partially shadowed. This is a pretty big problem if we’re going to be changing the object at that time, since the whole point is that the player won’t see the object when the change happens.

So we can detect when a point is in shadow, but just checking the exact position of an object isn’t enough. The easy solution is to simply check more points! By casting two rays, one toward the leftmost side of the object, one toward the rightmost, we can check if both of them are in shadow. If they are, then the whole object is in shadow. This version of our theoretical ‘IsObjectInShadow’ function works much better – as we move a character around a pillar, the object will more accurately determine whether or not it’s in shadow.

We can get the object’s leftmost/rightmost positions (relative to the player/light) by getting the objects dimensions, which we can either get from the Renderer component on the object (Unity will measure the visible object), or simply by placing some restriction on the size of the objects. Since Where Shadows Slumber uses a grid system, everything that changes with shadows is restricted to a 1 x 1 x 1 unit cube, in order to make shadow calculations easier.

Now comes the question – why is this version not good enough? We have to do a little math up front to get the left/right bounds, but after that, we simply have to cast a few rays, and we know whether or not our object is in shadow. Seems pretty good! And it is pretty good. It only works in two dimensions – if you move upward, above the object, the object will still think it’s in shadow – but that’s not too bad, and most level designs don’t involve a lot of vertical movement, so we can ignore it for now. The biggest problem with this version is that we have to add a Unity Collider component to every object that might cast a shadow. Then, every ray cast will test collision against every collider every frame (the reality is not quite this bad, but that’s the idea). This can become a problem in a scene with a lot of shadow objects and a lot of shadow casters, especially if you want different casters to affect different objects. We can improve upon this version with a little math and some clever thinking.

If we think about the way that shadows are cast, we can come up with a better way of determining if something is in shadow:

(There’s a reason Frank’s the artist, and I’m not.)

If we specify that every object is restricted to a 1 x 1 box (in the two non-height dimensions), then we can use some trigonometry to determine whether something is in shadow. I won’t get into the details of the actual math, just the overall conceptual parts. No matter the angle, the radius of the blocker will always be at least r (0.5). In the same way, no matter the angle, the radius of the shadow object will always be at most R (√2). Thus, by taking distance into account, we can always tell if the entirety of the shadow object (everything within the bigger circle) is put into shadow by the blocker (everything in the smaller circle).

By using this method, we can tell if a shadow object is in shadow without ray casts or Colliders, and we can do it for a specific object. In this way, we can specify which blockers affect which shadow objects, which gives us a lot more control over level design.

Now that we’re able to tell if an object is in shadow, the hard part is over. Every frame, we just follow the steps outlined above, for any shadow object. We check if it’s in shadow, then check if it was in shadow (meaning we have to keep track of whether or not it was in the previous frame). We change the object to the next state. The object will only change once, until the user sees it, when it’ll appear differently. Then, if it’s put in shadow again, it’ll change again. This allows us the flexibility and consistency of shadow objects.

As it turns out, this version of the shadow mechanic didn’t end up being the one that we needed for Where Shadows Slumber. The shadow mechanic that we actually did use will have to wait for Part 2. We already did a lot of the heavy lifting this time, so it shouldn’t be too hard to make some small adjustments to the work we did here.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I hope you enjoyed this first highlight of the shadow mechanic in Where Shadows Slumber. Hopefully it wasn’t too complex, and I was able to explain it well. Let us know if you have any feedback! As always, you can find out more about the game at WhereShadowsSlumber.com, find us on Twitter (@GameRevenant), Facebook, itch.io, or Twitch, and feel free to email us directly with any questions or feedback using contact@GameRevenant.com.

Jack Kelly is the head developer and designer for Where Shadows Slumber.

Welcome to the Where Shadows Slumber blog! I know Frank posted something last week, but this is my first post, so I’m going to pretend like I’m important or something. In case I’m not important and you don’t know who I am, I’m Jack – the head designer and lead engineer for Where Shadows Slumber. We’ve decided to do a blog to keep in touch with the people that really matter in the production of our game – the users!

So, since this is the very start of our blog, I figured that a good topic would have something to do with the very start of Where Shadows Slumber – the inception of the idea itself. If you haven’t played yet, you definitely should (and how did you end up here?). If you have, then you probably know that the core mechanic of the game is rather interesting, and isn’t something you see, or think of, every day. So how did I come up with it? I get this question a lot, and I never have a satisfying answer for it.

Watch the bridge – it appears and disappears!

I’ve always been a gamer, and thus a game designer, even if it’s usually just in the back of my mind. I’m always thinking about what might be a good game design. A kid walking down the street, avoiding cracks in the sidewalk? Maybe that could make a good game. The picture on that billboard? Looks like a cool puzzle to me – can I expand on it? These thoughts are always floating around my head, and, to be honest, 99% of them are completely worthless. Almost everything I think of has an inherent flaw, or has already been done, or just wouldn’t be fun.

However, it’s the other 1% (it’s probably far less, honestly) that matters. I find that these few half-decent ideas often come up when I’m thinking about the design of existing games, since they’re often far more in tune with what users might be looking for. And I think that’s an important point – no one wants to play Generic Shooter 257342, but a lot of people are willing to give a new, quirky platformer a shot.

Enter Monument Valley. Yeah, I said it, and I’m gonna pander commit a whole paragraph to it. Monument Valley is one of the greatest mobile games I have ever played. Monument Valley took a simple idea and a simple aesthetic, polished them both into a well-oiled game engine, and gave us an incredible experience based around an interesting, understandable mechanic. It wasn’t difficult, but it made you think. I love Monument Valley, and if you haven’t played it, you should go do that. If you have played it, you can probably tell that it was a pretty big inspiration for Where Shadows Slumber, and despite the many reasons for that, there’s one word (which I just learned) that I would use to describe why that is: frisson.

fris·son

frēˈsôn/

noun

1. a sudden strong feeling of excitement or fear; a thrill.

   “a frisson of excitement”

The way I think of it, frisson is that feeling you get when something really cool happens. When you figure something out, and it makes you realize that the universe fits together in a really awesome way (the math nerds out there know what I’m talking about). In short, it’s the feeling you get when you solve, understand, and appreciate a really cool puzzle. That feeling stood out so drastically when playing Monument Valley that it made me realize – this is why I play puzzle games, and this is the feeling that puzzle games should strive to inspire.

So Monument Valley came out, and I played it, and I loved it. This was right around the time of the lackluster culmination of our previous project, SkyRunner (go check it out!), and it made me want to try to create something just as unique, interesting, and beautiful. So I continued thinking about potential game ideas, but I started aiming for something new, something interesting, something that hadn’t really been done before. I never sat down and tried to think of a great idea, I just tried to let them come to me.

Left: Monument Valley, by ustwo games. Right: Where Shadows Slumber, by Game Revenant.

And then (and this is the unsatisfying answer that I have to give everyone), the idea came to me. I don’t remember how or when or where, but it just came to me – gradually. It didn’t start out as shadows – basically, it was the idea that anything that you can’t see might be different from the way you remember. You don’t know – you can’t see it! This eventually developed into the idea of shadows, because we decided on creating a third-person game, and shadows are a good way to show that something ‘can’t be seen’.

Now this idea is by no means new. Erwin Schrödinger stuck a cat in a box with the same general concept. If you look, you can find other instances (in fact, you don’t even have to look – just click here or here.) In fact, I remember watching a proof-of-concept demo for a video game based on this exact idea – anything you couldn’t see could change. So it wasn’t a brand new idea, but it was definitely something novel, something interesting, something that we hadn’t seen in the mobile gaming space, and something we thought we could design a lot of fun puzzles around. After a few conversations with Frank, we decided to put together a small initial demo for the first version of Where Shadows Slumber.

We ended up falling in love with both the concept and the aesthetic we had managed to cultivate. For probably the first time in my life, I can actually say that, 18 months or so after I had the idea, we have managed to create a game that actually looks every bit as good as what had first popped into my head. I’m really proud of the work we’ve done to get here (which you’ll hear about if you’re willing to continue reading my hackneyed posts), and I’m very excited for the upcoming phase of production.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

Thanks for tuning in, I hope you enjoyed reading about the inception of the idea for our game, Where Shadows Slumber. As always, you can find out more about the game at WhereShadowsSlumber.com, find us on Twitter (@GameRevenant), Facebook, or Frank’s game development Twitch stream – and feel free to email us directly with any questions or feedback at contact@GameRevenant.com. Next week, Frank will talk about our development process and how we manage our time.

Jack Kelly is the head developer and designer for Where Shadows Slumber.