I created library that handles some of new features introduced in Pretty Scary Update.(Source included) This features are: Colored wolf collars Custom fuse and explosion radius for creepers Custom skin of skull API for Beacon API for Zombie villager and baby API for Fireworks(changing type, trail, colors, fade colors, flickering) API for Enchanted books Adding recipes which returns items with NBT Tags Adding enchanted-like glow to items Download: Link JavaDocs: Link GitHub: Link Example of new recipes: Code: ItemStack item = new CraftItemStack(Material.DIAMOND_SWORD); ((CraftItemStack)item).getHandle().c(ChatColor.RESET + "" + ChatColor.AQUA + "Diamond Dagger"); ItemStack item1 = new CraftItemStack(Material.IRON_SWORD); ((CraftItemStack)item1).getHandle().c(ChatColor.RESET + "" + ChatColor.GRAY + "Iron Dagger"); ItemStack item2 = new CraftItemStack(Material.SKULL_ITEM, 1, (short) 3); item2 = setSkin(item2, "stirante"); CustomShapedRecipe.addRecipe("Diamond dagger", item, new Object[]{"X", "Y", 'X', Material.DIAMOND, 'Y', Material.STICK}); CustomShapedRecipe.addRecipe("Iron dagger", item1, new Object[]{"X", "Y", 'X', new ItemStack(Material.IRON_INGOT), 'Y', new ItemStack(Material.STICK)}); CustomShapelessRecipe.addRecipe("head", item2, new Object[]{Material.INK_SACK, new ItemStack(Material.SKULL_ITEM, 1, (short) 3)}); What you think about this?
Could I request some documentation? Would save me looking through the code Looks awesome though, I agree with the PR (whether it'll be accepted though is another matter)
Any reasoning as to why? Can I take a look at them? This one? https://github.com/Bukkit/Bukkit/pull/710 "Need a space before brace here" particularly frustrated me. When I process pull requests for my project, I don't complain about small issues - I'm grateful for the fact that somebody has taken the time to contribute to my project. I'm not worried if there are small errors, it helps with the development process and I can easily correct them. Formatting is not important. The compiler doesn't care about it, and if the lack of consistency annoys you, eclipse can easily format code to your specification in 2 clicks.
First PR was broken by GitHub and second one was closed with this message "This is not how the item data should work (from an API standpoint)". Both were working(First wasn't after uploading). You can check it here https://github.com/stirante/CraftBukkit/commit/b398f0195f8b19944ee59108a41a7dc4467288a2
I would commit again, but fieldmaster said " Thanks for suggesting api's though... I will add these myself, however." EDIT: Added Javadocs, but it's not completed yet
Im trying to use your library @stirante but it just isn't setting the text of the tooltip item for some reason...
Maybe it's bug caused by converting into Maven project and then disabling Maven. I'll see what's wrong. For now You can use class in http://forums.bukkit.org/threads/item-name-changing-class.104249/
Added API for Zombie villager, Zombie baby and Wither skeleton Added tester Code: commands: slowmo: description: 'Gives potion with custom effects' usage: 'Usage: /<command>' wolf: description: 'Spawns tamed wolf with green collar' usage: 'Usage: /<command>' creeper: description: 'Spawns creeper with 10 seconds fuse' usage: 'Usage: /<command>' zombie: description: 'Spawns zombie baby villager with diamond helmet' usage: 'Usage: /<command>' skeleton: description: 'Spawns wither skeleton' usage: 'Usage: /<command>' beacon: description: 'Builds beacon' usage: 'Usage: /<command>' name: description: 'Sets name of held item to given name' usage: 'Usage: /<command> name' armor: description: 'Sets players chestplate to green leather chestplate' usage: 'Usage: /<command>' skull: description: 'Gives players head' usage: 'Usage: /<command>' Download: Link
I believe we would use this in DiabloDrops if it didn't require this to be on the server as well. Thanks for the code you've done here, mate.
I don't mean to take this offtopic, but you're talking about your project. When dealing with code on such a massive scale, it's vital to sanity that people format and follow best practices that are defined by the team. You're not updating CB, so I would have to say you aren't quite qualified to base this off your experiences. You can't just submit stuff to Bukkit with "small errors" - because they don't end that way. Not even close to true. Formatting your code is one of the most important aspects of working as a community on a project like this. Again, I'd have to say you can't talk about "lack of consistency annoying you" until you see what the people who update CB go through.
Seems like a pretty easy thing for you to fix for it to get approved. The team really has a lot to handle without having to put in that time on your behalf.
I can understand that such practices will differ when you have a larger project (I do like everything neat, but then again I have the time to go through and sort the code out myself). It just frustrated me somewhat that new features are not easily accessible to those who don't know how to reference CB and setup NBT tags manually, etc. In no way am I trying to attack the performance of the development team, they do a fantastic job maintaining CraftBukkit & Bukkit with new updates and protocol changes.
I agree, I try to keep my formatting stuff in shape, eg. always try to use tabs, not spaces... also is that a new avatar? Nice
I just got an idea, if you want people to format their code, just give them a format profile from eclipse. I don't know if there is something like that for netbeans too... Than you can just ask them to format it with that format profile and the code will be formatted for you.
@stirante Fireworks already? I'm pretty sure they added those like... two days ago or something. Impressive!
In skull.java line 59, I get an error about the skull.a() not being applicable with no arguments. Is this supposed to be skull.a or is it just something that has to be ignored?
