Так, а стамина вообще тратится? Я на изи забил кролика просто постоянно спамя удар и запрыгивая ему на голову.
oneir👁️mancer
Creator of
Recent community posts
Post-Mortem
Oh boy, what a month it was! And not just this month, I think I’ve been doing games for gamejams for 3 month non-stop. And so far SkyCrawler is my favorite game to work on!
What went right
The Ludum Dare jam was a great jump-start for the game! 72h constrains pushed me to focus on essentials, to come up with the strong hook and just work it to the bone. And then the rest of Devtober I could just work on those little features I discarded because they were time consuming, and just polish the game.
But then I remembered that I want to add some more levels and some new mechanics because the game is like 5 min long right now…
What went wrong
The scope of the game was a little too small, and yet most of the time I was just fixing and polishing what was already there, or experimenting with the new mechanics I just came up with. I didn’t have any plan in mind and just went with the wind.
And that’s why the last week was really straining for me. I had to rush a bunch of new levels, planning as I go. Naturally, I didn’t have nearly enough time to properly polish them. It was “last day of the jam” all over again.
Conclusions?
I was just making a game at my own pleasure. It’s not bad, but when you have a time constraint, you gotta do some planning. Otherwise I just lose my track.
Day 9
SkyCrawler didn’t really have any plan for a post-jam development. The game was designed as a jam game - something I can finish in 3 days of development, something that people can play through in 5-10 minites. And up until now I kinda went with the wind, fixing bugs, inplementing some cool mechanics I came up with.
So that’s what I was doing today. Planning. Deciding what should I change to make it into a 30 min long game instead. Deciding which design elements confine me, and which help me add new levels and iterate on mechanics.
Day 6
Not much done today. Mainly playtesting, bug-fixing and polishing the new Web and Standalone build, and publishing it on Itch.io page.
Day 4
I’m just going to say it, refactoring game’s code is so frustrating. You deliberately break the game, and than work super hard just to get it to basically the same state it was at the beginning. It’s getting on my nerves.
So I took a little rest from coding, and instead worked on music and done some art for my game.
Day 3
Today’s, and probably tomorrow’s, work is reimplementing gravity. I actually had two “gravities”: first uses default Unity physics simulation, and it was used for player character only. Second one is a hardcoded gravity specifically for an enemy I added in the last day of the jam. I basically have two scripts that have almost identical code, plus a lot of hacky coupling with other components.
So I set to reimplement it and have one unified system, that is all clearly written in code and doesn’t use Unity physics simulation.
The idea behind my gravity implimentation is quite easy: find a collision point with a platform, get a normal in this point, use the tangent and the normal in this point as x and y axis.
For jumping I just fix normal vector until I collide with a platform. I also smooth “horizontal” movement in air, and to get horizontal velocity in local space I project character velocity on the tangent vector using dot product.
Day 2
So, it turns out it’s quite hard to do everything right on the first attempt. Transitioning to the next level worked like a charm, but restarting the level had a bunch of problems. Today I was fixing those: double animations, double sounds, resetting all the stuff that needed resetting, reenabling all that needs reenabling. I think I managed to make it again playable from beginning to end, but I still left a few hacks that need fixing and polishing.
Day 1 (not really)
Today’s work was focused on reimplementing level transitions. I try to design the levels to flow one into another, which helps me to have a certain structure to the world:
During the jam I decided to choose a hacky solution of keeping each level in a separate scene. While it generally worked, it resulted in little but noticeable stutters when a new scene was loaded into memory. Plus, scene transition would eat all the sounds and particle effects that were playing (if they weren’t set to persist between scenes).
So, I was fixing just that.
Since I treat my levels as one continuous level, the obvious solution would be to keep them in one scene:
The transinion from one methon to the other went smoothly, except for some resetting issues that came naturally with reloading the scene.
Hi! I come here from Ludum Dare, and I’ve decided to join this jam because I really want to continue working on my entry. Which means that I already have quite some progress on my game and an MVP that you can check out.
What is SkyCrawler?
SkyCrawler is a puzzle-platformer, that is focused on breaking your stereotypical concept of gravity. It pushes you to think of gravity outside the box and use that to solve platforming puzzles. The core mechanics is elegantly summarised with this picture:
You can already check the game out: https://oneir0mancer.itch.io/skycrawler
Or rate it on Ludum Dare: https://ldjam.com/events/ludum-dare/47/skycrawler
Tools I use
- Unity
- Photoshop for art
- Audacity for sounds
- Guitar Pro for writing music (yep, I’m a wierd one)
- ScreenToGif for making all those gifs
Quick progress recap
- How I came up with a core mechanics
- How I designed levels
- What progress I made just after Ludum Dare
What is my endgoal?
At the moment I just want to tidy up and refactor the code, because right now it is a mess. Then, I want to start propeply implementing some stuff that I had to cut at the end of the jam, like an enemy that you see on the last level. In my head the idea has really grown from a simple gimmick to a full-fledged platformer with a lot more movement mechanics, combat, and a dozen of pages of lore. And while I am hoping to make it all come true, realistically, I aim to introduce at least one new mechanic and at least double the amount of levels I currently have.
Hi. Thanks for the feedback you gave during the gamejam. I actually took some time to work on the concept and turn it into a full game. Check it out here: https://oneir0mancer.itch.io/cold-light
Hi. So, I did some testing and tweaking to make the inputs more smooth (not to mention all the other polishing I did to turn it into a full game). Check it out here: https://oneir0mancer.itch.io/cold-light
Hi. Well, I took some time to expand the concept, put back in a lot of stuff I discarded during gamejam, and turn it into a full game. Check it out here: https://oneir0mancer.itch.io/cold-light
Hi. I spent some time on polishing and making the game overall a better experience. Check it out here: https://oneir0mancer.itch.io/cold-light
Well, now you can actually change the signals you chose (not to mention a bunch of other new stuff). https://oneir0mancer.itch.io/cold-light
Guess what, now you can actually change the signal (not to mention a bunch of other new stuff). https://oneir0mancer.itch.io/cold-light
Post-Jam version is here. More levels, more polish, more stuff that I didn’t manage to fit in due to jam time constraint: oneir0mancer.itch.io/cold-light
It’s a tricky balance between too much input delay and too little. I designed it so that I myself feel comfortable playing, but also I thought that it would be much worse if your input would just randomly interrupt because you wasn’t quick enough to press the next button.
But yeah, the only way to really fix it is just lots and lots of playtesting.
I was planning on giving the player the ability to reset inputs, but I had to cut it due to jam time constraint.I do want to add it in future, as well as a bunch of other ideas I discarded.
As for the puzzles, well, in some cases I wanted them to be tight to force players to look for solutions that would help them overcome input delay. But maybe I went a little too much in some places.
I really liked the discussion Matt and Arthur had about escort mission on a theme reveal stream. So I started to explore ideas of how to make an escort mission into something more original and unique. It clicked quite quickly, and I ended up with a puzzle game where you, as an AI overseing an underground lab, need to TAKE CARE of a little girl and guide her to the exit, having only a limited control over that lab.
https://oneir0mancer.itch.io/cold-light
Also, I tried to incorporate the idea that “Take care” can stand for a farewell to someone, but it’s kinda only at the end of the game.
I didn’t really try to meet any challenges except for one of them that I really liked.
Although I think I also naturally met Extra Distance challenge: There is only one character besides you, the player, and you are separated with a screen of your computer, as well as thousands of meters of concrete and steel. In fact, you can’t even communicate directly, and need to come up with some inventive method of communication.
The challenge I purposefully went for was Extra Translation: Since you can’t communicate directly and the only things you can control are the lights of this underground lab, you have to invent a whole new language to communicate by blinking those lights. Well, rather you need to assign a particular sequence of lights to a particular action, but I’d still say it’s coming up with a language.
All in all, I really tried to achieve the feeling that even if you really try to take care of someone, you are never really in control of their actions.
So… The game looks really good. Except for the fact that all the graphics are from this asset pack. I’m not going to say it is bad, it just biases people to like this game more purely for its visuals.
Other than that, the game has got some solid platforming. A little bit more polishing, more levels, and it will be a great game.