Have you ever wanted to put a cat on a carpet when you were playing on a certain server on minecraft? Have you ever wanted to perhaps count how many cookies a player has eaten before they have become fat?
Well, I'm pretty suitable for this type of thing.
I've always been a tech nerd, my favorite thing is programming and i like to drink coffee because it keeps me awake and i'm very greatful for it, i also like bananas and will do anything for them-- Bla bla bla, let's get to the cool stuff.
So, I'm offering small plugins, cool, cool. What does that mean?
"Small" is subjective, but I'll narrow it down so you can understand.
A small plugin should contain only a few action-checks or, events, as they're called. Basically these "action-checks" are called when somebody does something in-game, an entity, to be more exact(maybe even an inanimate object, events are wonderful).
Went to bed in minecraft? Check - that's an event. Killed a player? Check, that's an event.
So, try to narrow down your plugin idea, if it has three-or-more of these events, sorry, bucko, you're outta luck.
What about commands? You know, the ones like /help and stuff? Yeah I can most definitely do that as well.
You can have like, 1-2 of those.
Why am I limiting my plugins so much?
First, time is a serious problem for me, and I'm sincerely not ready to take full-on-commissions, you know?
Second, and this one is a core problem:
I HAVE NO REPUTATION(noooooooooooooo)
Anyway, want a format to keep things clean and not just us communicating back and forth about plugin details:
Plugin name:
Server version(Like, the version your minecraft is when you join the server, this is excluding some multiple-version-plugins like ViaVersion - in which case, i'll probably ask about your jar's version. Or, the version that was compiled into the jar.)
Details:
And that's it!
have a good day!
Well, I'm pretty suitable for this type of thing.
I've always been a tech nerd, my favorite thing is programming and i like to drink coffee because it keeps me awake and i'm very greatful for it, i also like bananas and will do anything for them-- Bla bla bla, let's get to the cool stuff.
So, I'm offering small plugins, cool, cool. What does that mean?
"Small" is subjective, but I'll narrow it down so you can understand.
A small plugin should contain only a few action-checks or, events, as they're called. Basically these "action-checks" are called when somebody does something in-game, an entity, to be more exact(maybe even an inanimate object, events are wonderful).
Went to bed in minecraft? Check - that's an event. Killed a player? Check, that's an event.
So, try to narrow down your plugin idea, if it has three-or-more of these events, sorry, bucko, you're outta luck.
What about commands? You know, the ones like /help and stuff? Yeah I can most definitely do that as well.
You can have like, 1-2 of those.
Why am I limiting my plugins so much?
First, time is a serious problem for me, and I'm sincerely not ready to take full-on-commissions, you know?
Second, and this one is a core problem:
I HAVE NO REPUTATION(noooooooooooooo)
Anyway, want a format to keep things clean and not just us communicating back and forth about plugin details:
Plugin name:
Server version(Like, the version your minecraft is when you join the server, this is excluding some multiple-version-plugins like ViaVersion - in which case, i'll probably ask about your jar's version. Or, the version that was compiled into the jar.)
Details:
And that's it!
have a good day!
