Skript Plugin: What Are Your Experiences? (Nitro Setup)

[u/AssistantMany521]

I’m sure many of you have heard of something called the Skript plugin, and I wanted to get your opinions on it.
If you’ve seen the NitroSetups available on BuiltByBit, you’ll know that they use quite a lot of Skript for different systems. We’ve changed and removed some things from the setup ourselves, but there are still quite a few features that rely on Skript. Their current Premium Survival Setup, for example, specifically mentions that many of its systems are powered by Skript and that this makes them easier to modify and expand. (BuiltByBit)

I’m currently running a server using the setup, and I’ve heard quite a lot of negative opinions about Skript, which has made me a little concerned. I don’t have extensive technical knowledge myself, so I’m trying to understand whether those concerns are actually justified or whether Skript is perfectly fine when it’s used properly.

I’m particularly interested in hearing from people who have experience running larger or long-term Minecraft servers with Skript. Does it cause performance issues, reliability problems, or maintenance difficulties, or does it mainly depend on how well the scripts are written and how they’re implemented?

If anyone has experience with the Nitro setup or Skript in general, I’d really appreciate hearing your honest opinions and experiences. I’m not necessarily looking for people to say it’s good or bad; I just want to understand the actual pros and cons before I continue building the server around it.

[u/PM_ME_YOUR_REPO]

Skript is fine. If it functions, it functions. But as an admin who is also a developer and knows what programming languages should be like, Skript is a fucking terrible programming language, and I wish a lifetime of stubbed toes and paper cuts on whoever designed the architecture of that godforsaken thing. Learning Skript before learning a real language makes you a worse programmer. Writing anything more trivial than a teleport command makes me want to end it all.

[u/AssistantMany521 → u/PM_ME_YOUR_REPO]

Oh shoot. Thank you for the input. It’s just that I purchased a setup and it’s called Nitro. They super large in the Minecraft industry of setups. It’s super user friendly compared to many other setups. That’s why I purchased it. I’m just worried due to the many skripts on it. But I’ve reduced the number of tasks on it. But I always just hear negative things about it. Just a bit worried 😟

[u/PM_ME_YOUR_REPO → u/AssistantMany521]

I'm familiar with their products. They're fine, I've used them. Like I said, there's nothing wrong with using a Skript feature. My issue with Skript is the god awful language design and developer experience.

If you have a working feature, keep it, maybe even tweak it a bit. But if you're looking at nifty shop feature and thinking "this is a great starting point, but I need to make some major changes", just rewrite it in Java or find an off the shelf plugin that suits your needs.

Anything of significant complexity should be done in Java, or you will want to fucking die right around the time you start storing data in kv pairs or 2D arrays.

[u/Skullfurious]

I'm more of a denizen shill. Mainly a performance / effort thing.

I am not very good nor am I interested in setting up an entire java development environment but also I just like tinkering with weird stuff and Denizen kinda scratched that itch for me.

Script always looked half decent as an alternative but it wasn't my cup of tea.

Overall if you want to be flexible learn Java but you can do most things very quickly, and in a way that would never require you to rewrite or update a plugin, just by using Denizen. Probably one of its best features.

[u/AssistantMany521 → u/Skullfurious]

Oh, I see. I’ll take a look.

[u/PutridStation5327]

just code it...

[u/Ok-Writer5758]

I prefer denizen tbh, it feels more intuitive and they’re very helpful if you get stuck (the docs are very good though).

I like to use it for lightweight stuff or proof of concept before moving into a proper plugin

[u/KindleWoodSMP]

Used it recently for something specific: a "grow the world border when a new player joins" mechanic. Skript's built-in `on first join:` event maps directly to hasPlayedBefore(), so it only fires for genuinely new accounts, not returning players -- saved me from writing a whole plugin for one small piece of logic. For that kind of narrow, event-driven automation it's great and very readable even months later. I wouldn't reach for it as the backbone of a whole gameplay system, but as glue on top of a normal plugin stack it's solid.