Welcome to skUnity!

This is an April Fools joke! https://forums.skunity.com/threads/new-rule-no-use-of-sk-skript-in-addon-names.2883/#post-7408

Hi everyone,

I unfortunately have to announce this new rule which takes immediate effect. Please read on for what is happening:

I was recently contacted by Njol via email and we discussed how skUnity Forums had at first replaced the DBO forums and have now become the only Skript forums due to DBO not having the forums section anymore. For skUnity Forums to become the official forums, Njol has asked for some input into how the forums operate. I have agreed to this with him, so long as skUnity Forums are branded as official and he has some activity on them.

However, during this conversation with Njol, he brought up an issue. He is contacted multiple times a day with people reporting bugs for addons. He believes the general confusion lies with the fact that addons use the wording "sk" or "Skript", either at the start or end of their name and people then believe they're either official addons of Skript or they are Skript.

This rule is that addon developers can no longer brand their addons with "sk" or "Skript" if they're posting them on skUnity. Addons currently posted will be changed over the coming days. I know this rule probably doesn't help out the community, but it's something Njol has asked for.

Name changes:
OpenAudoMcSkript => OpenAudoMc
skript-json => json
MythicMobs Skript Addon => MythicMobs Addon (direct references to Skript also not allowed)
SkellettProxy = ellettProxy
Skellett => ellet
skQuery (inc. forks) => Query
SharpSk => Sharp
TwitterSk => Twitter
Vixio, this addon already complies with the new rule
WolvSk => Wolv
Reqn, this addon already complies with the new rule
TuSKe, this addon already complies with the new rule
QuarSk => Quar
BentenCore, this addon already complies with the new rule
SkStuff => Stuff
Umbaska, this addon already complies with the new rule
skUtilities => Utilities
WildSkript => Wild...

It's time to announce the Winners of the 3rd Skript Challenge! Finally...​

@BaeFell has given me the honour of deciding the winners (probably because he forgot again...). As such, it is my honour to announce the following 3 winners.

The selection process was quite simple, as most of the submissions a) didn't work properly, or achieve the needed result and b) were mostly based off of @LimeGlass's submission.

In no particular order, the winners are.

@LimeGlass - First Submission, Lowest amount of lines, Small and Simple and easily repeatable.
@Mr_Simba - Much like LimeGlass, but with extra detail in the included failsafe.
@Blueyescat - With added detail in the form of his arguments, added cancellation ability and more.

Congratulations to all the winners, and thank you to everyone else who submitted!​

Just some helpful advice for future events;
1. Try to be original, there are always more than one way of achieving a goal. If you make the most longest and craziest response, then so be it. It's awesome in its own right.
2. While we're not against building off of others', at least add something new to it (ie; a stop feature)
3. Make sure it actually does what is required... There's one submission here that didn't even get close to the wanted result.

Thats all! Thanks a lot!

(Winners: Your badges will be given in due time, make sure to annoy @BaeFell if you haven't gotten it by next week)

(This was posted here, since @BaeFell forgot to give me permission to post in the proper place...)

Hi everyone,

Welcome to another Skript Challenge!

So here's the third one! If you have any suggestions for #4 or general improvements, let me know

This Skript Challenge is kinda mathematical, but mostly around being smart with how your script works. The task is to create a way for me to fill an area. The area fill must be suitable for any size or shape area. The areas will be completely closed in (so no holes in walls etc). Example:

Filled:
​

There are no holes in the walls, floor or ceiling (apart from an open door but they're classed as a block). But also note the odd shape. This is just an example, areas can be very complex.

The rules are as follows (note: rules may change between challenge):
- Your code must be in [code]<code>[/code] tags so that I can easily read it.
- You can use addons, but, you're not allowed to use a feature from an addon which does this (don't think any do) and the addon must of been released publicly prior to the creation of this thread.
- You cannot use a feature like "fill area from location of player" or whatever.
- You can use another user's code, but please don't edit your messages. I can see all message history and you'll not be counted at all.
Remember: this one is about quality, not just length. So trying to cut variable names from someone elses code will lose points!
- WebAPI's or using an external source (outside of Skript), to get your result in not allowed. All submissions must actually do the conversions themselves.
- You can use an addon to place blocks, but not to fill the area.
- You must list all addons used. I will be testing on Spigot 1.11.2.

I might add a rule after a submission has been made, it's up to me whether or not that submission is valid. I can deny any submission for any reason.

Challenge details (specifics about this challenge):
-...

Hi everyone,

It feels like I've already posted this thread before... but we've done it again! skUnity Forums has hit 1,000 members! The 1000th was at 2:40pm (GMT) today! @SchnapsKy. There are now 97 new users from them at the time of this thread because xenForo takes a while to actually update statistics.

What is crazy is that it has only taken us less than a month to get this level of users back to the forums. I understand completely that it was a difficult process of downtime, a (failed) move, downtime and a wipe. But eventually everything has turned out ok! xenForo is treating us great and the community is expanding rapidly.

A huge thank you to everyone who has been a part of the community, here's to another 1,000!

Another huge thank you from,
BaeFell and the rest of the skUnity Forums Team...
@Wrong, @Sashie, @Gatt, @Mr_Simba, @Tuke_Nuke, @xXAndrew28Xx, @Blitz and @TonyMaster21

Hi everyone,

After remembering yesterday, then forgetting and remembering now, here are the winners of the second skUnity Skript Challenge! There weren't many entries this time (to be honest, it was slightly more complex), but there were some amazing ones anyway! I've also got the medal system up and running, and have created a medal for the people who win a Skript Challenge! The 3 winners from #1 were award their medals earlier.

Anyway, without further ado, here are the winners:

In first place is @SwiKZiiK - a French Skripter who created the shortest way of doing it, while not using any loops, addons or splitting!

Code (Skript):

1.     set {_num} to "Put your number here."
2.     length of {_num} <= 2:
3.         return {_num}
4.     else if length of {_num} = 3:
5.         return "%first character of {_num}% hundred and %last 2 characters of {_num}%"
6.     else if length of {_num} <= 6:
7.         return "%first (length of {_num} - 3) characters of {_num}% thousand, %subtext of {_num} from (length of {_num} - 2) and (length of {_num} - 2)% hundred and %last 2 characters of {_num}%"
8.     else if length of {_num} <= 9:
9.         return "%first (length of {_num} - 6) characters of {_num}% million, %subtext of {_num} from (length of {_num} - 5) and (length of {_num} - 3)% thousand, %subtext of {_num} from (length of {_num} - 2) and (length of {_num} - 2)% hundred and %last 2 characters of {_num}%"
10.  

(while I'm not looking for the shortest, it amazed me and many others on how this one was so simple for the challenge).

In join-second place is @Rezz - a beautiful and well crafted solution to the challenge. Massively extensive and covers a wide range of features.

Code (Skript):

1. options:
2.     TABLE: number-to-name
3.     ERROR: [Error]
4.     ENABLE_LARGE_NUMBER_NAMES: true
5.  
6. # Define all masks in a string with pattern:name pairs.
7.  
8. function defineMasksIn(values: text):
9.  
10.     set {_pairs::*} to {_values} split at " "
11.  
12.     loop {_pairs::*}:...