Data API Implementation


#1

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).

Priority List:
- BlockState
- PotionEffectData
- HealthData, FoodData

I'll be updating the priority list as it goes along.


Some questions on the "Entity Spawn Tutorial"
#2

BanData & WhitelistData


#3

PotionEffectData


#4

Isn't AttachedData a generic class? Maybe this could be usefully to handle all the blocks temporary?


#5

HealthData and FoodData.


#6

ExperienceHolder, HorseData, JoinData, RespawnLocationData, MobSpawnerData


#7

All Item Data.


#8

VelocityData, DamagingData, IgniteableData so I can update the SimpleFireball plugin example smile

I would also love to contribute some of my time helping anywhere I can with implementation if possible. Looking forward to digging into the system more, just need a starting point.


#9

Packet data? blush


#10

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.


#12

I'm suggesting it should be implemented......


#13

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 stuck_out_tongue.


#14

I don't think you understand what Data API is. Please go re-read the issue I posed in the OP.

Did you read the javadocs?


#15

Whoops I am sorry worried.
(We really need links to docs, downloads, javadocs, ... on this goddamn forum. I keep forgetting that their are javadocs .... .)


#16

I would link them in every instance I can, but..... that takes a lot of extra time to get a link to the javadoc, properly format it for the forums.... eh, too much work.


#17

Need a browser plugin to auto generate javadoc links for a selected class name


#19

That's a great idea, @RobodudeMC any chance on some javascript magic for tampermonkey?


#20

I will look into that. That could be useful. This should really be a discourse plugin though.


#21

PR then wink


#23

@viveleroi BlockState has been implemented.
@Impervious PotionEffectData has been implemented.

Now to work on HealthData and FoodData.