Closed phase closed 9 years ago
Sponge is actually a (Forge) mod so both things are wrong
I don't want to keep it at just "mod", as then it might be confusing on what it's a mod for.
This part of the README should probably be revised, but currently this PR retains the grammatical ambiguity (in that "which serves..." may appear to refer to Sponge rather than Pore.
Additionally, it should be kept in mind that Pore isn't limited to the official implementation (I.e. the Forge mod).
@caseif Too much ambiguity...
to be honest anyone looking at pore source, should know what Sponge is xD
@jamierocks Anyone looking at LapisBlue should know what Sponge is.
Change it to Pore is a plugin for the up-and-coming SpongeAPI which acts as a bridge to provide compatibility for Bukkit plugins on servers implementing SpongeAPI.
@jamierocks Eh, that sounds a little redundant. How about:
Pore is a plugin for the up-and-coming SpongeAPI built to provide compatibility for Bukkit plugins on the platform.
Maybe:
Pore is a complete reimplementation of the Bukkit API on top of Sponge API.
It aims to allow you to run any Bukkit plugins on any Sponge server, be it
Quartz, Glowstone, the official Forge mod, or others. **Pore is currently
incomplete, and is not known to run any Bukkit plugins.** Contributions
are welcomed and encouraged.`
This replaces both mini-paragraphs with one paragraph. We may also want to mention that Pore will probably never run any plugins that require NMS.
@AesenV That's a bit long-winded IMO. I'd vouch for keeping it short and sweet.
@caseif I'm going to have like 30 commits in this once it's over...
@phase I would use this to keep it more concise:
Pore is a plugin for the up-and-coming SpongeAPI built to provide compatibility
for Bukkit plugins on the platform. Please note that this project is still under
heavy development and **is not yet considered functional**. Currently, no Bukkit
plugins are verified to be supported.
@caseif Why didn't you merge this pull request?
@phase It was merged, just rebased into one commit before being merged, that's why GitHub is not displaying this correctly
@Minecrell Gotcha!
Small typo.