I do sell plugins already, but most times I donate it to organisations who really needs money, so its like 50% non-profit.
Minecraft PC IP: play.cubecraft.net
And thanks for your feedback :)
Gradle takes more time, but it is still beautiful when u get down to the i need more than a simple lifecycle here
That way, no matter what the player types, it will still work...
Other than dark eclipse themes having the cruddy colored normal menus XD. Looks better than regurgitated trash that people post as 'tuts' on bukkit and spigot. Those are just blatant copy pastes. At least here you spent some time to reword explanations and the process without requiring the user to have some initial knowledge about their IDE and terminology.
But those pics are ugly. Eclipse needs better theme support. Or at least a better full body dark theme like intellij's darcula.
But those pics are ugly. Eclipse needs better theme support. Or at least a better full body dark theme like intellij's darcula.
I agree with the theme, but still it looks better then default, hehe. Would love to see a "IntelliJ theme"
And thanks for your feedback :)
I wouldn't mind a tutorial on maven, I know there are other advanced developers in this community of ours!
Maven is easy to learn, very copy and paste xml snippets, simply because its so verbose remember all the plugins and their configuration options is a pain
Gradle takes more time, but it is still beautiful when u get down to the i need more than a simple lifecycle here
No edit button XD
@TrinityDEV yeah no problem there. Eclipse would be fine if the rest of its ui would change to the set theme. Not just the major areas
@TrinityDEV yeah no problem there. Eclipse would be fine if the rest of its ui would change to the set theme. Not just the major areas
I would disagree that gradle takes more time - it's incredibly simple and the configurations are a lot shorter. It also has the advantage of using a DSL, which you can use for scripting etc as well if you want.
With regards to the tutorial itself, I'd say even for basic plugin development these days, looking into Gradle or Maven is a must. With IDEs, I'd go for IntelliJ over Eclipse, the autocomplete is better, live templates enhance productivity so much, and maven/git support is built in (as opposed to using a plugin).
I'd say it would also be better to know OOP concepts before moving into plugin development, and doing things like creating classes for each CommandExecutor rather than having them all in the main class can end up in far cleaner code in larger projects.
I'd say it would also be better to know OOP concepts before moving into plugin development, and doing things like creating classes for each CommandExecutor rather than having them all in the main class can end up in far cleaner code in larger projects.
Not exactly, most people do simple things, but the complicated stuff is for da pros >:D
I suggest... "cmd.getname().equalsignorecase("test"))"
That way, no matter what the player types, it will still work...
Oh whoops, yeh i usally use that too, i dont even know why i did it like that here, upsie :$
Great job with your tutorial, definitely good for starters. For your next tutorial could you do like how to make a basic API because i'm pretty weak in that area.
Very helpful thank you. I will try to get better but this is a great starter guide. Very well done.
Similar threads
Team online
-
FesaQuality Assurance -
SpringWarzSenior Moderator -
Thunder⚡ Moderator ⚡
