schema
Cat God
I'm not against opening up the code. But it has to be done in an ordered fashion. The first people with access will be people I absolutely trust.
And I'm planning to do it in stages. The thing is, that organization of coding with multiple people is very time consuming. I don't want people to get into parts that have a shaky core: For example if someone was to make an amazing feature but it's build on a foundation that has to be changed for optimization. I don't want them to have to redo the whole feature. It just wastes time. So I want to release part by part of things I know are solid enough to be extended.
As a side-note: optimization is a very big buzz word in the gaming industry, often thrown around at will. Promoters often like to use that word when something is not working the way it should. but optimization is not something you can actually do efficiently at later stages. Most of of the core work that took so long is actually optimization. But, because there are atm limited features it won't make a big difference visually. The difference is, that planned features are already accounted for in terms of basic optimization in starmade (there can be deviations of course). And of course there are still ways to do it more efficiently, but what I want to avoid is having to change a system because there is something seriously wrong in the core. Just doing features without caring about the core will end up making the game limited. If the game is already slow with the features that are in, all the planned features will just add to that performance cost.
As that issue is often ignored and optimization is just promised when the game reaches beta or release state, I was in the past often disappointed by those games not actually having much optimization at all compared to their alpha states.
My point is basically: optimization has to happen now or never!
And I'm planning to do it in stages. The thing is, that organization of coding with multiple people is very time consuming. I don't want people to get into parts that have a shaky core: For example if someone was to make an amazing feature but it's build on a foundation that has to be changed for optimization. I don't want them to have to redo the whole feature. It just wastes time. So I want to release part by part of things I know are solid enough to be extended.
As a side-note: optimization is a very big buzz word in the gaming industry, often thrown around at will. Promoters often like to use that word when something is not working the way it should. but optimization is not something you can actually do efficiently at later stages. Most of of the core work that took so long is actually optimization. But, because there are atm limited features it won't make a big difference visually. The difference is, that planned features are already accounted for in terms of basic optimization in starmade (there can be deviations of course). And of course there are still ways to do it more efficiently, but what I want to avoid is having to change a system because there is something seriously wrong in the core. Just doing features without caring about the core will end up making the game limited. If the game is already slow with the features that are in, all the planned features will just add to that performance cost.
As that issue is often ignored and optimization is just promised when the game reaches beta or release state, I was in the past often disappointed by those games not actually having much optimization at all compared to their alpha states.
My point is basically: optimization has to happen now or never!