To many Platforms
Now days there is sponge Husk Rainbow Arrow PotionMC(A project I am working on that is already on 1.8 and works (measing some stuff) that no one probably ever heard about)
It is going to be allot harder now to find Plugins to work for evreything 
Give that time after the first few months we will know what project will be the main attraction and the one we have to build plugins for.
(I am putting my chips on sponge)
Arrow was discontinued due to lack of support.
Proof:
However there is also Granite, donāt forget them!
Ya ya ya So one quited and you added another one
the only reason I am still making my server Platform is just to learn and Beacuse peapole from my comuntty wanted to see
how it will look
I have nothing against sponge hell i used half of the plugins made by the devs of sponge on my servers.Now with that being said I must apologize for some of my words in here.Its just some of the people who support sponge do nothing but hate on other platforms.Like all the pros and cons in this topic.They have no clue how far sponge will go or rainbow for that fact.So now i list some of the facts for rainbow.
1)DIW the creator of Rainbow works tirelessly putting out new builds and updating
2)We have an ever growing community with new plug in devs working hard to make plugins for rainbow
3)You have dedicated forum staff always on top of things making the site easier to navigate
some notable plugins already made for rainbow
Pl3xCommands v0.1 BETA11 (essentials like)
RainbowLogBlock
Rainbowcord (helps hook into bungee) and yes I run a bungee server with Rainbow hooked
Pl3xPerms v0.2 (first perm plugin that replaces the built in perms)
ProtectionCore Beta 0.6
AntiCheat beta
Lottery
Kits!
Rainbow Chest Lock 1.4
RainbowVotifier (CoolVās Edition)
Server Shop!
RainbowEdit (WorldEdit)
Rainbow Zones
and more ā¦
So good luck to sponge
but i can guarantee Rainbow wil not be going no where but up.
Have a Nice Day
1 Like
Sounds credible.
i heart rainbow, plus it is super easy to use
Pros and cons are just that, both good and bad points. Yes some people are assuming Sponge will go farther than Rainbow and thatās conjure because no one truly knows at this point but others were pointing out very solid opinions on the state of api (at the time of the posting) comparing it to Spongeās then current and/or planned api.
And making points about this projectās plugin devās following vs yourās is also a credible point to make as you already know by making that list.
Yes some people were hating on it and that was already said it wasnāt the point of the topic creator. He wanted comparisons and it got a bunch of pros and cons (mostly) which is what he was going for. To be honest, hearing everyoneās opinions on the matter, both good and bad, makes me believe in the project more than a list of plugins because I can see the problems and risks of using it and weigh them against the things itās gotten right.
Plus, in my opinion, there simply isnāt enough of a active plugin following for either one yet to say which one will lead the pack and in my opinion, that matters most of all. As much as I love Sponge and believe in it, if the tide for plugin dev turns to another platform then Iāll go over along with them. Rainbow or one of the many others.
Of course that wont be for a long while to give them enough time to build plugin library of course
You say you love sponge but cant play on it.Its like saying i love my blind date before meeting her.thats what i dont understand the commitment of users to sponge based on whos making it.I like to see and feel things before comparing. you can try rainbow so there is a way to make that comparison but you cant play on sponge so how can any pros and cons be accurate.also my point of listing plugins made for rainbow is just my way of pointing out we are growingā¦Im not hating on sponge just the people dissing rainbow based on what they read here.Until sponge is up and working its all here say.the planned api and all the hype. i can say I plan to live forever but we know thats a lie.I withhold judgement on sponge until i can play on it.
1 Like
Well, I guess rather than loving Sponge I shouldāve said I love the idea and the plans of sponge. I also love the idea of all these developers who I known and trust and used their plugins/mods/anything else for years getting together to make it so it brings me great hope for the project. And you can already compare Sponge to to Rainbow in the following ways:
-
What each project is trying to accomplish and their approaches to it. Sponge runs off forge and Rainbow is a custom jar for example.
-
Rainbowās current Plugin following vs Spongeās plugin following. Many Bukkit plugin devs are already planning on porting their old plugins over to Sponge and I doubt theyāll change their minds in a matter of a month when the api gets to the state where porting can begin. Compared to Rainbow, it seems like most of the plugins are new and rainbow specific. (Rainbow Chest, Rainbowcord, etc) Yes they havenāt been ported yet but itās a valid point to make.
-
Again, devs can compare rainbows current api to Spongeās api and give their pros and cons. Yes Spongeās isnt ready yet but enough info about it is out there to give devās a good idea how itāll work and handle.
-
Legality. Yes itās already been debated and we know your stand on it. But still some users may feel better developing for Sponge since it doesnāt supply any minecraft assets along with it unlike Rainbow and, especially after the buyout, they may feel like it has a better chance of surviving. Plus, microsoft already said they wont disrupt mods and forge is one of the most popular modding apis. For microsoft to dmca forge would be one of the most foolish things they could do.
-
Trust. Most people here including myself have used many of the devās projects before whether they were plugins or an entire modding api. With that amount of use comes an obvious trust and many believe that theyāll deliver on at least a decent project. And with Rainbow, not many people knows these ānew devsā or even the core development team. So some may not want to go over based on that alone. While some others may want to give you a chance. Or maybe even someone could vouch for you having used one of the devās pluginās in the past. Thereās more to the projects than just the code. Thereās also the reputation of the devs and if people will be willing to take a chance to follow them.
There you go. Just five ways you can compare they two without having to play them. And even if you had to play them, it doesnāt matter what matters is how decent the api is and how many devs will use it.Vanilla Rainbow should play the same as Vanilla Sponge so to compare them at their base playability would be foolosh.
Yes you are growing but so is Sponge. Just not in ways you may see yet. I will withhold judgement on which one is truly better than the other until several months pass after Sponge comes out and the plugins begin being ported but comparing the two and deciding which one youāll go for is perfectly reasonable because rainbow, like sponge, is still early in itās life. It may be out now and have plugins for it but, as you said, itās being updated every day and hasnāt reached itās fullest potential yet.
Edit: added another point
Edit 2: corrected some typos
Yes like you said āStupid litte userā yes you are as you said, Sponge IS NOT ready for any kind of download as it being build from the ground up, okay its new so thats why it take time to get even ready for any kind of download for us. but when you look at Rainbow from what i know its the bukkit that have been edited with the normal Minecraftserver.jar so it works like bukkit when its not, so by that its ready for downlods and testing. so yes
you can say that sponge is very very slow but here the thing. You want a rush modding api with many bugs and crash or a ānotā rushed Sponge build that works with no crash and a few bugs as there will allways be that litte bug
- Hobitenā¦
Iāve tried out Rainbow for 1.8, and it seemed to work adequately in the small server tests I ran. At least it gave us some useful tools like warps for 1.8, although the Janitor tends to spam the log a bit. I have no serious complaints about itās functionality, just the limited range of plugins available (which is quite understandable).
That said, Iāll still hold out for an API that can handle a range of plugins similar to the 40-odd that my 1.7.10 server is using at present. Itās all about the Baggage, and my server has a lot of it. Iād hate to lose the power and complexity of the detailed configs I have evolved over the years. Iām hoping that most of the plugins will make it to 1.8 in Sponge (and the signs are good), and that the configs wonāt need to be significantly rewritten. So in the long term, I want Sponge.
If I were starting a server from scratch, the appeal of a server wrapper thatās actually ready NOW would probably be irresistible, and Rainbow would be my choice.
So there you go, 2-bob each way. I wish success to both teams.
1 Like
While it might seem like a trivial point, I simply couldnāt bring myself to use an API which puts underscores in its class names. Java has coding conventions which 99.9% of software uses - what makes Rainbow special?
2 Likes
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
O pleaseā¦ Sponge isnāt out yet so hold your horse and wait for spongeās release
But Rainbow isā¦ so why not compare them and see if Sponge can learn anything from Rainbow?
People around here are just rude and hostile and trollish toward anything that isnāt Sponge. The most reasonable people around are the actual devs of Sponge, who have repeatedly said competition is good.
1 Like
@Inscrutable simply stated the pros and cons of each project, very reasonable ones at that. You would do well to actually read the post before leaping into criticism. 
1 Like
Thatās not very civil of you. Thanks for responding to a post I made weeks ago back when you started spreading lies about Husk.
2 Likes
Good evening,
Iām the developer for Rainbow. It was interesting reading through this (long) discussion.
First, I like the stance the Sponge team is taking in being open to discussion.
Iād like to point out thereās an obvious path of cooperation here. A developer who
is working on Sponge should be able to write a plugin for Rainbow that then
loads and delegates events to a Sponge plugin. I.e. Rainbow platform (as server .jar)
with Sponge API surfaced on top.
I donāt know Sponge API current state, but presumably they would have the basics of
āload pluginā, āstartupā and āshutdownā ironād out reasonably well if not fully.
Iād be willing to help, even expose custom events if needed in Rainbow.
My line of thinking for a Sponge enthusiast with development skills is:
- Create a Rainbow plugin that catches onStartup/onShutdown
- I made a video tutorial how this is done (real easy)
http://www.project-rainbow.org/site/media/?sa=item;in=13
- Load something implementing Sponge API and call itās equivalents.
Assuming that goes well, you could proceed to delegate other events.
We have something similar being done to delegate to Bukkit plugins which is coming
along nicely (reportedly WorldEdit works 90%+ with the latest PluginBukkitBridge)
I think this would be a bonus to both server owners and plugin developers.
I.e. For server owners, itās something they could start using now. And also feel like
they arenāt tied to Rainbow. For plugin developers waiting on Sponge API, itās something
they can start experimenting with now and also feel like their not tied to Rainbow.
Anyways, it seems to me like thereās some opportunity here we could tap into.
So Iāll toss the idea out there. 
6 Likes
@DoingItWell Can I create an event in my plugin that āinheritsā from your blockbreakevent thing and raise it so other plugins can catch it and afterwards I verify if they cancelled it?