Since the entire Space Frontiers code-base consists of Rust code, Rust programmers are essential to expanding the gameplay by implementing new plugins and crates.
Learning resources, guides, YouTube tutorial videos and heavily refined and iterated code documentation will be key to introduce programmers to Space Frontiers.
However, because Space Frontiers is in an early development cycle and currently undergoing porting procedures it is not in an ideal state to contribute to the core or to expand upon it yet. The aforementioned learning resources haven't yet been created. Ways to get familiar with the code is by helping improve the code documentation and/or code layout. The modules, code naming and code placing could also be improved, new standardized practices for crate modules could be introduced. The generated code documentation is also very basic and insufficient in some areas. There are also Rust clippy lint issues to be resolved. Using CLion by JetBrains will also show more possible code improvements.
The code repository has a private AI machine learning model at Tabnine. If you have a paid Tabnine account you can request access to it.
Development is done on gitlab.starwolves.io/starwolves/space
No experience required, you can learn on the go. You will have to get familiar with git and the Bevy game engine, sign the contributor license agreement for gitlab.starwolves.io account activation.
You can get in contact by all means.
Financial rewards.
Learning resources, guides, YouTube tutorial videos and heavily refined and iterated code documentation will be key to introduce programmers to Space Frontiers.
However, because Space Frontiers is in an early development cycle and currently undergoing porting procedures it is not in an ideal state to contribute to the core or to expand upon it yet. The aforementioned learning resources haven't yet been created. Ways to get familiar with the code is by helping improve the code documentation and/or code layout. The modules, code naming and code placing could also be improved, new standardized practices for crate modules could be introduced. The generated code documentation is also very basic and insufficient in some areas. There are also Rust clippy lint issues to be resolved. Using CLion by JetBrains will also show more possible code improvements.
The code repository has a private AI machine learning model at Tabnine. If you have a paid Tabnine account you can request access to it.
Development is done on gitlab.starwolves.io/starwolves/space
No experience required, you can learn on the go. You will have to get familiar with git and the Bevy game engine, sign the contributor license agreement for gitlab.starwolves.io account activation.
You can get in contact by all means.
Financial rewards.