Moonlets - Unopinionated utility modules

Resources Community Resources
, ,
#1

GithubBanner

Unopinionated utility modules for Roblox


Modules :jigsaw:

Module Install Description Learn
Wrapper Wally Bind code to Instances Source
Stator Wally Create minimal state machines Source
Instantiate Wally Construct instances w/ less code Source
Leaderboard Wally Set leaderboard stats w/ one line Source
HumanoidDescriber Wally Easily modify HumanoidDescriptions Source
CoreThemer Wally Easily theme Roblox’s core UI Source
Bootloader Wally Load / unload OOP services Source

If you code in Roblox Studio, you can use Studio Wally to install Wally packages.

Values :sparkling_heart:

  • Infer types :face_with_monocle: - Types should be inferred where possible, giving you full typing on data you construct.
  • Don’t assume :dove: - You should not be locked into specific formats or methodologies. Not even OOP.
  • Minimize :relieved: - Modules should not be bloated, overly-complex, or force their dependencies onto you.




A request <3

If you use this free software as part of your game or project, please tell me about it! I love seeing what people make. You can reply in this thread, or reach out directly. (@avafe on Discord)


Watermark

8 Likes
#2

The significant modules have now been published on Wally! Additionally, there is a new Stator module to help you construct minimal state machines.

1 Like
#3

You should not be locked into specific formats or methodologies.

Can you upload these modules to the Roblox library? I don’t use wally, and I don’t use studio wally either.

#4

The GitHub repository does not currently have ample automation for releasing .rbxm files. I’m looking into changing this in the future, but as of now, Wally will be the only way to install these modules.

And while I do believe in flexibility overall, that project value pertains to the modules themselves. Wally really is great, once you get started with it.

#5

The “star on github” button points to OnyxUI

#6

I find a bit odd to claim

Modules should not […] force their depenencies on you

but also require users to use wally… Not everyone uses wally and so every new release should just have an rbxm file uploaded for each module. Automation isn’t required!

#7

the automation seems to exist for standalone rbxms, they just don’t exist because it isn’t configured right

#8

I was in the process of writing an actions workflow to release to both rbxm and Wally. Pesde too actually, before I discovered its architectural incompatibility with Wally. I unfortunately ran into issues when it came to rerunning steps for each of the modules. PRs welcome if anyone’s feeling generous.

#9

Doing it manually adds friction to my development process. Many of the Moonlets modules are used across my own codebases. I give away the (free) code I feel comfortable with, and in exchange, I get to make my own impact and get a little bit of clout.

#10

Obviously you’re not required to do it, and I’m not upset that you don’t because I can generate my own rbxm file if I download wally and rojo and all that – but it would take maybe 2 minutes to put an rbxm in the directory for each module, assuming you do it only when you update that specific module

1 Like
#11

Stator has been updated to support table specifiers when observing state.

#12

Stator now supports type passthrough, so you get full autocomplete