Hello again. Today we are releasing Glowstone 2017.8.0, which is the last release to support Minecraft 1.12. Since 1.12.1 was released, we will now bump our version to 2017.8.1 which will be released at the end of August (unless Mojang pushes another protocol update).

Since we released 2017.7.0 less than a week ago, not much has changed. Here is the changelog since that release:

New Features

• Added Ender Crystals to the end-pillar generation in The End
• Added support for 17w31a clients

Fixes

• Properly handle generators with null spawns (#536)

We are now working on updating Glowstone to 1.12.1, which will be officially supported in the next monthly release (2017.8.1).

This post was mirrored from the site.

Hello again! The time has come for us to publish this month’s release for Glowstone, 2017.7.0. We have plenty of new features this time around, including boats and paintings, as well as many bug fixes since 2017.6.1.

There has been a total of 40 commits by 8 contributors in July, with 4,491 additions and 730 deletions in 122 files.

New Features

• Implemented some more vanilla commands (FlorrentClarret)
  • /banlist
  • /defaultgamemode
  • /me
  • /playsound
  • /seed
  • /setidletimeout
  • /setworldspawn
  • /spawnpoint
  • /toggledownfall
  • /xp
• Began work on caves (surface caves specifically)
• Added support for multiple passengers (Postremus)
• Better support for off-hand item usage
• Added optional GPGPU surface noise generation (mastercoms)
  • Allows for surface nosie generation to be executed by a GPU instead of the CPU
  • See pull-request for more details
• Implemented boats, ender crystals and paintings (Postremus)

Bug Fixes

• Fixed furnaces not showing as ‘burning’ when smelting items (#474)
• Fixed incorrect argument-length check for /tell
• Fixed players spawning above the map when respawning (#460)
• Fixed player’s internal last damage cause not being updated (#456)
• Check for cancelled events in some missing cases (#516)
• Fixed explosions wrongly destroying certain blocks (#515)
• Fixed armor/shield slots not being excluded when sending container contents, causing client errors (#481)
• Fixed /tellraw command parsing
• Fixed errors when loading horses from NBT, including spawn eggs
• Fixed horse babies not being the same color as their parent
• Fixed player entity-interaction being wrongly duplicated in some cases
• Fixed exception when getting tameable entity’s owner internally
• Fixed 1.12 parrots-on-shoulders functionality
• Fixed shift-clicking for crafting slots (#525)
• Fixed crafting result slot not being updated in certain cases (#526)

Other Updates

• JavaDocs are now automatically deployed every build
  • You can view the Glowstone JavaDocs here, and Glowkit’s here.
• We have continued updating the new Beta site
  • The Beta site is a completely open-source initiative.
  • More information can be found in the official announcement.
• Important: Due to a possible intrusion of our forums database, we recommend you reset your account password on the forums
  • Multiple issues with our Redis database and Proxmox virtualization system have lead to a complete external exposure of its contents (including email addresses and bcrypt-hashed passwords).
  • All data between June 18 and June 25 has been lost due to a technical failure.
  • Please read our report on the intrusion. Feel free to contact us if you have any questions or concerns about this.

Coming Soon

I have personally been working on implementing pathfinding for Entity AI. After several months of on-and-off work on this issue, I have found an efficient solution to implement it, and I am aiming to have it all functional for the next release (2017.8).

We are continuously updating our Beta site with new features, and we are looking forward to your feedback. We are planning to have a complete ‘Download Center’ for Glowstone on there in the near future!

This post was mirrored from the site.

Hello again! We released Glowstone 2017.6.0 today, which is the final release to support Minecraft 1.11.2. This release is pretty light compared to the previous one, 2017.5, which we published only a week ago.

Changes

• Updated default start script
• Optimizations to world loading and saving

Fixes

• Fixed containers dropping empty items when broken
• Fixed bug where default spawn point would be underground
• Fixed bug with lake generation

1.12

Now for the bigger news, we have updated Glowstone and Glowkit to Minecraft 1.12. Starting from today, our scheduled release for the end of this month is 2017.6.1. While this update has been in the works for about 2 weeks, we will continue to implement more features from 1.12 this month. You may notice that some vanilla commands are now missing from Glowstone; they were removed from Bukkit by the Spigot team and we will have to implement them ourselves in the coming days.

Thank you for your continuous support as always. We look forward to releasing 2017.6.1 in 3 weeks from now.

Hello everyone! So we’ve heard your critism and concerns about no longer planning to support Sponge on our server platform. Well, turn that frown upside down, because we are now dumping Bukkit plugins in favor of Sponge plugins!

That’s right, starting from today, Glowstone will permanently consist of patches to the SpongeVanilla server software. Why reinvent the wheel when we can base our work on a much more capable server and API? You can view the source for GlowSpone here!

Bukkit? Gross! Use GlowSpone now and never go back to Spigot or any of its nasty derivatives.

Thank you for your continuous support,
The GlowSpone team.

Edit: this was our April Fools post for 2017, we are not planning to support Sponge or to drop Bukkit anytime soon. Read more here.

@kamcio96 Sponge does have a vanilla server implementation, but this hasn’t been their focus (mostly API development and SpongeForge afaik).

Also note that it is now possible to download the latest successful 1.11 build on the website, under the “Future release” section. Please backup your world and submit an issues to the pull request. Thanks!

5 months ago, we updated Glowstone’s implementation to 1.10, and Glowkit was moved to a patch-based system.

So, Mojang recently released the first version for Minecraft 1.11, which means MCP, Bukkit, Spigot, and Paper should update in the coming days (hopefully). Just like last time, I think we should consider updating how we push new future updates (note that I am not talking about bug fixes, but features in general) -> we will probably change our version scheme to a Minecraft version-independent update cycle: having our own betas, releases and versions with support for a specific Minecraft version.

In other words, I think we should start off with what we have, and progressively update with new features starting from major features not currently implemented (AI, Rails, some generation stuff, etc.) and then going on with more recent additions (1.9-1.10-1.11). Obviously, the first thing I am going to do is to update the protocol to 1.11 - without necessarily adding all the new features included in the Exploration Update right away. Hopefully, we will be able to push important features quicker than we normally do.

What do you think?

Assuming you mean Forge Mods, it’s not really planned to be added as a feature. Glowstone is intended to be based on Bukkit and support plugins for the Bukkit API, and Forge’s API relies heavily on Minecraft vanilla internals.

@mastercoms Yes I agree its a pretty important feature. I have to build up some tweaks to my Pathfinder library because it breaks in under-ground areas, so I’m going to do that first and adjust the pathfinding AI. I’ll go with that!

Hello fellow Glowstoners (that sounded nerdy),

I’ve recently been working on different aspects and features for Glowstone in the past few months, whether it be the tile tick format implementation, updating to 1.9.4 then 1.10, fixing some inconsistencies, the new website, etc.

However, I also have a bunch of stuff I have tried implementing and never finished/wrapped up. I have working prototypes most of these… here’s a list of a few I can think of:

• Entity AI prototype (branch here with demo)
• 1.11 snapshots (branch here and Glowkit here)
• Packet API (PR here)
• Projectiles (thanks to LukeDeLoop/DeprecatedLuke)
• Rails (connecting them together)

Since I’m not the best at prioritizing my time, I’d like to know, what would you like me to work on first? It can be anything, on that list or not. I’d be more than happy to hear your opinion. Albeit, there are some that could take longer than others…

Thanksidup for reading my post!
Momo