![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://sh.itjust.works/pictrs/image/045a2049-eb61-4960-88ba-97e7f1ffbf31.jpeg)
1·
7 months agoBalders Gate 2 was developed by Bioware and published by Interplay. That’s not to say Larian couldn’t have learned from it anyway, but it’s not a lesson they would have learned from experience.
Balders Gate 2 was developed by Bioware and published by Interplay. That’s not to say Larian couldn’t have learned from it anyway, but it’s not a lesson they would have learned from experience.
I don’t think I’ve ever seen ‘vise’ written down before, I always just assumed it was spelled ‘vice’! You learn something new every day
I’m not very familiar with TotK and I’m not sure how familiar you are with game development, but just in case you’re not very:
When making something like a shadow puzzle it is very unlikely they’re actually checking shadow conditions, and if they are it’s probably very sparse/only a couple of pixels.
For instance, if you know the position of the light source, the position of the shadow catcher and the position of the shadow receiver you could approximate the shadow casting with much simpler geometry. If Link is just treated as a box then you only need to check where each corner would cast a shadow and see if that overlaps the area you care about.
When done correctly the player would think it’s link’s shadow that’s being tested but in reality it’s nothing to do with the shadow, it’s just a much simpler estimation of a shadow that works well enough to trick players.
Game development is all smoke and mirrors. Tell the players one thing such as “This NPC is always at this location” then unload them when the player isn’t looking. It’s all sweet lies and I love it.