---

Development

• 

  [2016Q2] Feature Voting Thread
  community vote official • • mastercoms

  7
  7
  Posts
  1563
  Views

  

  @kamcio96 https://github.com/GlowstoneMC/Glowstone/issues/379

• T

  Official Multiversion Support
  • Tom

  14
  14
  Posts
  2132
  Views

  

  @Tom Since we forgot to mention it here, you should know that ProtocolSupport now supports Glowstone, properly.

• T

  Glowstone performance
  • Tom

  3
  3
  Posts
  577
  Views

  

  We use a thread per world and also have worker threads for some block tick tasks and other things.

• 

  Updating to 1.11
  • momothereal

  1
  1
  Posts
  348
  Views

  No one has replied

• 

  Near-future development priorities
  • momothereal

  3
  3
  Posts
  698
  Views

  

  @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!

• M

  Reviving future plans
  tags • • MisterCavespider

  3
  3
  Posts
  795
  Views

  

  @MisterCavespider Also, those aren’t really our future plans. I never commented on that post, but I don’t think those future plans are good for us right now.

• H

  Problems with the new tick-map-system
  • hibo98

  5
  5
  Posts
  1169
  Views

  

  The new tile tick save format should handle that. It’s in a PR that will be merged soon.

• 

  Looking for feedback - Entity loot tables
  • momothereal

  6
  6
  Posts
  1359
  Views

  

  I’m with Jayson.

• 

  Glowstone future
  • kamcio96

  6
  6
  Posts
  1899
  Views

  

  @gdude2002 Sure, special api, some tutorials how port the mod, maybe class transformer for small plugins, we will do it

• 

  Forge support request for Glowstone++ 1.9 and further updates
  • Andrew Westbrook

  11
  11
  Posts
  2924
  Views

  

  @Andrew-Westbrook But as a clean room rewrite of vanilla Minecraft/CraftBukkit, we can’t use any CraftBukkit code, and Forge relies on Mojang code so heavily, so Forge support has no place in Glowstone, at least for now. If you want an updated Cauldron, that would be a separate project from Glowstone entirely.

• 

  Updating to 1.10
  • momothereal

  27
  27
  Posts
  7467
  Views

  

  @mastercoms I can’t update to 1.10 until Glowkit is updated, because it depends on it. I won’t PR my current branch since it uses my own version of Glowkit 1.10, and we should use the official Spigot/Paper API

• 

  Issue and pull request templates
  meta • • gdude2002

  1
  1
  Posts
  500
  Views

  No one has replied