I built a plugin called Sparkle for Godot 4. It lets you bundle camera shakes, screen flashes, particle bursts, hit pauses, sounds and more into a single node. Instead of managing all of that in code you stack them in the inspector and fire everything with one line. You can tweak, preview, copy and paste entire sequences without touching code.
I built it for my own commercial MMO because nothing like it existed in Godot. After using it in a real production context I wanted to release it so other developers do not have to build and maintain their own juice system from scratch.
I like the look of the Inspector. Very colorful. Also cool that you have a light version people can try. I’d recommend creating a how to video though. Without it, I doubt you’re going to get much traction.
Thank you so much! This is a plugin I originally built for my own game which I actively use in production. I always loved Feel in Unity but the Godot tool ecosystem was missing something similar so I decided to build it.
Beyond just showcasing the plugin I am also planning videos on game polishing in general. How to use juice effectively, when to use it, and how to make your game feel professional without overcomplicating things.
The Lite version covers around 85% of the most commonly needed feedbacks so even with the free version you can ship a production quality game.
Feel free to reach out anytime. If you want to try the full version and share feedback I would love to hear your thoughts.
Sorry for the late response. I am not much of a forum person.
I am currently working on a 3D action-combat multiplayer game. I recently picked up Godot because I am working at the engine level and using a custom C++ server. Unreal offers more tools and has a better job market, but it is too heavy for the size of the project I am working on. I needed an open-source, lightweight game engine with an expandable and clean editor.
I am planning to share more information about my current project later, once it is out of the prototype stage and the concept art is in place.
I have seen some concerns about plugins containing malware or using LLMs.
I cleaned and documented the plugin using an LLM to make sure it works well with LLMs. Some new developers are using LLMs, so the README files are aligned with LLM usage to optimize token usage and help the LLM provide better feedback and tweaks.
Furthermore, both the lite and paid versions of the plugin contain the full source code, since it is written in GDScript.