FAQ

FAQ

Q: Why is it called HoneyGO?

A: I started the project when 1.16 came out and the new block was Honey, so I chose to base my project naming after that and works quite well. GO is for golang.

Q: Why should I use HoneyGO?

A: You should not use HoneyGO just yet it's in pre-alpha and I'm still working on things with a lot of breaking changes in between builds. But I am planning on HoneyGO to be more performant and versatile than vanilla and forks like spigot, paper and tuinity. It's an ambitious goal to achieve; I am basically writing a Minecraft server from scratch and having to guess on many things, but it's why I like it, as it teaches me more on topics like networking, concurrency, and how game servers work in general.

Q: Will it have an API?

A: Yes HoneyGO will have an API called HoneyCOMB it will have native support for golang and potentially its own bytecode compiler/interpreter for plugins that are made to be simple and easy. I have talked more about this on issue #2

Q: What even is the point of making HoneyGO

A: Just to learn really, if it becomes much more than that it will be a major benefit and I will certainly be happy about it since I have put a lot of effort into this in between my time in college and preparation for university.

Q: When will it be ready?

A: No idea, I work on it whenever I can and I am working to make it have a use by adding in a reverse proxy called HoneyHive (Like a hive of servers).

Q: This project is cool and I want to help, how can I?

A: I am currently not accepting help as this project is still pre-alpha and I have to make sure that no code is based on Mojang which is hard without a CLA bot which I'm going to implement near beta or alpha.

Q: Why do you have a list of other servers in your readme? Don't you want people to only use HoneyGO?

A: I don't think of this as a race really, having a good performing MC server is nothing to compete about and I like helping others when I can. Knowledge is power.