[dlgn]

In 1.8, there are a number of new stone types: granite, diorite, and andesite, as well as their polished counterparts. While they are craftable, this requires Nether Quartz, which is already in short supply; furthermore, in vanilla, 1.8-generated Minecraft, this isn't the main way they are obtained: instead, they are merely mined from underground similarly to stone. It is for this reason, as well as the precedent set by the Nether Quartz substitution that I suggest the following (if and when Bukkit should update to 1.8).

Do the same thing that we did with Nether Quartz. Use the world seed to find where granite, diorite, and andesite would have been if the map had been generated in 1.8. Then, substitute those blocks into those places. This would allow players to obtain these blocks in a reasonably legit way without having to use up the server's relatively small supply of Nether Quartz (which was, of course, obtained in the same way).

OPTIONAL: Only substitute granite/diorite/andesite into a spot if there is stone there (IIRC they generate in places where 1.7 generated stone). If there is air or another material there, don't do so. This would prevent the occasional case of random stone-type blocks being scattered through the air or builds on public land, as well as being more legit.

HIGHLY OPTIONAL: Add an option for private realm owners to enable and disable block substitution within each realm. As this would probably be difficult from a coding standpoint, it isn't at all necessary, but it would be convenient.

Vote and discuss this idea below!

~dlgn

[Valendr0s]

As far as I know a 1.7 seed will generate the same as in 1.8, just with the new ores. What *I* would do if it were my server...

If block is not owned. If block is stone. If block is naturally "supposed" to be one of the new block types in 1.8, replace block with 1.8 block.

Also, If '/plot regen' is set to true by the plot owner, do the same process as above.

[monkeychunks]

Voted yes however this could cause some major issues. After playing survival 1.8 I have found that this stone is everywhere. There is no shortage of it and is in fact more common than gravel patches underground. The problem with this is that it is very likely to spawn inside a build or replace a chest. Unless well coded. I would conclude the wilderness would have enough stored in it if it was reset, however it would be nice to have it in the normal part of the world.

[dlgn]

Voted yes however this could cause some major issues. After playing survival 1.8 I have found that this stone is everywhere. There is no shortage of it and is in fact more common than gravel patches underground. The problem with this is that it is very likely to spawn inside a build or replace a chest. Unless well coded. I would conclude the wilderness would have enough stored in it if it was reset, however it would be nice to have it in the normal part of the world.

No need to worry; that would be solved by the part marked "OPTIONAL".

OPTIONAL: Only substitute granite/diorite/andesite into a spot if there is stone there (IIRC they generate in places where 1.7 generated stone). If there is air or another material there, don't do so. This would prevent the occasional case of random stone-type blocks being scattered through the air or builds on public land, as well as being more legit.

Furthermore,

1. Should this suggestion be accepted, Intelli may opt to only add in stone in public land, and
2. Even should he enable it in private realms, it seems likely that he would allow the realm owner to disable it, similarly to how private realm-wiping was optional in the most recent map wipe.

~dlgn

[123DontMessWitMe]

(if and when Bukkit should update to 1.8)

Bukkit and all it's children (Spigot, Cauldron, MCPC+) See here Have all been been removed due to copywrite infringement. So the server will not be updating to 1.8 unless Intelli wants to update spigot himself, which I find quite unlikely. There are other server software in the works behind the scenes which may prove worthy in the future but we will just have to wait.

[Valendr0s]

(if and when Bukkit should update to 1.8)

Bukkit and all it's children (Spigot, Cauldron, MCPC+) See here Have all been been removed due to copywrite infringement. So the server will not be updating to 1.8 unless Intelli wants to update spigot himself, which I find quite unlikely. There are other server software in the works behind the scenes which may prove worthy in the future but we will just have to wait.

Technically the license broke and now all the mod writers have been released to their own copyright again. Nothing is stopping them from continuing to keep their individual mods updated.

[dlgn]

(if and when Bukkit should update to 1.8)

Bukkit and all it's children (Spigot, Cauldron, MCPC+) See here Have all been been removed due to copywrite infringement. So the server will not be updating to 1.8 unless Intelli wants to update spigot himself, which I find quite unlikely. There are other server software in the works behind the scenes which may prove worthy in the future but we will just have to wait.

That's why I said "if". Bukkit may or may not update, depending on whether Microsoft can sort out Bukkit's legal issues.

[Sandsnake]

The Bukkit issue was entirely revolving around decompiled MC code being included under an open source license. Bukkit wasn't authorized to do that since MC isn't open source. I imagine Mojang already had a resolution for this but had to DMCA themselves to check the "we defended our copyrights" box. The question, of course, is what is Mojang going to be doing during the transition. Will they continue to update Bukkit like they said they would? or will they just let everything languish until MS provides new direction.

[dlgn]

The Bukkit issue was entirely revolving around decompiled MC code being included under an open source license. Bukkit wasn't authorized to do that since MC isn't open source. I imagine Mojang already had a resolution for this but had to DMCA themselves to check the "we defended our copyrights" box. The question, of course, is what is Mojang going to be doing during the transition. Will they continue to update Bukkit like they said they would? or will they just let everything languish until MS provides new direction.

Ah, but that wouldn't solve anything. It would prevent anyone else from using their code, but it wouldn't allow them to take that code.

To use an example someone posted on Reddit, if you draw a picture of Mickey Mouse, Disney can tell you to take it down and stop using it. But that doesn't mean that they can use it. The picture is yours, for all the good it does you.

Of course, it's possible that Mojang could threaten to do this unless people permit their code to be used. But that's pretty unlikely, in my opinion. After all, what do those people have to lose? It isn't like they can do anything with their code, anyway, other than what Wolverene is already refusing to do (allow Mojang to use it as part of Bukkit).

~dlgn

[Intelli]

Bukkit wasn't authorized to do that since MC isn't open source. I imagine Mojang already had a resolution for this but had to DMCA themselves to check the "we defended our copyrights" box.

Incorrect.

It has been unfairly suggested that Mojang is in some way behind his request that CraftBukkit is taken down. We want to make it clear that Mojang is not responsible and has no liability whatsoever in regard to these claims.

http://forums.bukkit.org/threads/mojang ... ct.309715/

Mojang was going to update Craftbukkit to 1.8: https://storify.com/lukegb/the-tale-of- ... ecraft-1-8

That likely won't be happening now due to the legal claims from Wesley Wolfe.