Hi everyone.
Soon we will publish the post-ld version of our game.
Now we are fixing bugs (yes yes the protagonist’s jump will be fixed :)), creating a new monsters and adding graphics effects. We are planning to publish post-ld version in a few days.
We have fixed some issues and bugs with our newest update for “Invent The Wheel!”
Changes/Fixes include:
1) Overdrawing – You only have a limited area in which you can draw.
2) No more timer – You have an infinite amount of time to draw your wheel.
3) Updated controls – You now draw with RMB, which appeared to be easier during our testing.
4) White flag – You can now abort your run and retry.
We also fixed some minor display bugs that occasionally appeared pre-fix.
Enjoy your new (and hopefully improved!) wheeling experience! 😉
http://ludumdare.com/compo/ludum-dare-36/?action=preview&uid=32967
Just added a few last minute features and fixed too many little bugs to mention ahead of the Jam submission deadline. If you played it before, you may want to try it again. Mostly (I hope) the bugs weren’t noticeable. The HTML5 build now renders at correct size though!
Howdy fellow jammers,
While I’m at work on cooking up a postmortem post for you to feast upon, you can check out and rate Aether Crypt if you haven’t already. If you’re fond of ambient stuff, a big fan of metroivania style games, a platformer addict or a chemistry nerd, you might enjoy giving it a try. Here’s a couple of screenshots to give you a taste of what you’re in for.
Have a good one!
Tselmek out.
Check out my post-mortem for Foreshift here:
Foreshift: Ludum Dare #35 post-mortem
I talk mainly about how I made the art and sound for the game.
Also, uploaded a bug fix for the multiple-spawning balls. Boy, it was so tempting to want to make a few subtle changes for the overly-difficult level 6, but I didn’t feel that would be in the spirit of the compo!
Sweet!
I fixed my black-sprites bug in WebGL!
Playable inside the entry page with the power of WebGL!
Have fun!
We just pushed a new version of our LD33 jam entry “Human Zoo”. This fix a crash in the HTML5 version when playing for several minute and going out of memory. We also give the offline solo “.exe” version and a multiplayer version. With this version, you can play multiplayer on the same machine, in lan, or through the web. We played a bit of the multiplayer, and its fun to compete or cooperate. You can grab a stunned player either to save him or to put him back in the cage. Playing the game yourself in multiplayer give a lot of emergent ideas. Let us know if you had fun !
We also recorded a timelapse while making graphics :
I’ve expanded the tutorial with camera info, as well as sped up the movement of the camera, and more, based on initial feedback.
Thank you all so much for the feedback! 😀
Play postcompo version! (full gamepad support now)
Last Rooftop Hero
Ok, guys. This is fail of pretty epic proportions. I forgot to disable WASD in my compo entry Last Rooftop Hero. The whole idea of gameplay was to use one single button only for the whole game. I’ve NEVER used WASD during testing, and thought everyone had a one-button game. I think I’ve just made these controls out of habit and forgot about them.
Fixing this “typo” took me 5 seconds, should be a proper version without WASD now. The thing is… You never know. The game has been online for 3 days and now I don’t really know how many have people found this and had “wrong” gameplay. And not a single one person have told me up to this point 😀
Thanks to Ellian, who wrote a comment about this.
I just re-uploaded my game with fixes. You should be able to play my game, even if you don’t have any controllers connected.
So… turns out I forgot to disable some menu links when the menu is invisible, which means you can accidentally click them during the game… which immediately kicks you out of the game and opens up my website in a new tab. Annoying as all hell if you’re in the midst of shooting rockets at the time. I’m going to go ahead and say this should be okay to fix without disqualifying me, but if anyone disagrees… let me know?
Herp a derp.
edit: Double herp a derp. Apparently the end game screen wasn’t showing up AT ALL. Way to go me!
So turns out I had a complete brain fail during the Ludum Dare weekend and totally failed to make the speed of my game’s player character independent of the FPS, which I only discovered when I accidentally destroyed Chrome a bit and suddenly it started chugging horribly, simulating playing In The Blood on a tired old computer.
I’d used the delta for computing velocity… but then multiplied it by 0.000005 for no reason I can actually remember now and the result is that the delta had virtually no effect whatsoever. So.. I fixed it. I REALLY hope this is okay, dear people in charge of such matters. It’s still the same game, no new features, but hopefully everyone playing it will have the same frustrating, tormenting and short-lived experience it was designed to provide. I wanted the game to be a difficult, challenging and hopefully addictive little action arcade game but when you’re moving ten times slower than you should? Oops.
I’ve also added a Post Compo version now! It’s the same game but I managed to add a bit of the visual Woo that I didn’t have time to do during the 48hours. It destroys the mood entirely but things are a lot clearer and hopefully a bit less motion sickness inducing. Again, sorry about that too.
You can play both frustratingly difficult versions on its compo page!
Incidentally, if you like Super Hexagon style ridiculously difficult action arcade games you might enjoy other competition entries Underneath Our Faces and Diver X … and would love to hear about any other games in the compo like this!
I recently discovered that my game, North Exit, has a large, game-ruining bug; I somehow omitted the code for detecting a lose condition, so the player can’t lose the game (no, no that game, but yeah).
However, that doesn’t really make the game unwinnable or less playable — it just makes it infinitely easier.
My plea for help is: is it okay to re-upload the game with that single bug fix? Will that break any Jam rules? I know the Jam is relatively lax on rules, but I just want to be doubly sure. :’D
Thank you to anyone who’ll reply! I’ll go ahead and play your games too if you respond! <3
Thanks to all the great constructive feedback I’ve received from you, I decided to make a postcompo version of my game.
It mostly adresses the default controls and tries to fix some of the collision bugs.
If you’ve already played and rated the original entry, give it a go at:
http://www.ludumdare.com/compo/ludum-dare-27/?action=preview&uid=11939
Fixed a few issues with Karyote:
The disappearing food bug was the main thing. After playing for a few minutes, it seemed like everything disappeared. That wasn’t supposed to happen. Now you can play a lot longer. This is closer to the way it was meant to be all along.
[mild spoiler alert]: fully implemented the mote behavior. I don’t want to give it away, too much, but they now do something. OK, I’ll tell you, when you mutate, they mutate also, into one of the other food types that are present in the game.
Slightly improved the title screen by adding a larger title font. The old title text is now kindof a subtitle, I guess. I think it looks a lot nicer. Also added a graphic to the title screen which gives the controls, so you know how to play without reading the entry page. And added a timer to the Game Over to return to the title screen if you don’t start a new game after a few seconds.
Give it a try now:
The Windows build has nicer particle effects due to the way colors are rendered by the Game Maker runner in HTML5.
Ran through the game again and noticed a few bugs, which are now fixed:
If you’ve already downloaded it and played it before, it’s worth downloading again and trying it out with the fixes. Gameplay should be a good bit more challenging than in 1.0.
