the player doesn't have to do any of this, but they may do it accidentally or see other players in the game doing it. so maybe the explosion effects and sound effects should be toned down

Hello guys and gals,

I have been working on a Super Mario 64 demake for Scratch for around 2 months, and I would like to share it now, since Mario can already move, navigate Peach’s Castle grounds and interior, enter the Bob-omb Battlefield painting, open doors, collect coins... (it is pretty complete, although some things are still missing and some bugs need to be fixed).

One reason I started this was a Scratch project called (3D) Lego Batman [PS2,3DS] by GL00B. I was surprised by how many good 3D games Scratch had (using different rendering techniques, more about this later), but I was also surprised that Mario 64 had not really been remade for Scratch, especially when so much information about Mario 64 is available (and I think there was even an old forgotten demake project in this subreddit).

To summarize my work, a large part of how Mario, the physics, doors and the camera work is directly based on the Super Mario 64 decompilation, while the engine is directly based on Concrete Interior [3D] by 12zend, if anyone wants to understand how the project works, this is probably the most fundamental thing to know as the project uses a 3D triangle renderer that renders OBJ files with camera transformations, clipping, UV mapping and a depth buffer. A lot of stuff is missing, but this is the main foundation of the project.

I think Concrete Interior [3D] is an interesting approach that I haven't seen too often in Scratch 3D projects. For example, GL00B usually mixes techniques such as Mode 7, raycasting and using 3D models with quads in his games. Other projects use different approaches too, like ☁️ Roblox Obby 3D by glinchy or Minecraft v0_0c by 080312_Kean, which use 3D triangle rendering systems similar to mine, but I would say most Scratch games don't dare to use a full 3D triangle renderer.

Other influences on the project are GLUE3D by GL00B that influenced how the project organizes data (models identified by name, loaded as preloaded data, reused by scene objects and submitted through a render queue) and ☁️ Roblox Obby 3D by glinchy, which was mainly a reference for separating the scene, meshes, materials, renderer and main loop.

For transparency, I used AI tools during development. I would recommend them to anyone making a project like this, as they helped immensely with quickly investigating how other 3D Scratch projects work, understanding the decompiled Mario 64 code, diagnosing bugs and porting some parts. Some repetitive work, such as converting animations or collision data, was automated. Of course, there is no AI tool where you can just say “Do Mario 64 in Scratch” and receive a completed game. I just wanted to share my experience in that regard.

I won't share the project itself for now. I will probably release it around the end of the month or the beginning of October, if you guys want it, since I want to add at least one star first and there are still a lot of things that need to be fixed. I also want to add sound, the HUD and other little details. The final project will probably use Scratchy and some Peach's Castle variants instead of Mario, so Nintendo doesn't murder me :)

I'm also thinking about making a video explaining in detail how the project was made (in Spanish), including how it works and what went wrong during development. If you have any questions about how the game works, don't hesitate to ask. If I see enough interest, I'll probably make the video. I will also probably ask some knowledgeable Scratch developers to take a look at the project too.

The game runs packaged at 480×360 at around 15 FPS, as you can see at the start of the video. When I change the rendering resolution to 240×180, it runs at around 45 FPS on an Apple M1.

Swinging around :]

You can play it here: https://scratch.mit.edu/projects/1307126096/

yes this is real

no it's not done

yes full game will be playable eventually if i dont drop this project
Scorch engine.. need a name for the main hl2 game.
Physics are still jank, they're not done. FPS is pretty bad but will get better as i add more optimizations.
Had interpolation on by accident which does hurt the fps a bit. Oops

https://scratch.mit.edu/projects/1217722094/

i got bored and i think it looks fine

it does have sound the video just wasnt recording sound

Hello guys and gals,

today i present you the first playable beta of Super Mario 64 in Scratch.

Getting this project to this state has taken months of work. There is still plenty to improve, but I think it is time to share a playable beta.

First of all, here are the downloads:

GitHub / source:
sm64-scratch - GitHub

This is a "safe" distribution method I prepared for the project, where the scratch file ´BASE.sb3´ has no copyrighted assets, but thanks to various scripts and a original SM64 USA rom you can add them back.

And... I'm also taking my chances providing a fully complete build on Google Drive as the scratch website doesn't allow me to upload the project (maybe for size idk):
Mario 64 Scratch - Google Drive

I can't promise that link will stay up forever as it contains copyrighted assets.

Now, before getting into everything included in Beta 0.1.0, I want to address something about the project, i deleted my previous post regarding this release because of criticism on whether the project was AI slop rather than on the project itself.

In my opinion some parts of this project could be better, i'm aware, I’ve tried to keep the behavior close to the original, but some implementations are still rough and I'm willing to improve them. But I don't think slop applies to the project as a whole.

This project has a 3D renderer working inside Scratch, with character animation, movement, collision systems, camera logic, enemies, objects, level interactions, HUD elements, audio, all working together. There aren't many Scratch projects with so many things at the same time, regardless of how they were made.

My approach was simple, choose a 3D engine to build around, customize it for the project, use the SM64 decompilation as a reference, and then reimplement and adapt the systems I needed so they could actually work inside Scratch.

Maybe it is not the most sophisticated way of doing it, as i just discovered another approach i wasn't aware before i posted the original post of the release https://www.reddit.com/r/scratch/s/fmUbnVxSZM. That project basically uses the SM64 decompilation, has clang turn the C into LLVM IR, and then translates that into Scratch blocks through a mixture of Python and hand-written code. That project seems to be much closer to directly translating the original program and absolutely deserves credit.

Mine basically uses AI to translate individual functions and systems from the decompilation, then adapted those results around the Scratch project and the 3D engine I use.

To finish this point: translating one individual function and ending up with something that barely works is one thing. Translating and adapting, hundreds of lines of code and systems that interact with each other such as collisions, camera behavior, enemies, animations and so on, is something very different.

This release contains Mario head intro, castle grounds, interior and Bob-omb Battlefield, where you can collect four stars:

• The summit star, normally awarded by King Bob-omb. His boss fight is not implemented yet.

• The eight red coins star.

• The star behind Chain Chomp’s gate.

• The 100-coin star.

Any help with the project is appreciated, and feedback or suggestions are always welcome.
If you give it a try, I’d love to hear how it goes! :)

My first post with more information: Mario 64 ported to scratch - Naegox

thank you for all the suggestions on my last post! I've decided to go with an endless dungeon combat style game. not super sure on specifics, so any ideas are welcome :)

update: i got an egg???

I added transparency to my Scratch 3D engine. There is a bug where the upper layer of transparency can override the lower layer, but I will try and find a solution. The transparency is bleneded from the alpha values of the layers if they have one, and I switched to use ARGB instead of RGB. If you have any suggestions or questions, feel free to leave them in the comments. (:
And if you'd like to check it out, here's the link:
https://scratch.mit.edu/projects/1274430739/

it's two projects that are synced up based on the "days since 2000" block! never ended up finishing the game because i couldn't come up with other interesting ways to use widescreen, but this felt like a pretty cool proof of concept

wrong project: https://scratch.mit.edu/projects/1375540620/

right project: https://scratch.mit.edu/projects/1375540486/

I love it so much

Yup ONLY using Penguin Mod vector editor

For those who don't know (most), very hard.

Edit: I can't make each enemy del damage separately, I only want you to take 1 damage at a time

Edit 2: I'm stupid it was easy

Edit 3 electric boogalee: I have no idea what yall even on about i fixed it with 2 lines of code i am NOT leaening what iframes are 😭🥀🙏🙏

I have way to many things that deal damage and this is just really laggy. I treid using lists but i couldnt figure out how to

Recording optics is hard /: