Use our engine to make your next fantastic game!
Contribute code! Remove a bug, add a feature! (Not the other way around:)
Code changes are best submitted as pull requests on GitHub. Pull requests are really easy for you to create (fork our repository, commit stuff to your fork, then create a pull request by clicking on GitHub), and for me to apply.
If you're looking for a feature to implement, take a look at our planned features.
Contribute to our wiki useful tips or tutorials about using our engine.
If you use Castle Game Engine or our tools (like view3dscene) to view or play anything (a game, or just your 3D or 2D assets):
Show it on our Discord or forum by sharing a screenshot or movie recording. Michalis loves to see how his work is useful for others :)
Contribute models to our demo models.
Look into improving our documentation. Our scene graph (X3D) documentation is large, and wants to be larger. Contributions describing how something works, or how to do something practical, are welcome.
Test the view3dscene snapshots. These are build automatically after every commit to GitHub. You can test them and catch eventual bugs before the release. This way you can also preview new features before they are released.
Bugs are best reported in the issues tracker.
view3dscene is a versatile and stable viewer for many model formats.
Castle Game Engine features are listed here.
Desktop integration files (SVG icons, .desktop files etc.) are already included in our archives.
Build-dependencies include Free Pascal Compiler, but this should not be a problem — all major distros already have fpc packaged.
Copyright Michalis Kamburelis and other Castle Game Engine developers.
Thank you to Paweł Wojciechowicz from Cat-astrophe Games for various graphics.
This documentation is also open-source and you can even redistribute it on open-source terms.