Welcome to Créme Suite

The smooth blend of clean, consistent, and scalable open-source magic.

Our Signature Blend

A vanilla latte isn’t just about the vanilla, it’s about the harmony between smooth milk, rich espresso, and just the right amount of sweetness. Miss one element, and the whole drink falls apart.

Créme Suite follows the same philosophy: every component is carefully designed to work together, creating a development experience that’s smooth, reliable, and effortlessly scalable. No missing pieces, no unpleasant surprises—just a well-crafted toolkit you can depend on.

Take A Sip, It’s On The House

What’s the Barista’s Secret?

Smooth Consistency in Every Drop

No more mismatched tools. Every piece of the suite is designed to blend together nicely, ensuring a frictionless development experience.

Crystal-Clear Documentation

Skip the guesswork. With detailed documentation, clean code, and practical examples, you’ll always have the perfect reference at your fingertips.

Extensible by Design

Wanna add your own flavors? Créme Suite’s architecture is built for growth, ensuring that components remain flexible and easy to modify to fit your needs.

Strictly Typed for Maximum Reliability

Every part of Créme Suite is strictly typed, eliminating hidden errors before they happen and making your workflow more predictable and robust.

The Brewing Principles

Consistency & Adaptability

Créme Suite prioritizes clean design, logical structure, and predictable behavior; so you can focus on creating, not refactoring.

Built to Last

Créme Suite’s components are highly abstracted; making them easy to follow, maintain, and extend as your project’s needs grow.

100% Free of Charge

Resources should be accessible by everyone, not locked behind a paywall. That’s why everything in Créme Suite is completely free, and will forever be.

Made by people, for people

Créme Suite is licensed under a permissive NON-AI MIT License, because your work deserves to be protected, not harvested by companies.

Ask the Barista

Is attribution needed?

Although appreciated, attribution is optional.

Do I need advanced knowledge to use this?

Not at all, the introductory section should explain everything related to this library in complete detail, meaning any intermediate scripter should be able to use it with relative ease.

Didn’t understand something? Feel free to reach out, i’m always happy to help.

Can I contribute?

Absolutely! All contributions are appreciated.

The only requirement is to follow the cookbook, which you can find in the Getting Started section.

Why is the project hosted on Codeberg?

Microsoft keeps repeatedly proving they can’t be trusted with our data, and so, in order to avoid having Copilot be willingly trained on it, I decided to move my projects away from GitHub.

I understand Codeberg may not be everyone’s cup of tea, and I know it won’t prevent Microsoft from scrapping the data anyways, but at the very least i’m not willingly giving it to them, nor supporting their ecosystem.

As for why my code isn’t hosted on the devforums either, much of the same can be said about Roblox.

Are forks/derivatives allowed?

As stated in the license, redistribution of derivative work is perfectly fine and allowed as long as it abides by the license terms. You can find a resume for these on the Getting Started section.

Just make sure to check the licenses for third-party dependancies if you plan to redistribute your work, as i’m not responsible for those.

How does this compare to X/Y?

Créme Suite focuses on being a clear and consistent package, while other resources may focus on different things, such as providing a larger set of features.

It’s down to you to compare the options available and choose the one that best fits your use case.

Where’s CE/SNM?

Créme Engine didn’t work out. Providing it as a bundle made it harder to maintain, it didn’t get much usage as people figured it was only made for platformers, and eventually I lost the motivation to keep maintaining it. As for SNM, much of the same happened to it.

Créme Suite’s goal is to offer much of the same as standalone components, which is easier to maintain for me, and hopefully easier for everyone to use as well.

Both the old CE and SNM place files can be found on the old github’s releases section and/or in it’s devforum post, but be aware they are no longer maintained.

I’m having trouble with a component / My question wasn’t answered

Check out the forums listed in the website’s socials, you’ll find plenty of solutions to problems people has previously had.