I’ve amended the rules to be a bit more clear about which plugins are allowed to enter.
[quote] * Must be a plugin that is one of the following…
a.) A new plugin.
b.) A plugin that is relatively new (no more than a month old).
c.) A plugin that is not that popular/has a small user-base.
d.) A plugin that is a port from another project (Forge, Bukkit, Canary, etc).[/quote]
Most of those that will review the plugins wish not to deal with looking at an unfamiliar language. While we have nothing against the languages themselves we just prefer to keep it simple and straight-forward.
However syntax takes time to adjust to depending on how different it is. In order to ensure that we are able to efficiently and accurately rate these plugins we added this rule to the contest. This rule was part of the first contest as well.
We appreciate all feedback given and will use it for future contests, however at the moment this rule still stands for this contest.
To be honest, I’m kinda confused at why everyone is getting so annoyed at not being able to use these languages… It’s a competition, the rules are set and that’s that. I have to say, looking back on code that I have written in other JVM languages, none of them are very easy to read for other people.
Take Kotlin for example, you don’t need to declare what a variables type is if it’s inferable… Or what about operator overloads? Do you expect the judges to really want to have to take the time to figure out all the information and crazy usages that people come up with?
I think the rules stated fairly clearly what was allowed. My only reason for asking the last question was because I was wondering if side loading scripts for the plugin was allowed.
I want to port my plugin, RottenFood, but aside, I wrote the Sponge port of BuycraftX. Does that count? What if the code is good but since inventories are not yet implemented it doesn’t really work fully?