Bukkit

What is the enhancement in mind? How should it look and feel?
provide support for custom items' damage values without adding them to the items.yml

when i want to give me an item for example an CeilingCornerSlope from Kaevators: /item 183:12
it doesn't work
chatresponse:
"12 is not a valid data type for Itemkaevcobblestonecorners"
shure is that a valid data typ, you just have to make it so for all unknown id's

and there are way too many items to add them all manualy to the items.yml

Adding them to the items.yml probably wouldn't do anything anyway. I //was// thinking of an API for informing General of valid data values for other blocks; it was intended more for things like Bookworm or Creaturebox, but would also allow registering custom block data values. (I'm actually a bit surprised that the custom blocks even work, by the way.)

This is not really high priority, though.

http://forums.bukkit.org/threads/mech-dev-itemcraft-1-6-6-support-for-client-mods-in-bukkit-1060-1000.15808/

with this wrapper some base classes from bukkit are overwritten, and thats how custom blocks work in smp :)

the only custom block typ that works with /item is the base block with 0 dmg other plugins that use /item or give work fine with the other dmg-values

couldn't you just exlude id 97-255 from the check for valid data? i would make it by my self but i coulnd't include all things ... some of the craft-irc classes are not excisting in the latest version

import com.ensifera.animosity.craftirc.BasePoint; import com.ensifera.animosity.craftirc.CommandEndPoint; import com.ensifera.animosity.craftirc.RelayedCommand;

edit: i have now everything rdy exept this craft-irc thing

I could exclude invalid block IDs from the check for valid data; however, if I did that, then when there's an update with new block IDs the check for valid data would not be applied to them. I'm not going to do that.

what about just removing the dmg-check? as it is now there is way to create a potion with /give or /item

Damage check not removed in 4.1, but it's theoretically customizable in items.yml.

Leaving this open because custom blocks are still not supported. Don't expect that before a hypothetical 5.0, though.