So, as it has come to light that many developers are trying to write plugins for SpongeAPI, a lot of the Data API has yet to actually be implemented. As the issue list can be viewed for the checklist, of course, there are some priorities for implementation.
So now I ask, what data manipulators do YOU want to be implemented first? (this is more along the lines of prioritizing the implementation for what developers need first than just writing from the top of the list).
You’re funny. There is no such thing as PacketData in SpongeAPI.
I have to confer with @gratimax on actually implementing a ban system because, well, that’s stepping into a different API section altogether.
I can implement that really quickly, likely today after I get BlockState implemented correctly.
Not sure what you mean. AttachedData is specifically for signifying that a block is attached to something, the immediate impementation would apply to things like BlockTypes.TRIPWIRE and BlockTypes.TRIPWIRE_HOOK.
I’ll get this in shortly after PotionData.
Priority no. 4.
Priority No. 5, and I’ll be updating the SimpleFireball as I’m doing it as I’ll be using it to test the implementation.
Could you specify what Item data you’d like implemented? I can’t just bundle all item data as that’s a fair bit of classes to implement.
I thought that AttachedData was something like an NBT editor class without known parameters. And if we wanted to read/write NBT from forge blocks we could use the generic class. But I am guessing I am wrong .