And well, purely judging from a quick glance at the documentation, it does not seem to be nearly as mature as Luanti. I have no way of comparing the size of their featuresets, I’m purely talking that you have a certain featureset which is battle-tested and stabilized and usable for outsiders, which does require extensive documentation of all kinds of eventualities.
I don’t find it hard to believe that a single passionate person would be able to dish out a similar featureset to Luanti, but yeah, do not underestimate how much work maturing a project is and then not breaking backwards-compatibility when others actually depend on your project.
But so long as it remains proprietary, I do not see anyone wanting to use that engine anyways, so no idea if it even matters… ¯\_(ツ)_/¯
@Ephera I haven’t compared the whole project. I compared the addition of features and their derivatives. The mentioned project started quickly from zero and spent the year fixing problems like optimization. Luanti, however, has had problems since 2018 — flickering shadows, render bugs, and so on. I haven’t seen any big fixes this year, only pure features or rewritten documentation.
@Ephera Exactly. Luanti is now the best project in the open-source community, but from a spectator’s point of view nobody wants it. “Why bother if we have Minecraft and already Hytale?”
But you have a point. The community is mostly the core of progress.
Just mentioning that the progress of the core is very slow from a spectator’s point of view
Yeah, I believe one of the big things they are working on, is replacing large parts of the technologies that they base on with more modern alternatives. This here changelog does mention SDL, for example. If they’re integrating that fully, it will handle all input. That’s a big change for the codebase, even though the user-facing impact is zero at first. It just ensures that you can keep maintaining and extending the codebase in the future.
And yeah, you don’t need to do that kind of thing in a codebase written from scratch, for obvious reasons. 😅
Hmm, seems to be proprietary? At least, I’m not seeing a license in the repository, if this is it: https://github.com/MihailRis/voxelcore/tree/main
And well, purely judging from a quick glance at the documentation, it does not seem to be nearly as mature as Luanti. I have no way of comparing the size of their featuresets, I’m purely talking that you have a certain featureset which is battle-tested and stabilized and usable for outsiders, which does require extensive documentation of all kinds of eventualities.
I don’t find it hard to believe that a single passionate person would be able to dish out a similar featureset to Luanti, but yeah, do not underestimate how much work maturing a project is and then not breaking backwards-compatibility when others actually depend on your project.
But so long as it remains proprietary, I do not see anyone wanting to use that engine anyways, so no idea if it even matters… ¯\_(ツ)_/¯
@Ephera I haven’t compared the whole project. I compared the addition of features and their derivatives. The mentioned project started quickly from zero and spent the year fixing problems like optimization. Luanti, however, has had problems since 2018 — flickering shadows, render bugs, and so on. I haven’t seen any big fixes this year, only pure features or rewritten documentation.
@Ephera Exactly. Luanti is now the best project in the open-source community, but from a spectator’s point of view nobody wants it. “Why bother if we have Minecraft and already Hytale?”
But you have a point. The community is mostly the core of progress.
Just mentioning that the progress of the core is very slow from a spectator’s point of view
Yeah, I believe one of the big things they are working on, is replacing large parts of the technologies that they base on with more modern alternatives. This here changelog does mention SDL, for example. If they’re integrating that fully, it will handle all input. That’s a big change for the codebase, even though the user-facing impact is zero at first. It just ensures that you can keep maintaining and extending the codebase in the future.
And yeah, you don’t need to do that kind of thing in a codebase written from scratch, for obvious reasons. 😅