Hello

I’m working with Glowstone almost a year. Now I see some good changes in project (Glowkit with git patches, back to old name, new forum…), but what we should do next?

I really hope in future Glowstone will be used on 50% servers. But how we can do this?

I think first we should give reason to switch to Glowstone, mean before implementing all features.
Why? Less popularity = less devs will help with project.

How we can get it?

In my opinion, most important thing is performance. Server’s owners need handle as many as possible players. They don’t care about how it works. Just player amout and TPS.

My simple suggestions are:

• multithread core
  • separated for 16x16 chunks
  • separated for chunk list, with specified load
  • tick separated to few thread (players, entity, blocks)
• add async chunk loading (its really important)
• base player’s function
• maybe some forge support (wait a bit for it)

Why that? It’s base. Change this after implementation will be very, very hard.

Feel free to talk, and share it with friends

• Base entity ai
• Base multithread ticking
• Async chunk loading (I can do it)

#TeamJSON

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

Yea I didn’t see date xD

@Jonathan-Henrique Sponge uses remapper for vanillia classes. Why not use it for mods?

@momothereal Still dosen’t understand it. Sponge has a lot of devs. They could write own server from scratch twice, in different langs

Still dosen’t understand why they just don’t write their own server. And you are right, some parts of Sponge API isn’t good

#TeamJSON

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

I thought and we talked on IRC about that few times. First we have to rewrite base system, then create a simple mod for forge or vanillia client.

Main problem is performace. See how Forge runs.

Associated Sponge thread: sponge new era

Hello

I’m working with Glowstone almost a year. Now I see some good changes in project (Glowkit with git patches, back to old name, new forum…), but what we should do next?

I really hope in future Glowstone will be used on 50% servers. But how we can do this?

I think first we should give reason to switch to Glowstone, mean before implementing all features.
Why? Less popularity = less devs will help with project.

How we can get it?

In my opinion, most important thing is performance. Server’s owners need handle as many as possible players. They don’t care about how it works. Just player amout and TPS.

My simple suggestions are:

• multithread core
  • separated for 16x16 chunks
  • separated for chunk list, with specified load
  • tick separated to few thread (players, entity, blocks)
• add async chunk loading (its really important)
• base player’s function
• maybe some forge support (wait a bit for it)

Why that? It’s base. Change this after implementation will be very, very hard.

Feel free to talk, and share it with friends

“BlockType rewrite” is something wrong here?

Yea I didn’t see date xD

• Base entity ai
• Base multithread ticking
• Async chunk loading (I can do it)