Minicraft 1.13
Gaspard Xenos
1.13, the first release of the Update Aquatic,[2] is a major update to Java Edition released on July 18, 2018. It focused mainly on ocean content and technical features.[3][4] Specifically, new blocks, such as blue ice, coral, conduits, kelp, sea pickles, stripped logs, wood, and turtle eggs were added, as well as new items such as buried treasure exploration maps, debug sticks, buckets of fish, hearts of the sea, phantom membranes, tridents, and much more. Also, water is more transparent than before and the color was changed to match specific biomes, while it was only dark blue before 1.13. In addition, dolphins, drowned, fish mobs, phantoms, and turtles were added, as well as new biomes, a new buffet world type (a stopgap replacement for the customized world type), and new generated structures. This update also added many commands and changed the format of existing commands, and added many new technical aspects, such as data packs and tags.
This update was originally intended to be released as two separate updates with 1.13, originally named Technically Updated, having the technical changes, and 1.14, originally to be called the Update Aquatic, having all the ocean features, however they were combined into one big update,[1] and as such snapshots from 17w43a to 18w06a mainly just added or modified commands.
The update was originally revealed during the MINECON Earth 2017 livestream on November 18, 2017.[5]Initially, 1.13 was scheduled to be released on May 30, 2018.[6] However, the release was pushed back to July 18, 2018, to fix critical bugs.
CraftBook has sat on the backburner since progress towards 1.13 started, mainly due to the smaller user base than WorldEdit and WorldGuard. In saying this, CraftBook is still my main priority out of all plugins I develop.
The main annoyance regarding this issue, is I fixed it back in 2014 with CraftBook 4. CraftBook 4 never requires entering items or blocks on signs; however, it depends on a feature that is not realistically possible with Spigot.
The current solution has been to allow legacy IDs for existing blocks and use 'minified' (without the minecraft namespace) string IDs for new blocks. In the few cases where they're still unable to fit on signs, CraftBook's Variables feature allows for it to still function. This recommendation is a temporary solution.
Another major issue that I've encountered is the instability and bugginess of the Spigot API. Upon first updating the plugin, over half of the features didn't work purely due to Spigot not correctly handling API calls and events. Even now, I'll find issues caused by a new bug in Spigot.
CraftBook uses almost all of the Spigot API, making it one of the most common plugins for encountering bugs within Spigot itself. Due to this, I quite frequently run into very niche issues, some that have existed for years.
I've gotten some of these fixed within Spigot and others within Paper. However, many are fundamental design flaws that Spigot can't reasonably fix. For these, I'd need to create new additions to the API, and Spigot is less likely to accept these.
Having to make such significant changes to the plugin meant this was also a perfect time to modernise the plugin. The build system has switched to Gradle, meaning builds are once again available on builds.enginehub.org. I removed the WorldEdit API's deprecated usages and made few other minor changes to ensure the plugin has a modern codebase.
Currently, CraftBook 3 is in a predominantly working state. I'm fixing issues as they crop up and improving the plugin as usual. There will have to be some changes made in the future to ensure that CraftBook continues being a performant, stable, and versatile plugin.
This goal is also where CraftBook 4 comes into it. Maintaining CraftBook for both Spigot and Sponge as two separate code bases was an awful idea. The intention here is to have CraftBook 5, compatible with Sponge and Spigot, and based on the CraftBook 4 source. It's unclear how I will replicate the Sponge-specific features on Spigot at this stage. My main idea is to require Paper and add the necessary functionality there.
Hi, I'm Maddy Miller, a Senior Software Engineer at Clipchamp at Microsoft. In my spare time I love writing articles, and I also develop the Minecraft mods WorldEdit, WorldGuard, and CraftBook. My opinions are my own and do not represent those of my employer in any capacity.
From a technical perspective: The update to 1.13 is a major one. A lot of stuff has changed under the hood.
Firstly, the server software itself has to be updated and tested for the new version. This is not done by us but by the developers. Things are looking pretty good there, they have already released an unstable test version so I expect a stable release in a few weeks. Secondly, a lot of old plugins will not work for the new version and will need updating. We have to wait until all the major plugins, we would like to use, have updated. This can take longer.
Literally in all the time i have mined on this version ive found maybe 10 or 12 diamonds. They made it too rare on 1.13 java version. tried different layers, etc. It literally fiels like griefing when you spend an hour and all you have is 6 or less diamonds to show, tried branch mining all kinds. Whatever they did to this version they messed it up.
Was this a completely brand-new 1.13.1 world or did you play on the 1.13.0 snapshots with it? There was a ore-generation bug in the snapshots that reduced the ore generation by a lot, it wasn't fixed until one of the last RC versions. You might be in an area affected by this bug, and will have to go further afield to generate new chunks that will have the normal oregen.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
This is bad news. Even if I didn't do any statistical analysis I did find that I'm mining a lot less diamonds out of my strip mine, and the extra diamonds got from underwater relics aren't covering the difference.
Yes, the problem here is that is all up to playstyle and playtime. I restarted the game to have the new ocean biomes nearer to the location of my base; if i had been forewarned the new mineral generation gave less diamonds, I would not have restarted the world because it would be less time consuming to move the base near a newly generated ocean chunk than remine all those diamonds.
That said, if the diamond generation is less than expected and still documented as a bug, I have no moral issues with using commands or creative to give all the players in my private world some extra diamonds.
I, too, have noticed this lack of diamonds. I started a new world in 1.13.1, began a branch mine, and after many hours of mining, came up with 15 diamonds. I recall playing the Legacy Console Edition on the PS3 and coming back with 30-50 diamonds without Fortune on my pickaxe.
I noticed the number of diamonds per ore to be really low in 1.13.1. While mining long tunnels in layers 10/11/12 in version 1.12.2 or 1.13 I could usually find 4/5 diamonds per ore, while now they are usually a single diamonds or 2 dimaonds per ore.
Apparently terrain generation was rewritten again, but the feature should be coming back in the future, though it will be very different. They say it will be easier to mess with, so it probably won't be nearly as powerful.
I've been playing on a 1.13.1 vanilla server for the last few weeks and I have never had so many diamonds in my inventory. I have almost six stacks using a fortune 3 pick and mining now and then between building sessions. Most of those diamonds were found while clearing out a large area down to Y=6 looking for slime chunks.
(And for the 99th time: Strip mining is stripping off the surface layer to remove minerals right near ground level. Wikipedia says "Surface mining, including strip mining, open-pit mining and mountaintop removal mining, is a broad category of mining in which soil and rock overlying the mineral deposit (the overburden) are removed, in contrast to underground mining, in which the overlying rock is left in place, and the mineral is removed through shafts or tunnels." _mining The word you're looking for is "Branch Mining", not "strip Mining.")
This can be the key. I feel like lava lakes being somewhat rarer, so it' possible that there are fewer caves (which would be filled with lava) and much more stone where diamonds can spawn from bedrock to layer 11, where I usually branch-mine. I could try to lower my y while mining and see if I get more diamonds 6-11.
1.13 had significantly decreased ores. 1.13.1 seems to be fine. IF you are playing in chunks generated in 1.13 the ores don't change so you might want to try mining in new chunks if applicable. If not, idk what to say, the generation seems fine to me in playing across multiple 1.13.1 worlds including ones that have been upgraded.
While the area they analyzed is not very large (about 128 chunks) the results vary to much to be explained by random chance; the results for 1.12.2 do not vary much, less than 10%, from what I found myself in 1000 chunks of a 1.8 snapshot, after I noticed changes in ore frequency (in this case, significant increases for all ores; diamond used to be around 3.1 ore per chunk while I found 3.72 and the above data shows 3.87 for 1.12.2 and only 2.27 for 1.13.1). The ratio of redstone relative to diamond (16.5:1) is also double what would be expected given that it is generated 8 times more often with the same vein size.
59fb9ae87f