Hot Summer Deals are Here!
Celebrate with up to 99% off on 17,000 resources
03
Days
19
Hours
50
Mins
28
Secs
View all deals

Plugin Emporium recruitment

Status
This thread has been locked.
Salvific

Salvific

Owner of Zonix Network
Banned
Feedback score
23
Posts
421
Reactions
341
Resources
0
Hey guys, we are thinking about extending our services, and that won't happen very soon with us 3 only!
Now to give every customer its deserved service, we need more hands.

This is an application for Plugin Emporium, where we offer 70% of the income we get from your plugins.
And you might be like, dude that's like very low! I made the plugin!
True, but you're also getting X% of all other plugin incomes. (we're still thinking about X (10% to 20%?))
So you will also be making money for the plugins you didn't write!

You'll also recieve bigger projects, meaning that custom plugin requests will be done by you.
Now this is only when we are working on other projects (which is like always).
(Custom plugins are never sold to the public without the customers permission!)


We do require a few things:
- The code you write is YOUR code.
- Your code is from top quality!
- Plugins need to be able to run on 200+ player servers without problem
- You do NOT redistribute it in any other way.
- Allowing us to keep your plugins on the site after you leave (and update if nessesary).
- Being active! We don't like leechers.
- Payments needs to be handled through us.
- Being able to communicate on a professional level to our customers.
- Code needs to be closed source (for now (sorry!))
- You're willing to add features without hesitation (if it's doable ofcourse)

(Server owners, this means that any plugin coded by us will always follow these rules)

Eventually we will also create some sort of API in our website to prevent piracing/redistribution.

If you feel like you want join, feel free to make an application.
If we contact you to do a certain project, and you don't have the time,
don't hesitate to say no. If you can't, you can't. No hard feelings :)

After you've proven yourself to us, we might be willing to give more perks,
which some of them, you would like very much ;)


By making an application you agree with the text in this post.
This post is subject to change without notice.


Application example:

Name?
Thomas "SubSide" van den Bulk

Age?
20

Where do you live? And which timezone?
The netherlands, CEST (UTC +2:00)

Which language(s) do you speak?
Dutch (native) and English

Do you have a microphone (not required!)?
Yes.

How much programming experience do you have?
I've started programming making websites for fun in HTML, CSS, PHP and javascript when I Was 12.
At the age of 16 I started learning Java which I am still using up to this day.

How much time do you have a day to work on plugins?
I have up to 8 hours a day to work on plugins.

Any servers you work/worked for?
Koonkraft (2013 - now)

Any projects that you're known for?
Not really. (This isn't required btw, but if you do, post github/bukkit/spigot links)

Any other things you like to add?
I am a very trustable person that loves to take on a challenge. Once I start a project I am very dedicated to it, and sometimes work 12 hours straight just to finish it. I am trying my best to always find the best solutions for things, but I also think about all the problems that could occur.
Most of the time I write perfect code, what I mean by that, that I never test till I think I am completely done with the code, and then I test. Most of the time, I only need to change 1 or 2 things, and the plugin works 100%.
I am very careful if it comes to performance. I am used to writing plugins for servers with 200+ players, and aiming to get my plugins to work in such environments.



Greetings, the Plugin Emporium team.
 
Last edited:
Click to expand...
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.
VG.Developments

VG.Developments

Java Developer
Premium
Feedback score
0
Posts
740
Reactions
398
Resources
0
Salvific said:
We do require a few things:
- Your code is from top quality!
Click to expand...
Why should our code be top quality, when yours is not?
Code: 
public enum Perms {
    ChatBypass("chatbypass"), CommandBypass("commandbypass"), SocialSpy("socialspy"), Admin("admin"), Sign("changesigns");
He doesn't seem to follow simple Java naming conventions. Instances of an enum should be capitalized.
Code: 
public static boolean debug = false;
public static String gChatPrefix = "!";
public static int signUpdateSpeed = 20;
public static String chatPrefix = "";
Ever heard of encapsulation?
Code: 
public static boolean debug = false;
Redundant. The default value of booleans is false.
Code: 
if (src instanceof Projectile) {
It is faster to compare enums then using an instanceof check
Code: 
int x = 0;
Redundant. An int's default value is 0
Code: 
public static String version;
Look into encapsulation.
Code: 
static final ArrayList<LobbySign> lSigns = new ArrayList<LobbySign>();
    static final HashMap<String, Game<?,?>> signToGame = new HashMap<String, Game<?,?>>();
Encapsulation and naming conventions. Constants should be capitalized.
Code: 
private RunningGame<?,?> rGame = null;
Redundant.
Code: 
public AbstractEvent() {}
Redundant.
Code: 
private static String title = "[WarpSpectate]";
I'm assuming this is a constant, and it is not final, nor does it follow naming conventions.
Why is it a requirement that we use quality code when your current team does not?
 
SubSide

SubSide

¯\_(ツ)_/¯
Premium
Feedback score
0
Posts
165
Reactions
68
Resources
0
VG.Developments said:
Why should our code be top quality, when yours is not?
Code: 
public enum Perms {
    ChatBypass("chatbypass"), CommandBypass("commandbypass"), SocialSpy("socialspy"), Admin("admin"), Sign("changesigns");
He doesn't seem to follow simple Java naming conventions. Instances of an enum should be capitalized.
Code: 
public static boolean debug = false;
public static String gChatPrefix = "!";
public static int signUpdateSpeed = 20;
public static String chatPrefix = "";
Ever heard of encapsulation?
Code: 
public static boolean debug = false;
Redundant. The default value of booleans is false.
Code: 
if (src instanceof Projectile) {
It is faster to compare enums then using an instanceof check
Code: 
int x = 0;
Redundant. An int's default value is 0
Code: 
public static String version;
Look into encapsulation.
Code: 
static final ArrayList<LobbySign> lSigns = new ArrayList<LobbySign>();
    static final HashMap<String, Game<?,?>> signToGame = new HashMap<String, Game<?,?>>();
Encapsulation and naming conventions. Constants should be capitalized.
Code: 
private RunningGame<?,?> rGame = null;
Redundant.
Code: 
public AbstractEvent() {}
Redundant.
Code: 
private static String title = "[WarpSpectate]";
I'm assuming this is a constant, and it is not final, nor does it follow naming conventions.
Why is it a requirement that we use quality code when your current team does not?
Click to expand...

Damn, someone is mad.

Why should I capitalize enums? just because everyone else does it?

Static fields in a config are easy, encapsulation is only really nessesary if you don't want anything else accessing it.
Yeah, it looks better, but encapsulating it really only adds just some extra characters to the code to access it.

adding = false to the end might be redundant, but it gives a way better representation of what the default value is.
same for int x = 0; and such, it gives a much better representation of the value it has at that point.


Thanks for pointing out the instanceof thing though, didn't know that.
 
VG.Developments

VG.Developments

Java Developer
Premium
Feedback score
0
Posts
740
Reactions
398
Resources
0
SubSide said:
Damn, someone is mad.

Why should I capitalize enums? just because everyone else does it?

Static fields in a config are easy, encapsulation is only really nessesary if you don't want anything else accessing it.
Yeah, it looks better, but encapsulating it really only adds just some extra characters to the code to access it.

adding = false to the end might be redundant, but it gives a way better representation of what the default value is.
same for int x = 0; and such, it gives a much better representation of the value it has at that point.


Thanks for pointing out the instanceof thing though, didn't know that.
Click to expand...
Sorry but i don't get mad over the internet. Your welcome for pointing out a few mistakes.
 
Last edited:
SubSide

SubSide

¯\_(ツ)_/¯
Premium
Feedback score
0
Posts
165
Reactions
68
Resources
0
Skionz said:
I have to agree with VG.Developments. Code that doesn't follow naming conventions is very hard to read and it is even more important since you are in a team.
Click to expand...
I have to agree with that for team projects it would be better, and I will propably change it in GameFramework, as it is an opensource project, which I and maybe other people will use.

VG.Developments I will keep this in mind for the next projects. I am always open to improve myself, as I thaught everything myself.
Sorry for the first post, "Damn, someone is mad." wasn't the best way to respond. Although I am not "happy" with your post, as you could also have private messaged me pointing it out, and not just putting it out in the open.

Like I said, I self-taught everything, this means that nobody ever teached me or critisized about what was best, and which rules to follow.


So even though you could've notified me about these things in a different way, I am still thankful for the input.
 
Last edited:
Status
This thread has been locked.
Top