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.

So, we need to sort of loot table system for Glowstone. Currently, Mojang uses a JSON-based, “pool” system file format. For example, this is the loot table for Cows in Vanilla (insert asset copyrighted by Mojang blah blah).

Now, I suggested this file format for the Sheep loot. It has a YAML and a JSON version:

YAML version

# Entity Loot Table: SHEEP

items: # Item drops
  -
    default:
      item: mutton
      count:
        min: 1
        max: 2
    conditions:
      - condition: ENTITY_ONFIRE # The mob is on fire
        item: cooked_mutton
  -
    default:
      item: wool
      count: 1
      data: $.getColor().getData() # byte Sheep.getColor().getData()
    conditions:
      - condition: $.isSheared() # boolean Sheep.isSheared()
        count: 0

experience: # Experience drops
  count:
    min: 1
    max: 3

JSON version

{
  "items": [
    {
      "default": {
        "count": {
          "max": 2, 
          "min": 1
        }, 
        "item": "mutton"
      }, 
      "conditions": [
        {
          "item": "cooked_mutton", 
          "condition": "ENTITY_ONFIRE"
        }
      ]
    }, 
    {
      "default": {
        "count": 1, 
        "item": "wool", 
        "data": "$.getColor().getData()"
      }, 
      "conditions": [
        {
          "count": 0, 
          "condition": "$.isSheared()"
        }
      ]
    }
  ], 
  "experience": {
    "count": {
      "max": 3, 
      "min": 1
    }
  }
}

Note some characteristics of this format:

• It uses Java reflection injection for some values ($.getColor().getData() and $.isSheared()). This is a format I created along with my utility, OneLineReflection. It allows getting values from the entity, the “context”, which is represented as $. For instance, the condition
• Certain conditions and values are mapped. For example, ENTITY_ONFIRE is the equivalent of $.getFireTicks() > 0
• For randomization, you can put children max and min (latter is not required). If the result is expected to be of fixed value, simply put it directly.

Basically, I am asking for feedback on this format (the idea itself, the JSON/YAML format choice, etc.). What do you think?

• /summon command (I’ll work on this since the Mojangson PR got merged)
• Mob features (drops, sounds, etc)

(I’ll add more when I think about them)

@kamcio96 said in [2016Q2] Feature Voting Thread:

• Entity ai

Are you sure AI can be completed by June 30? Me thinks this should take much longer, no?

So, Mojang recently released the first pre-release for Minecraft 1.10, which means that the full-release should not be too far away.

Right now, a lot of major features from 1.8 to 1.9, and even some from 1.7, are still not implemented in Glowstone++. Thus, we need
to decide how we want to proceed with the update to 1.10, since some server owners still want to stick to 1.9 and prefer having a
complete version rather than a feature-incomplete 1.10 server.

What I propose is to focus on 1.9 development on the main branch, and develop a 1.10 version in a separate branch. As such, we can
focus on the development of features on the master branch, and when we feel we have reached a somewhat complete feature-set for
earlier versions, we can merge the 1.10 branch into master and release G++ for 1.10. For example, I currently have a
branch for 1.10 that I update as snapshots come out.

What do you think?

Today, we are putting in place Glowstone’s new Cheating and Illegal Behavior Policy. This is an effort to engage ourselves in our position against illegal piracy and behavior in the context of our project.

Although Glowstone will always keep the online-mode: false option functional in the server configuration for testing and development reasons, we will not put extended effort into keeping our software compatible with pirated software (such as cracked clients). Our mission, on that front, is to stay at the same level of compatibility as Mojang’s server software.

In addition, this new policy extends to the usage of illegally distributed or obtained products used with Glowstone (including plugins and libraries). In other words, we will not assist users if their support request implies the usage of cracked premium plugins or similar products. This also applies to the usage of cheating/hack clients (in the context of a support request).

The policy document can be found in our GitHub repository.

Thank you for your comprehension. As always, feel free to communicate to us any concerns about this new policy.

The Glowstone Project.

This post was mirrored from the site.

As fireworks are let off for the end of 2017, we are releasing this year’s final version: 2018.0.0. In the last month, we’ve been working hard on polishing Glowstone as much as we could, and this has resulted in one of our most productive months in terms of commits, merges, bugs resolved and code written.

We’ll start with a quick changelog of what has been done since the last release, 2017.11, then follow with a recap of the year!

Glowstone 2018.0.0

This month, we’ve pushed 138 commits consisting of 17,993 additions and 11,491 deletions in 938 files.
There are a lot more changes than what I can list here, so you check check out the git diff if you want more details.

• Implemented /clone command (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/590”>#590</a>)
• Implemented Ender Pearls (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/602”>#602</a>)
• Added support for Java 9 (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/649”>#649</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/652”>#652</a>)
  • Note that while Glowstone can run on Java 9, it can only be built on Java 8.
• Fixed a number of bugs with player interactions (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/644”>#644</a>)
• Fixed issues when shift-clicking in the crafting inventory
• Fixed an exception when joining a Glowstone server run from an IDE
• Fixed gravity not updating the location of items (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/591”>#591</a>)
• Fixed a number of bugs with fall damage
• Fixed the minimum food level to regenerate health from 19 to 18
• Fixed, rewrote and optimized chunk indices (Chunk.Key)
• Improved region file I/O, fixing some issues (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/199”>#199</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/510”>#510</a>)
  • More details can be found in commits 98aeb19, 34ce26b, 3179cef
• Optimized chunk streaming to players
• Improved hanging entities (paintings, item frames) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/597”>#597</a>)
• Fixed a number of bugs with Sign editor (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/596”>#596</a>)
• Fixed an exception when pinging the server behind a proxy (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/599”>#599</a>)
• Updated Netty from 4.1.0.CR7 to 4.1.17.Final
• Fixed inventory slots in HumanEntity spawn packet
• Rewrote ItemTable to use Material instead of item IDs
• Fixed inconsistencies with PlayerInteractEvent (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/595”>#595</a>)
• Fixed open inventory not being closed when player is teleported (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/594”>#594</a>)
• Partially implemented MapView/map rendering API (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/572”>#572</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/605”>#605</a>)
• Added slf4j back-end dependency (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/612”>#612</a>)
• Abstracted WorldStorageProvider to allow plugins to change how world data is saved and loaded
• Added log4j configuration
• Cleaned up chunk locks (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/623”>#623</a>)
• Implemented Fire Resistance potion
• Refactored EntityManager and BossBar management (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/636”>#636</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/641”>#641</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/642”>#642</a>)
• Fixed a concurrency exception when players switch worlds (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/628”>#628</a>)
• Implemented ItemSpawnEvent and ItemDespawnEvent (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/643”>#643</a>)
• Updated checkstyle
• Removed metrics
• Removed GlowClient and related dependencies
• A lot of code and documentation cleanup
• Updated Kotlin runtime to 1.2.0
• Updated CI to use CircleCI 2.0 on all branches, builds are now much faster

Whew, that was a lot of polishing. In addition of all these changes, we are also pleased to welcome 2 new developers as part of the team: Pr0methean and keanganxt.

Note that we now use the dev branch for ongoing work, while the master branch will be deleted. We have decided to try a new release format for 2018. We have updated our download section to reflect these changes.

We created a long-term support branch (LTS), 2018.0.x. While we will be continuing ongoing development on the dev branch, we will backport fixes into the 2018.0.x branch continuously. At the end of each month, there will be 2 releases, one tagged on each branch. For example, in one month, we will release both 2018.1.0 (like before) and 2018.0.1, the latter containing all the bug fixes from January, without the unstable/ongoing features.

As for protocol updates (1.13+), we will be backporting them to the long-term support branch one month after they are released on the dev branch.

2017 in Review

Let’s take a step back and look at what we have accomplished in 2017.
590 commits have been pushed to the master/dev branch, consisting of 35,242 additions and 12,287 deletions.
We have released a total of 13 releases (including today’s), which can be summed up to these key points:

• We are sponsored by Aternos
• We have a brand new website, with goodies like news posts and users
• Our team grew by 5 developers! Welcome, PickNChew, Postremus, Kyureki, Pr0methean, and kaenganxt
  • In total, we received code contributions from 24 users
• ProtocolSupport natively supports Glowstone
• We now have a CLA and a new Code of Conduct
• Glowstone is much more stable, polished and optimized
• A lot more features have been implemented
• Entities are much, much better and complete
  • Implemented Boats, Ender Crystals, Paintings, Parrots, XP Orbs, Leashes, Ender Pearls, complex entities (Ender Dragon)
  • Entity physics
  • Ambient and hurt sounds
  • Basic entity AI tasking
  • Custom entities for plugins
• Basic piston implementation
• Rewrote most commands, including multiple tools to parse and implement new commands
• And a lot, lot more.

So thank you, everyone, for such a wonderful year. Here’s to another solid, productive and joyful new year for all of you.

See you next time, and thanks for all the (498) stars this year,

The Glowstone Project.

This post was mirrored from the site.

For this monthly release of the Glowstone server, 2017.10, we now officially support 1.12.2. We also added some new features, optimized magic stuff in the background and worked on some new technical features.

As always, we remind you that the easiest way to chat with us to ask questions or support is on our Discord server.

Additions

• Added support for 1.12.2 (#566)
  • Dropped 1.12.1 support
• Added pistons (#577) (PickNChew)
• Added /testfor command (#573) (Kyureki)
• Added /testforblock command (#579)
• Added technical API for block state parsing in commands (#579)
• Added some missing entity NBT tags
  • Tags and PortalCooldown for all entities
  • Color for shulkers
• Added despawning of out-of-range hostile mobs
• Added chorus flower, plant and fruit (#582) (kaenganxt)

Changes and Fixes

• Ameliorated entity knockback considerably
• Optimized memory usage of chunk keys (#569)
• Fixed an exception when running Glowstone in an IDE (#568) (Z750)
• Fixed @r random selector (#575>) (kaenganxt)
• Fixed some food features and updated food saturation values (#578) (kaenganxt)
• Replaced Random instances by ThreadLocalRandom (#581) (PickNChew)
• Changed GlowServer.getVersion() to match the format in other Vanilla wrappers
• Replaced duplicates of BlockFace arrays in block types into one array (#583) (kaenganxt)

Other Updates

We also fixed an issue with ProtocolSupport which prevented it from loading on Glowstone 2017.10 snapshots. Make sure you use the latest version of ProtocolSupport with Glowstone!

We are also welcoming PickNChew in our developer team. He previously implemented particles, revamped the entity registry system, and implemented rails and pistons.

We have also been working on some more technical features this month. mastercoms has been working on a new “block function” system for a little while now, and we hope to see this completed and merged for the next release. I have also worked on a little side project with annotated NBT, so we will see where that goes as well.

That’s it for now, we’ll see you in the next release.

This post was mirrored from the site.

Hello everyone, we are releasing Glowstone 2017.9. This is the last release to support 1.12.1, as 2017.10 will support 1.12.2.

Additions

• Implemented /enchant command (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/560”>#560</a>)
• Implement Enderman carried block (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/561”>#561</a>)
• Added a new API for Villager Careers (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/563”>#563</a> and Glowkit #13)
• Added a new API for Entity Animations (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/564”>#564</a> and Glowkit #14)
• Implemented critical hits and damage enchantments (#564)
• Implemented /effect command (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/555”>#555</a>)
• Implemented the pvp setting the the server configuration

Changes and Fixes

• Fixed the /effect command not accepting Vanilla IDs (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/558”>#558</a>)
• Fixed certain entities which couldn’t be spawned using /summon (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/541”>#541</a>)
• Fixed incorrect Enderman ‘carried block’ metadata

Other Updates

After a few months of work, we have merged the beta site into production. We have dropped our Github pages site in favor of the Site software written in Python by gdude. Please let us know of any problems with the site on Discord or in the repository’s issues.

That’s it for now, see you all again in the next release!

This post was mirrored from the site.

Hi everyone, we are releasing Glowstone 2017.8.1, which is the first official release to support 1.12.1. Not much has happened since 2017.8.0, but here’s the changelog nonetheless:

Additions

• Implemented Experience Orbs
• Implemented Leashes (#538)
• Implemented /effect command (#555)
• Added ambient and death sounds for Ender Dragon
• Added network code for Craft Recipe Response and Crafting Book Data packets
• Started implementation of the Recipe Book, including I/O and network code
• Implemented API methods related to Lightning (#546)
• Added burn-time for all burnable items
• Added option to verify and validate incoming connections (#553)

Changes and fixes

• Fixed animals not spawning at all due to a mistake
• Optimized function storage using Map instead of List (#537)
• Fixed some issues with library management, and updated some libraries (#540 and #544)
• Fixed an issue with player head-rotation not being sent (#551)
• Fixed an issue with /tp player toplayer not doing anything (#554)
• Fixed shift-clicking in containers, again (#557)

Other Updates

We’ve had a slow schedule this month, mostly due to everyone being busier than usual.

I have personally stepped down as project lead and haven given this responsibility back to mastercoms because I will have much less time to give to this project due to college and other stuff.

Also, I’d like to welcome Postremus to our development team. He has been working a lot on this project recently and has implemented a lot of major features, including leashes this month.

That’s it for now, we’ll see you guys later! :^)

This post was mirrored from the site.

Hello everyone, today we are releasing Glowstone’s July release, 2018.7.0.

This update is very small, as updating to 1.13 is our priority. You can follow 1.13 development on Pull Requests #957 and #958.

We recently moved our Maven repository to Sonatype Nexus. Old artifact versions are currently unavailable, but we are working on re-deploying them to the new repository.

Additions and Changes

• Attribute management overhaul (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/955”>#955</a>)
  • Migrated to Bukkit’s Attribute API
  • Implemented modifiers
• Improvements to Mojangson boolean parsing
• Updated dependencies
  • Updated Glowkit to 1.12.2-R5.0-SNAPSHOT
  • Updated kotlin to 1.12.51
  • Updated JUnit and surefire plugins

Fixes

• Fixed inconsistency with bow charging animation
• Fixed some i18n formatting errors

That’s all for now! You can download the update from the GitHub release.

This post was mirrored from the site.

Hi all,

We are releasing Glowstone 2018.5.0 today,
which is the monthly release for May 2018.

Since the previous release, we have received contributions from 9 contributors,
including 3 first-time contributors: Mystiflow, Jacob (jhg023), and aki-ks.

This brings the total of GitHub contributors to a whopping 100! We’d like to thank every person who has taken time to
help this project throughout the years, and we’re looking forward to a hundred more!

Additions and Changes

• Implemented mining speed depending on tools, based on work by satoshinm (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/506”>#506</a>)
• Implemented a few API events (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/922”>#922</a>)
  • CauldronLevelChangeEvent
  • EntityAirChangeEvent
  • PlayerShearEntityEvent
  • EntityTameEvent
  • ItemMergeEvent (VaiTon)
  • ExpBottleEvent (VaiTon)
  • CreeperPowerEvent (VaiTon)
  • PlayerToggleFlightEvent (Jacob)
  • PlayerEggThrowEvent (Mystiflow)
  • ProjectileLaunchEvent (Mystiflow)
  • BlockExplodeEvent (Mystiflow)
  • PlayerSwapHandItemsEvent (Jacob)
  • InventoryOpenEvent (Jacob)
  • VehicleEnterEvent (Jacob)
  • ProfileWhitelistVerifyEvent
• More internationalization
• Added utility to clean up game tick conversion (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/917”>#917</a>)
• Refactored NBT deserializaton using a functional syntax (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/905”>#905</a>)
• Updated lombok to support Java 10
• Updated Glowkit

Fixes

• Fixed shooting bow with off-hand damaging the player’s main hand (fionera)
• Fixed breaking blocks instantly not registering (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/852”>#852</a>)
• Fixed a client-side desync when canceling SheepDyeWoolEvent (Mystiflow)
• Fixed the inlining of certain constants when compiling (aki-ks)
• Fixed some issues with unit tests

Upcoming

mastercoms has been working on updating JLine to version 3, revamping our console system, and bringing new exciting features such as interactive tab-completion, customization, and Java source code evaluation. The JLine3 PR is currently in review/bug fix state and should be ready for the next release.

creatorfromhell has also been working on an A* pathfinding implementation, and we are looking forward to merging it for the next release as well.

That’s all for now, you can download this release on GitHub. Thanks!

This post was mirrored from the site.

Hi all,

Today we’re releasing Glowstone version 2018.4.0. The previous release, 2018.3.0, was a bit late into April, so this one
is a little shorter than usual. Nevertheless, here is the changelog.

We received contributions from 6 community members, including 2 first-time contributors (jordanmurray and Muqsit).
As usual, we thank you for your effort!

Additions and Changes

• Enhanced entity physics calculations, fixing some inconsitencies (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/897”>#897</a>) (XuZhen86)
• Enhanced player throw physics (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/901”>#901</a>) (jordanmurray)
• Implemented animal feeding and baby growth acceleration (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/900”>#900</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/907”>#907</a>) (FlorentClarret)
• Configuration file changes (glowstone.yml)
  • Reorganized library configuration options
  • Removed unused database configuration
  • Implemented creatures.enable.monsters and creatures.enable.animals settings
• Added ability to download dependencies for libraries defined in the config (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/889”>#889</a>)
• Added support for Paper’s new PaperServerListPingEvent (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/880”>#880</a>) (Minecrell)
• Tweaked and refactored internal i18n usage (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/895”>#895</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/908”>#908</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/909”>#909</a>)
• Converted more strings to i18n (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/904”>#904</a>)
• Various code cleanup and enhanced Javadocs
  • Added an internal utility for tick conversion (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/911”>#911</a>) (FlorentClarret)
• Updated netty to 4.1.24
• Moved trove4j from Glowstone to Glowkit

Fixes

• Players can now place blocks when clicking on signs (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/902”>#902</a>) (smcconke)
• Fixed bug in ore vein generation (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/912”>#912</a>) (Muqsit)
• Removed duplicate slf4j binding

New Project Members

We have 2 new developers / project members in the team: FlorentClarret and smcconke. Thank you for your valuable contributions!

New Glowstone Documentation

We have begun transferring our Github wiki to a website called ReadTheDocs. It uses a more advanced markup language, RST, and allows for more styling options. It also allows versioning, which will make it possible to separate documentation between Glowstone releases.

As we are gradually migrating information to the new website, we are planning to enhance documentation to make it easier for new users to take advantage of Glowstone. It is available at docs.glowstone.net.

That is all for now, see you next month!

This post was mirrored from the site.

Hi all,

We are releasing Glowstone 2018.3.0 today, which is about two weeks behind our monthly schedule. Our team has been quite busy with other
projects and work for most of April. Without further ado, this is the changelog since the beginning of March.

We’ve had contributions from two first-time contributors, fionera and smcconke. Thank you for your time and effort!

Additions and Changes

• Updated to Glowkit 1.12.2-R2.1
• Added configuration validation for value types (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/870”>#870</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/869”>#869</a>)
• Implemented fire-damage for all entities, and proper bounding-box checks (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/888”>#888</a>) (smcconke)
• Implemented donkey, mule, and llama inventories (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/872”>#872</a>)
• Started work on i18n translations (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/874”>#874</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/883”>#883</a>)
• Refactored dependency management to use “compatibility bundles” (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/879”>#879</a>)
• Added shutdown message to /stop [message...] command (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/844”>#844</a>)
• Implemented slime-chunk formula (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/894”>#894</a>) (fionera)
• Add generic.flyingspeed attribute (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/878”>#878</a>) (FlorentCarret)
• Replaced a lot of reflective calls with Java 8 references, for optimization (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/860”>#860</a>)
• Added more unit tests for entities (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/863”>#863</a>)
• Added unit tests for boss bars
• A lot of refactoring to unit tests

Fixes

• Fixed an exception when spawning area-effect-clouds
• Fixed an exception when spawning an entity using the implementation classes (GlowXYZ)
• Fixed inconsistency with UUID lookups in player profiles (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/881”>#881</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/882”>#882</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/886”>#886</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/891”>#891</a>)

Coming Soon

We have a few more pull-requests in queue for review and merge. You may expect these to be ready for the next monthly release.

• Support for PaperServerListPingEvent and Glowkit upstream merge (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/880”>#880</a>)
• Adapt changes to dependency manager to allow for external libraries and conflict resolving (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/889”>#889</a>)
• Support for off-hand bow usage (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/893”>#893</a>)
• More refactoring and implementation for i18n support (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/895”>#895</a>)
• Enhanced entity physics (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/897”>#897</a>)

mastercoms is also currently working on updating Glowstone to jline 3.

Other News

As previously mentioned, we’ve all been quite busy with other endeavors in the past few weeks. However, we’ve been looking into a few
para-development subjects such as registering as a not-for-profit organization (501(3)) and other licensing issues.

I’ve personally developed a plugin for Glowstone to replace file-system world storage with a Redis solution, using our recent world-storage API created by Kyureki.

This post was mirrored from the site.

Hi everyone. We are a few days behind schedule, but today we are releasing Glowstone 2018.1 and the complementary LTS update, 2018.0.1.

This month, we worked on a few major features and fixed a lot of bugs.
As explained in the Year in Review news post, we will release two updates every month: an official monthly release containing all of the bleeding-edge features from the last month, and a complementary LTS (long-term-support) release which backports bugfixes to the stable branch.

We also want to thank new contributors XuZhen86, Minecrell and HugoDaBoss for their valuable contributions this month!

Additions and Changes

• Implemented projectiles (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/614”>#614</a>)
  • Thanks to Pr0methean for his continuous work on this PR for over a month
• Implemented /testforblocks command
• Added checksum validation for library manager (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/802”>#802</a>)
• Revamped library manager to allow for customization by server owners (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/808”>#808</a>)
• Added configuration file validation (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/809”>#809</a>)
• Updated API to 1.12.2-R1.0
  • Implemented Paper’s Profile API
• UUID lookups in commands are now asynchronous (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/111”>#111</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/814”>#814</a>)
• Implemented droppers (previously behaved like regular dispensers)
• Implemented advanced.suggest-player-name-when-null-tab-completions configuration option
• The server icon file will now be imported automatically from a Vanilla server
• Initial implementation for villager trading UI
• Implemented starvation damage modifier for different difficulties (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/835”>#835</a>) (XuZhen86)
• Implemented correct conditions for mob experience drops (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/823”>#823</a>) (XuZhen86)
• Added --generate-config command-line option to generate config files without starting the server
• Implemented grass path block (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/841”>#841</a>)
• Implemented Zombie Villager NBT storage
• Cleaned-up the ItemType.Context enum
• Moved building scripts to a separate directory
• Code style cleanup and lombokification
• Updated lombok and kotlin dependencies

Bug Fixes

• Fixed an error when loading Vanilla worlds containg Minecart-with-Chests
• Fixed an error when using command selectors with entities
• Fixed a concurrency error in chunk streaming
• Fixed incorrect ender pearl behaviour (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/822”>#822</a>) (XuZhen86)
• Fixed incorrect fall damage when switching gamemodes (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/820”>#820</a>) (XuZhen86)
• Properly implemented Player#getVirtualHost() and Player#getProtocolVersion() APIs (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/824”>#824</a>) (Minecrell)
• Fixed SLF4J logging for plugins (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/825”>#825</a>) (Minecrell)
• Fixed item drops for cactus and dead bush (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/832”>#832</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/833”>#833</a>) (XuZhen86)
• Fixed incorrect anvil sounds when landing on several blocks (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/827”>#827</a>) (HugoDaBosss)
• Fixed an error when spawning wolves from spawn eggs
• Fixed NBT storage for Strays, Wither Skeletons and Husks not being bound

Download links for both the release and the LTS update can be found on our website.

Thanks!

This post was mirrored from the site.

Today, we are putting in place Glowstone’s new Cheating and Illegal Behavior Policy. This is an effort to engage ourselves in our position against illegal piracy and behavior in the context of our project.

Although Glowstone will always keep the online-mode: false option functional in the server configuration for testing and development reasons, we will not put extended effort into keeping our software compatible with pirated software (such as cracked clients). Our mission, on that front, is to stay at the same level of compatibility as Mojang’s server software.

In addition, this new policy extends to the usage of illegally distributed or obtained products used with Glowstone (including plugins and libraries). In other words, we will not assist users if their support request implies the usage of cracked premium plugins or similar products. This also applies to the usage of cheating/hack clients (in the context of a support request).

The policy document can be found in our GitHub repository.

Thank you for your comprehension. As always, feel free to communicate to us any concerns about this new policy.

The Glowstone Project.

This post was mirrored from the site.

As fireworks are let off for the end of 2017, we are releasing this year’s final version: 2018.0.0. In the last month, we’ve been working hard on polishing Glowstone as much as we could, and this has resulted in one of our most productive months in terms of commits, merges, bugs resolved and code written.

We’ll start with a quick changelog of what has been done since the last release, 2017.11, then follow with a recap of the year!

Glowstone 2018.0.0

This month, we’ve pushed 138 commits consisting of 17,993 additions and 11,491 deletions in 938 files.
There are a lot more changes than what I can list here, so you check check out the git diff if you want more details.

• Implemented /clone command (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/590”>#590</a>)
• Implemented Ender Pearls (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/602”>#602</a>)
• Added support for Java 9 (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/649”>#649</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/652”>#652</a>)
  • Note that while Glowstone can run on Java 9, it can only be built on Java 8.
• Fixed a number of bugs with player interactions (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/644”>#644</a>)
• Fixed issues when shift-clicking in the crafting inventory
• Fixed an exception when joining a Glowstone server run from an IDE
• Fixed gravity not updating the location of items (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/591”>#591</a>)
• Fixed a number of bugs with fall damage
• Fixed the minimum food level to regenerate health from 19 to 18
• Fixed, rewrote and optimized chunk indices (Chunk.Key)
• Improved region file I/O, fixing some issues (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/199”>#199</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/510”>#510</a>)
  • More details can be found in commits 98aeb19, 34ce26b, 3179cef
• Optimized chunk streaming to players
• Improved hanging entities (paintings, item frames) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/597”>#597</a>)
• Fixed a number of bugs with Sign editor (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/596”>#596</a>)
• Fixed an exception when pinging the server behind a proxy (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/599”>#599</a>)
• Updated Netty from 4.1.0.CR7 to 4.1.17.Final
• Fixed inventory slots in HumanEntity spawn packet
• Rewrote ItemTable to use Material instead of item IDs
• Fixed inconsistencies with PlayerInteractEvent (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/595”>#595</a>)
• Fixed open inventory not being closed when player is teleported (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/594”>#594</a>)
• Partially implemented MapView/map rendering API (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/572”>#572</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/605”>#605</a>)
• Added slf4j back-end dependency (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/612”>#612</a>)
• Abstracted WorldStorageProvider to allow plugins to change how world data is saved and loaded
• Added log4j configuration
• Cleaned up chunk locks (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/623”>#623</a>)
• Implemented Fire Resistance potion
• Refactored EntityManager and BossBar management (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/636”>#636</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/641”>#641</a>) (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/642”>#642</a>)
• Fixed a concurrency exception when players switch worlds (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/628”>#628</a>)
• Implemented ItemSpawnEvent and ItemDespawnEvent (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/643”>#643</a>)
• Updated checkstyle
• Removed metrics
• Removed GlowClient and related dependencies
• A lot of code and documentation cleanup
• Updated Kotlin runtime to 1.2.0
• Updated CI to use CircleCI 2.0 on all branches, builds are now much faster

Whew, that was a lot of polishing. In addition of all these changes, we are also pleased to welcome 2 new developers as part of the team: Pr0methean and keanganxt.

Note that we now use the dev branch for ongoing work, while the master branch will be deleted. We have decided to try a new release format for 2018. We have updated our download section to reflect these changes.

We created a long-term support branch (LTS), 2018.0.x. While we will be continuing ongoing development on the dev branch, we will backport fixes into the 2018.0.x branch continuously. At the end of each month, there will be 2 releases, one tagged on each branch. For example, in one month, we will release both 2018.1.0 (like before) and 2018.0.1, the latter containing all the bug fixes from January, without the unstable/ongoing features.

As for protocol updates (1.13+), we will be backporting them to the long-term support branch one month after they are released on the dev branch.

2017 in Review

Let’s take a step back and look at what we have accomplished in 2017.
590 commits have been pushed to the master/dev branch, consisting of 35,242 additions and 12,287 deletions.
We have released a total of 13 releases (including today’s), which can be summed up to these key points:

• We are sponsored by Aternos
• We have a brand new website, with goodies like news posts and users
• Our team grew by 5 developers! Welcome, PickNChew, Postremus, Kyureki, Pr0methean, and kaenganxt
  • In total, we received code contributions from 24 users
• ProtocolSupport natively supports Glowstone
• We now have a CLA and a new Code of Conduct
• Glowstone is much more stable, polished and optimized
• A lot more features have been implemented
• Entities are much, much better and complete
  • Implemented Boats, Ender Crystals, Paintings, Parrots, XP Orbs, Leashes, Ender Pearls, complex entities (Ender Dragon)
  • Entity physics
  • Ambient and hurt sounds
  • Basic entity AI tasking
  • Custom entities for plugins
• Basic piston implementation
• Rewrote most commands, including multiple tools to parse and implement new commands
• And a lot, lot more.

So thank you, everyone, for such a wonderful year. Here’s to another solid, productive and joyful new year for all of you.

See you next time, and thanks for all the (498) stars this year,

The Glowstone Project.

This post was mirrored from the site.

On Sunday, we updated Archiva (our Maven repository) to a more recent version. During the upgrade, we unfortunately lost all our artifacts stored on the server. There was a major downtime in which we attempted to fix storage and deployment, but the artifacts could not be recovered.

Because we did not have backups for the Maven repository, (that would take a lot of space, considering each snapshot is ~19MB) we had to re-deploy the latest snapshots manually.
Deployment now works and further builds will be added to the repository. Note that any artifact older than 2018.0.0-SNAPSHOT (including the latest release, 2017.11) will cause 404 errors in your builds.
Furthermore, only the latest Glowkit version (1.12.2-R0.1-SNAPSHOT) is on the repository, and older artifacts will also 404.

Due to an issue with how Archiva indexes the Browse tool, you will still see metadata version about all previous artifacts that were on the repository prior to the upgrade. We have contacted Archiva for a fix to reset the search indexing to what we have now.

We are very sorry for the inconvenience the downtime and artifact loss may have caused. If there are more issues, please contact us on Discord.

This post was mirrored from the site.

It is the monthly blog post for Glowstone 2017.11, my Glowstoners.

Come say hi and ask questions on the Discord server

This month, we did things:

Additions

• Added /setblock command.
• … yeah so that’s it.

…

Just kidding!

Changes and Fixes

• Repealed and Replaced chunk key optimization to a system that isn’t broken (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/586”>#586</a>) (Kyureki)
• Fixed a concurrency crash with the Entity AI task manager (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/584”>#584</a>) (Microsamp)
• Fixed fire not being updated on tick (<a href=“https://github.com/GlowstoneMC/Glowstone/issues/435”>#435</a>) (kumpelblase2)
• Fixed tools not being damaged when using them
• Cleaned-up and fixed bugs with world borders
• Various code cleanup-ing
• Updated Kotlin to version 1.1.51

Other Updates

I was testing ProtocolSupport with the latest version of Glowstone and it was broken. So I fixed things. So now you can seamlessly use 1.4.7-to-1.12 clients on Glowstone using the plugin, with build 182 and above!

Also, we are welcoming Kyureki (a.k.a. smartboyathome on GitHub) on our developer team!

Finally, I just wanted to point out that we had a high increase in traffic on the website and GitHub because we got voted up to the top on Hacker News and the front-page of /r/Minecraft. That’s very cool! It wasn’t us who posted them, I promise. Thanks for all the stars and love

I think I have used all possible variations of “thanks for reading” in the previous posts, so I’m just going to say:

Thanks for reading!

This post was mirrored from the site.

For this monthly release of the Glowstone server, 2017.10, we now officially support 1.12.2. We also added some new features, optimized magic stuff in the background and worked on some new technical features.

As always, we remind you that the easiest way to chat with us to ask questions or support is on our Discord server.

Additions

• Added support for 1.12.2 (#566)
  • Dropped 1.12.1 support
• Added pistons (#577) (PickNChew)
• Added /testfor command (#573) (Kyureki)
• Added /testforblock command (#579)
• Added technical API for block state parsing in commands (#579)
• Added some missing entity NBT tags
  • Tags and PortalCooldown for all entities
  • Color for shulkers
• Added despawning of out-of-range hostile mobs
• Added chorus flower, plant and fruit (#582) (kaenganxt)

Changes and Fixes

• Ameliorated entity knockback considerably
• Optimized memory usage of chunk keys (#569)
• Fixed an exception when running Glowstone in an IDE (#568) (Z750)
• Fixed @r random selector (#575>) (kaenganxt)
• Fixed some food features and updated food saturation values (#578) (kaenganxt)
• Replaced Random instances by ThreadLocalRandom (#581) (PickNChew)
• Changed GlowServer.getVersion() to match the format in other Vanilla wrappers
• Replaced duplicates of BlockFace arrays in block types into one array (#583) (kaenganxt)

Other Updates

We also fixed an issue with ProtocolSupport which prevented it from loading on Glowstone 2017.10 snapshots. Make sure you use the latest version of ProtocolSupport with Glowstone!

We are also welcoming PickNChew in our developer team. He previously implemented particles, revamped the entity registry system, and implemented rails and pistons.

We have also been working on some more technical features this month. mastercoms has been working on a new “block function” system for a little while now, and we hope to see this completed and merged for the next release. I have also worked on a little side project with annotated NBT, so we will see where that goes as well.

That’s it for now, we’ll see you in the next release.

This post was mirrored from the site.