I made this video for people having trouble getting the game to work. Also...I just really wanted to play this awesome game again. Now I want jelly...and toast.

The reason it doesn't work on edge is because the collision doesn't work, even between pixels of the same object, making mario shrink. That's because Edge has issues with WebGL (which is needed to run Jelly Mario).

As someone who's made physics sims like this before, Mario collapsing into a ball like that gives me PTSD. Things like these are an absolute nightmare to work with and make

The visual of Mario swimming through the air like a damn jellyfish is so funny

10:48 Apparently Mario hates the game because it says "End the alpha"

I didn't know us YouTube commenters sounded like Diagonal Mario. LOL

I had no idea Jelly Mario actually performed like this. I played this game on Microsoft edge and WAS able to beat it after many, many tries. The fact that there is no collision in that version meant I was free to move Mario as I pleased, but had to be VERY careful with the sensitivity and timing of his movement (turning it into more of a rhythm game than a goofy platformer). Try to imagine the cape feather in SMW, but if your timing and inputs are off, you curl into a ball and explode.

1:39 I should note that it works fine in older versions of Microsoft Edge that aren't built on Chromium (Basically, any version released before the icon redesign will work.)

Broken Jelly Mario. He goes absolutely insane after seconds.

10:29
My dog: pukes
Also my dog 3 seconds later:

What Mario actually experiences after eating a mushroom.

0:18 my boy Mario got dragged to the shadow realm

the reason why mario is so slow on Chrome is because you need to have enabled "hardware acceleration" in the system setting of the chrome browser.

Me trying to run from the monster in my dream:

"That was luck but we'll call it skill."
Basically my friends when they find diamonds in Minecraft. Yeah and me too...

It's been a while since this video was uploaded, but as a programmer myself, it looks kind the game was having trouble with floating point numbers (numbers with decimals) not being what the collision functions were designed for so certain checks wouldn't trigger as intended. It's kind of strange when things like that happen because things like floating point math is usually standardized between various browsers with external tools like webGL.

Ah yes, browser incompatibility. As a JS gamedev myself, I can say fairly confidently that making sure that your already high-effort game (not that I know much about high-effort games lol) works on every major browser is a huge pain, since a lot of features are missing or work screwed sideways, even if they're part of the W3C standard.

"Is Jelly Mario broken?"
Heh.

its a bird! its a plane! no its a jelly mario?! 2:27

If jelly mario had co-op i feel like player 2 would be controlled with wasd and player 1 will be controlled with arrow keys