Roblox doesn’t allow sharing animations, so you need to reupload them to your profile in order for them to work (if i’m not mistaken I left them in Assets > Animations > Animation > KeyframeSequence (the one you reupload, the blue square). Other than that, like you already figured, you need to enable datastores for collectibles to work.
Work on the new version started last week, but it won’t be out until next year as the scripting needs to be redone from scratch.
the one you reupload, the blue square
Surprisingly reuploading the animations didn’t work! Maybe there is something I am missing? Can you clarify on the blue square?
Meant these, forgot the old icons got changed
If after reuploading and replacing the id’s the issue persists, make sure the animations are uploaded under the same profile/group as the game, and if nothing works, feel free to reach out in dms, I don’t wanna keep bumping the post.
Those edits make my head hurt 
Hi, is StreamingEnabled disabled? If not you’ll want to either disable it or place the files somewhere they won’t get deleted (updating the script references). If that’s not the issue feel free to dm me a repro file and I’ll look into it when I have time.
Figured it out, apparently if you have any other models named “Terrain” it confuses the script lol, thanks for the response though!
Is there any way to get this working on r6?
Yeah, you’ll want to replace the animations for R6 versions, and edit the scripts throwing errors so they use the R6 limbs and Motor6Ds.
Thanks! I was just wondering since I didn’t want to start working on a project just to realize I can’t do anything with this engine.
Hey there folks, it’s been a bit since I released the resource so I figured I might as well give you a little update on what’s planned to be added to the project.
Just wanna clarify that the main reason it’s taking so long is bc i’m redoing all from scratch besides the assets, and i’m working on it on the side, so no clue when it’s coming out if it ever is.
This time around the plan is to offer a short campaign to serve as a base for you to learn how to make your own cutscenes, quests, etc. Plan being to offer 3 worlds and the already available world being reworked to serve as the game’s hub (gotta clarify the worlds themselves won’t be part of the resource but the hub will and so will most assets and code).
Right now i’m working on the 1st world, which will be released idk, at some point in time? as it’s own separate demo, and when I have time i’ll update the main game to work along it and I’ll release the rest of the worlds when, again, I have time. Here’s some footage of one of the 5-6 sections it will feature (keep in mind collectibles haven’t been ported yet so it looks empty on that regard):
Truth is, i’m not good at balancing movesets, and it really showed with the moveset SNM released with (I tried to go for something different, more momentum based, and it didn’t work). This time around i’m going the good old adventure game style, no moveset, just power ups and mechanics, here’s 2 of the powerups:
?:The base game won’t feature a moveset, but the plan is to offer a new moveset separately, this one being a hybrid of the EH2018’s moveset and Egomoose’s i’m making for another game of mine, here’s some footage of it:
This moveset will offer:
With some of these moves being chainable, such as the dive land leading to a roll and such. I’m also considering adding combat to it, but no guarantees on that regard.
This should suffice the need for a moveset in most cases, with the base resource allowing to pick between any of the available movesets out there, you don’t need to stick with mine.
The plan is to offer a bunch of the content that couldn’t ship with the game originally, as well as reworking some of the existing one to feel more smooth, some of these include:
Back when SNM was released I wasn’t very fluent on OOP, so while some of the utilities the game relied on used it, the game for the most part had 1 script per system and that was it, 0 modularity, which meant lots of added complexity when editing the scripts and making them work with each other.
I don’t quite like how the code is organized at the moment, so on top of relying more on nested modules for additional ease of usage, for this version i’m considering using one of the following structures:
So it can be dragged and dropped with little to no issues (with exceptions such as code relying on the movement script which would be common), at the compromise of having repeated code (synced using packages, if synced at all).
With “Goodies” and “Resources” not existing because they’d be hidden away inside the modules.
You’ll still need to edit the code most of the time, but it’ll be easier to find than rn.
Initially I was going with option one as i’d like the resource to be easy to use, but I think i’ll end up going with the second as I want the resource to be as easy to scale for bigger projects as possible, i’m going to be using this myself after all, but i’m open to suggestions.
And that’s about all the news about the game i’ve got atm, hoping to release the update this year but maybe I won’t have time to, we’ll see how it goes.
Any feedback or suggestions are much appreciated as always, if anyone needs help or wants to contribute to the project my DMs are open, as well as the post itself, socials are on the main post, and that’s about it, sorry for bumping the post wish there was a way to not do that.
Hi, nice! I checked out your last one, thanks again for sharing!
Is there a .rbxl or edit place?
Thanks
If you mean the update no, it’s nowhere near done yet, just wanted to share some progress (I might release a chunk of the code with the next demo but no promises). Once it’s out the old version will remain available as a separate .rbxl file, but until then you can just edit the place to access the currently available version.
Holy crap! That’s amazing!
(To be honest, I should’ve tried to add powerups to my game earlier.)
This is so cool, hope to see the project be updated with this content! I’d love to incorporate custom powerups into my game!
Greetings, today i’d like to announce the previous version of SNM is now deprectated in favor of Créme Engine, a complete overhaul of SNM’s codebase!
Specifically, what i’ll be talking about today is CE’s pre-release, as I wanted to get it in your hands as soon as the core functionality was working. Once CE is more feature complete i’ll be updating the main post to reflect it.
So let’s talk about what’s new, what has changed since last release, and what i’m hoping to add in the future.
● Clean, scalable, and strictly typed modular codebase.
● Modern EH2018 inspired moveset.
● Modular power-ups system.
● Reliable, easy-to-use collectibles system managed by a ProfileService database.
● Several built-in platformer mechanics, utilities and game components such as a Ragdoll system and a swimming system.
● Lots more to come.
I’m way behind on my school’s final project and have to go finish it rn, so i’ll just quote the imagery from the previous update atm, it’s basically the same thing (i’ll try to update it for the full release), but I recommend you check the place anyways as it has a handful of new features:
You can now find them on github (i’m still getting used to rojo so yeah, bear with me until I either get the hang of it or until roblox adds built-in vscode support):
And here’s the preview place if you wanna take a look before downloading the place file:
Sip N’ Munch’s main purpose was to offer the entirety of it’s source code in order for you to be able to take parts of it as you needed them, while also providing plenty of assets and cases of usage for said code in order to help you kickstart your projects.
That said, what happened in reality was that most people looked at the code, didn’t understand it, and as an end result, as far as i’m aware very few projects ever benefitted from the previous resource.
Overall the feeling I get is that it’s way harder both for me and for the end user to benefit from a full game, as it’s both easier for the user to get lost, and it’s easier for me to write messy code, as when you write game logic you tend to focus on getting out of the door, not so much on it being pretty.
Due to the previous, the old SNM place has been closed in favor of a newer demo, which you can check out here:
With this demo we took a look at the game we had made, we didn’t like what we had, and so, we decided to take a different direction, which we hope you like. The game now plays a lot more like a classic adventure game, while also adding modern elements to it in order to keep the experience fresh.
If you play you might notice bugs on the demo that are not present in CE, as well as features on it that CE lacks. That’s due to the demo using what was going to be the initial SNM rewrite, which we ended up scrapping as soon as the demo was released for what we consider a much cleaner codebase, so we’re hoping to update the game to use CE for the next demo (if we ever get around releasing another one).
That’s entirely down to personal preference. CE is aimed at bigger and more complex projects, it expects you to understand OOP and Strict Typing if you plan to modify it heavily, and I reckon the script organization is certainly unconventional (although I believe much cleaner), but it also tries to be easy enough to use for simple projects, while aiming to be extremely flexible for big ones (i’m no industry professional but I tried my best).
The template’s codebase I feel is simpler, messier perhaps, but that’s kinda what templates are for, they try to allow the biggest amount of people possible to use them with it’s tradeoff being it’s lack of scalability and core features such as datastores.
But eh, that’s just my personal take on it, i’m clearly biased as the multi million dollar company kinda made my resource redundant while I worked on it, but I think it’s overall a net positive that it exists so people have choices.
So to resume it, If you prefer the template, use the template, it’s more begineer frielndly I believe. If you don’t, don’t. You can probably take things from it CE still lacks, but I wouldn’t do that as the resources are organized very differently, i’d just ask for the feature in the comments instead.
I don’t have time right now to properly document the resource, i’ll try to come back to it later.
Most utilities are either documented or provide examples of usage, if you don’t understand something, you can just ask down below.
Right now CE offers a limited amount of features compared to the previous release, the main focus right now is achieving feature parity with both the new and the old demo, once that’s done I’ll update the main post and new features will begin to be made.
But again, this is just a wishlist, if no one finds the resource of use or if i’m just not able to achieve these, they just won’t happen, theres no guarantees these will become a thing.
CE is licensed under the “MIT NON-AI” license for reasons I don’t think I need to explain. This means you’re free to use, modify, and redistribute this project as you wish, but you are NOT allowed to use it to train AI.
Due to the previous nothing I make moving forward will be available uncopylocked, it’ll be only available in place files and perhaps on github once I have the hang of it.
As always, credit is appreciated and it helps tremendously, but remains completly optional.
Also, external resources are attached to their own licenses (most under MIT but not all of them), so you’ll need to comply with those individually.
Crème Engine relies on the following libraries:
As well as the following assets:
Massive thanks to the creators of these, especially RbxUtil, CE wouldn’t be anywhere as compact as it is without it.
If I forgot to credit a resource please let me know.
I’ll list any bugs that get found post release here until I setup a github repo for the project, these will be fixed in patches in order of priority as I get time to do so (right now the focus is on feature parity with previous demos, so low priority bugs will be left for later).
These are core features that represent an important issue if they break.
These are usually features that are rarely used or are planned to be reworked later on.
Thanks a bunch for the support the original resource got, it might not have been the craziest when compared to similar resources, but considering I have 0 presence in this platform i’m happy so many people found the resource of use.
If the resource helped you and wanna donate something there’s a small button on the new demo’s topbar, anything is appreciated and helps me continue making these things.
As always i’m open to feedback if you think the resource could be improved in any regard or want to contribute to it, and yeah, I hope you find CE of use and hope I get the chance to keep updating it in the future, have a nice day.
Currently cant open the place file.
Directs me to studio and does not open a place.
.rbxl works…
why does the deep water / stun / kill you?
Did you try again after studio opened? Studio ignores what place file you originally opened when it needs to update (you can also try opening it from studio itself using the open file option from the dropdown menu on the upper corner)
Water and deep water are the same thing, just different attributes, we use the one from the deep water example to prevent players from going out of the map, and the other one determines if you can swim underwater or if you are clamped to the top of it
Créme Engine v0.3.5.rbxl (736.5 KB)
Preview:
I’ll do the documentation later, but for now here’s 2 screenshots of the classes, TDLR: the handler initializes the MusicZones module, which returns states and such.
Said module uses the internal playlist class, which handles the actual playback.
Hey, I wasn’t exactly planning to drop a rushed patch today, but it turns out I forgot to reupload the animations to the group the test place was under, so yeah, I can’t imagine the game looked very good before half an hour ago 
.
Other than reuploading those (which u can also find ready to reupload inside each animation object) i’ve added a bunch of visual/sound effects to the moveset (some from the template, some new), did lots of cleanup to the code, and there’s a github for the project now (although the main files are outdated atm, just grab the release until v0.4.0 is out).
Also important change, the Code folder and the Volume SoundGroup have been moved to RepStorage as that’s what I think most people will prefer, so you’ll need to update your code to adjust to these changes (i’ll try to make this the last major structure reformat, but this is a pre-release and i’m still trying to figure out what’s best for the project, so please bear with me with that).
You can find the newest release here:
Next release i’m hoping to add replication for moveset effects and contextual controls, so look forward to that, and sorry about the inconveniences, that’s kinda why this is called pre-release.
Hey, due to the lack of usage my projects have gotten over the years i’m gonna try to move to a different platform, meaning CE won’t be getting updated anymore unless well, I fail to switch platforms.
I still consider CE better in it’s current state than the old SNM release, so I recommend you stick with it and port over any old mechanics you need yourself.
If you have any issues, i’ll still be around to help as long as my notifications keep working, and if there’s any major issues I might drop by to patch them, but aside from that expect no more updates from my part (project is under MIT so yeah, do as you please regarding forks).
Thanks again and sorry for those who were hoping for more updates but it is what it is.
