Great plan. Looking forward to try out Sponge soon.
Great! I can’t wait to see the first Sponge build released 
1 Like
Reusablity then becomes easy: you can add the “grass eating” component to a creeper object and now creepers can eat grass.
I’ve always wanted to see a creeper that could eat grass…
8 Likes
Thanks for the update - you are all awesome!
I’m glad that Sponge isn’t using an ECS, mostly because it seemed a little silly to use a design pattern that is completely different from the one being manipulated… Although I was excited about the convenience of custom components. 
So has there been any discussion on a solution for attaching our objects to Blocks, Entities, etc? Built-in persistence like what deltahat (who wrote Bukkit’s Metadata API) suggests would be awesome. 
Minecraft may be switching to a component structure in the future sometime anyway:
(from this [post][1])
[1]:Component System and Minecraft
I’d rather wait longer for a complete API than have an incomplete API where we have to include the API implementation for us to do anything ground breaking (like in Bukkit). The end goal I believe should be that there will never be a need to include an implementation as a dependency in your plugin code.
1 Like
Personally, I want to say thank you so much for the Update. It’s really hard to be able to nothing when I want nothing more than to help. This means a lot to a lot of people and hearing anything makes the loss a little easier, but I understand the road ahead is long and uncertain. Keep working team, we’re pulling for you.
1 Like
I already love this project.
a) it embraces the “community”
b) it communicates
c) it responds
d) it moves forward
Good job guys, I will keep my fingers crossed.
4 Likes
Glad to see that even though an eye of caution is open wide it is not slowing down progress. I personally do not thing that Microsoft’s purchase will cause this community to fail as the success of Minecraft is always created to the greater community that has opened up so many possibilities beyond the original scope. Yes Microsoft has made a few blunders in the past but when you put it into perspective look at the some of the wonderful things that they have accomplished: anyone remember when they first announced the XBOX and everyone told them they were fools getting into something they could never succeed at? Big companies are easy to hate, massive companies with huge market shares and a vast product offering are even easier to hate. This deal is (by Mojang’s own admission) been in the works for a good while now, with this level of continued interest there is little way they could not be aware of what the community of developers, modders, server owners/managers, etc have done to make Minecraft the global phenomenon that it is today. Of course none of us can say what they have for plans with this purchase, but they are not going to want to lose such an important piece of the success.
Thank you to all that have made a contribution in the past and to everyone doing their own part to continue this adventure. This is what makes a community so strong and powerful. I have to admit that I look forward each day I arrive home to reviewing the discussions that have taken place and following the work/progress that has been made. Keep up the amazing work and community commitment!
Should’ve used Scala, it supports mixins using Traits
Anyway, good work dev team!
Oh and why is the sprint called “Inspired Wallaroo”?
While I agree and think it would have solved some of the API design problems related to running on Java 6, Java is what people are used to (probably including sk89q and co).
I can’t wait to sign up for API development, this project is looking good.
1 Like
According to Owexz, the new versioning system for Sponge builds is an adjective and an Australian Marsupial.
On that note, allow me to blow my own trumpet: Bardic Extrapolation (Rime of the Ancient Sponge) - #7 by Inscrutable
Why not combine ECS with inheritence. Keep everyone happy. Make certain attributes a component and keep others in their own classes.
1 Like
That sounds great.
I’m not sure there is a design pattern like that but I’m sure if it was planned out it would work. It would also allow for scalability in both ways in the future
Thanks for the update, the project looks promising. Get the API released ASAP so us plugin devs can have a happy programming session 
if you guys are going to make playerquitevent and playerkickevent, make sure to make them separated because they end up being triggered both even if the player was kicked, and that is bad for plugins like combatlog, thanks
Maybe a PlayerLeftEvent with a reason code of “Kicked”, “Logged Off”, “Disconnected”, etc.
3 Likes