Play game
Spewnicorn 3310's itch.io pageResults
| Criteria | Rank | Score* | Raw Score |
| Enjoyment | #7 | 4.250 | 4.250 |
| Overall | #121 | 3.667 | 3.667 |
| Design | #143 | 3.417 | 3.417 |
| Polish | #167 | 3.000 | 3.000 |
| Adherence to restrictions | #175 | 4.000 | 4.000 |
Ranked from 12 ratings. Score is adjusted from raw score by the median number of ratings per game in the jam.
Leave a comment
Log in with itch.io to leave a comment.
Comments
This is a really funny concept, with lots of interesting puzzle/platforming possibilities. Unfortunately the game crashed when I tried to fill the cup with vomit (which is itself pretty hilarious)
Ahh, that's a shame. Roughly how full did you manage to get it? I'm seeing more people get crashes at that particular point in the game (which is admittedly the only occasion you're required to produce a certain amount of vomit to progress) than I might have expected.
Not very full (it crashed a few seconds in), but then again, I had been vomiting everywhere previously just for the fun of it, so...
Ah, that might explain it - that level's not big enough for it to start clearing up vomit you've left behind you, which may have been a bit of an oversight on my part.
This is all I ever wanted.
This is a unique platformer, the sound effects came in really loud, just had to turn down the volume but I had a lot of fun playing it.
Whoops - sorry about that. The tones I generated in Audacity were absolutely deafening to begin with. I reduced the volume to 50% in the game itself, but apparently could have gone a fair bit lower.
Interesting game. First thing i did was shower in my own vomit. It was fun to play through and vomit everywhere. However, i ran into that same error as the others while holding vomit and filling the cup.
Thanks for giving it a go. That's definitely something I'll address in any future version - before submitting, I settled on simply allowing the error to happen rather than trying to guess at what point most people's devices would stop being able to cope with the number of objects on screen. Having learned that there's a specific universal limit to how much memory the game has available, though, it should be possible to work out how many I can get away with leaving floating around for everyone.
hahah, very funny idea! love it, but i think there a trouble with creating instance of tears as physic objects. BTW , make a full game with normal graphic it can become a MEME)
Yeah, it definitely freezes up if you spew too much in one place. I'm seriously considering putting together a non-Nokia version with brightly coloured graphics - the possibility of rainbow vomit was what originally drew me to the idea.
I like the idea, but where is the jetpack? :(
Also - potentially using vomiting as a way to create platforms to get through challenges? That might be something to take a look at!
Interesting game, barfed all the way out of memory. Console gave me this error: Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 16777216, (2) compile with ALLOW_MEMORY_GROWTH which adjusts the size at runtime but prevents some optimizations, or (3) set Module.TOTAL_MEMORY before the program runs.
Haha - yeah, I've had it freeze up on me after barfing too long as well. Currently the game will delete vomit particles a certain distance off screen (which I hope will accommodate players simply holding the puke button as they run), but it's entirely possible to spew more in one place than the game can handle. The final level actually draws attention to the possibility, so it's not something I'd try and fix in this Nokia Jam game (though would be quite a priority for a more polished version of the same thing).
I made this using GDevelop and I'm not sure it offers any easy method of actually expanding the amount of memory available, but it might be possible to assign each vomit particle a number and then start deleting the earliest ones once a certain quantity is reached. It's very handy to know that it is actually hitting a specific limit, rather than simply growing unmanageable for the machine it's running on. How did you get that error from the console? It would be really useful for me to check in future.
Pressing F12 in any modern desktop browser (Chrome, Firefox, Edge) opens up the dev tools. There's a console there along with some other super useful stuff if you're debugging webpages.