It has been almost a year since we have updated this blog. This has been for various reasons, foremost it was not of priority to the team as we did concentrate on the game itself. This post will start to explain a few changes we did implement last year and continues with some issues we are working on right now.
What happened with Inexor?
We have kept modifying Inexor to be more modable and flexible, which in turn led to many changes and additions to the overall architecture e.g.:
- Implemented Inexor Flex
- => our scripting side
- => plugin system
- => command line interface
- Created the Inexor Tree API
- => Automatic synchronization of nodes from Inexor Core to Inexor Flex and vice versa including:
- ==> Lists (SharedLists)
- ==> Classes as directories in the Tree (inheriting from a common base class)
- ==> Functions (SharedFunction)
- ==> and usual variables (SharedVar)
- => on Flex side you
- ==> you get signaled if that node changed
- Porting our dependency management to Conan
- Fixed several bugs with the ingame HTML rendering
Changes to our infrastructure
There have been several outtakes of our server which leaded to most of the services being outsourced, e.g. our Etherpads for which we use now mostly hackmd.io. Furthermore our website is now hosted at Uberspace.
We switched our IRC channel from Gamesurge to Freenode. You can found us now at
or on our new channel on Riot.im (recommeded):
Riot is a Matrix client, so you can connect to #Inexor:matrix.org with every compatible Matrix client. Therefore there are now more possibilities to chat with us as before. Both rooms are getting synced so nobody is missing something. We are recommending Riot since it is eliminating the need for a bouncer and has more features than IRC like file uploads and voice chats.
@koraa decided to leave us to work on new projects. Thank you for being with us from the beginning and good luck!
However, we are also happily noticing that new people are getting constantly interested in our project and we are welcoming new voices with open hands.
If you like our overall ideas and vision for the game we would like to hear from you. No matter if you can code, create maps or other assets, write blog posts or just want to hunt bugs down. We can need you 😊
How you can help
Things are getting really fast recently, but there are still a lot of things which need to be done. So, what you can do is:
- help us test
- help us fix and maintain the CEF integration
- getting involved in an experimental rewriting of the website
- some other things, check the issue ticker
- anything you would like to see in Inexor!
- Check if you find wrong/outdated/questionable content and let us know
- Spread the word about Inexor!
- => Write an article
- => Link to us
- => Tell your class mates, gamer friends and developer fellows
- => Send a mail to mailing lists that care about FLOSS
We really loved our first Hackathon and it will not be the last.
Right now we are planning the Inexor Hackathon 2017. It will be likely at some time in Summer and in some southern area of Germany. As soon as we know more we will publish a standalone announcement. Thanks to Fohlen to push these plans forward!
Of course everyone will be welcomed at the Hackathon. No matter if you already contributed to Inexor or just like the project or just heard of us because of the Hackathon announcement. Last time we had a few new people just being curious who gave it a shot and we would love to see this repeating.
We don't bite, promised! —— Well, just in-game at least.