search

FountainMC / FountainVanilla

FountainAPI implementation on NMS
MIT License
8 stars 2 forks source link

Update to 1.10 #9

Closed phase closed 8 years ago

phase commented 8 years ago

This is the 1.10 update!

Changes so far

Techcable commented 8 years ago

I like dropping the dependency on MCP.

wgaylord commented 8 years ago

I don't like the idea of spigot mappings but. As there license is unclear. (Does not have one in there repo...)

phase commented 8 years ago

@chibill $20 says it's better than MCP's, as their's is "you can use this, but you can't look, touch, smell, or use this."

wgaylord commented 8 years ago

Yeah but with out packages it make it over 100% harder to deal with.

phase commented 8 years ago

@chibill That's the whole point of adding our own mappings! They move it into new packages and update methods and such.

wgaylord commented 8 years ago

And make it hard on devs that want to use methods that are built into MC.

Techcable commented 8 years ago

Actually you know as @0x277F pointed out the spigot mappings aren't really licensed for us. And its not really a problem waiting for MCP to update since most people won't use a new version until forge updates.

phase commented 8 years ago

Supporting the latest version is a lot better than waiting for MCP to update. How many servers are running Spigot 1.10? A lot more than are running Forge 1.9.4. I'm sure we can get permission to use Spigot's mappings.

And make it hard on devs that want to use methods that are built into MC.

That's the whole point of these mappings. They give obfuscated methods new names.

phase commented 8 years ago

We're sticking to MCP.