Posted November 16, 2025 by Lyaaaaaaaaaaaaaaa
Hi everyone, it’s time for a new community report!
I have been working in part-time on AIdventure for almost 3 months now and it’s going great!
I said in the last report (of September 2025) I would produce a sprint every 4-5 weeks. Since 2 weeks, I have been waking up earlier to work on AIdventure one hour before going to work. For now I’m satisfied with this and I will be able to produce a sprint every 3 weeks (+ 2 days). So, you should expect an increase in the pace of the releases.
On Steam, the users can choose to try the latest changes in a branch I called “sprint release”. This branch will die soon as I will use the “Experimental” branch once again for this stuff. There is no point in having 2 testing branches.
In my previous report I also said I would produce a stable release every 4 sprints (~4-5months). I decided to change this.
This means releases will be smaller but more frequent. In the actual case, the latest changes are stable and could be published, but they remove a working feature (the automatic translation). So, in this case I won’t publish it yet.
In the future, most of the new content won’t be rework that break old features. So I expect to release as often as possible!
The next sprint should contain the following stuff:
So, based on my current work, I think the 29th you can expect a new unstable release. If all goes smooth, I will publish it in stable the 6th december.
The 3.0 will have a brand new system to run AIs and an auto translation with a much better translation (I’m testing it with French and it gives amazing results!).
Because my time is precious and I want to spend most of it making the game better, I started working on the automatisation of repetitive tasks.
Now, publishing a release is automatic! The faster it is, the easier it will be for me to publish and the less risky (Making it automatic reduces the risk of human errors).
My goal is to do continuous delivery with AIdventure.
Long time ago I started writing unit tests (Automatic tests to verify the code is still behaving as expected. Useful to verify if you broke something while doing an update). I couldn’t motivate myself to write all the needed tests and keep them up to date.
Now, for a task to be considered done, I have to test it (if it’s testable) and write documentation about it. The tests and documentation are considered when I estimate how long a task will take. Therefore, I always write tests and doc.
Now I’m at 184 automatic tests to make sure nothing is broken. I will never have a coverage of 100% of my code (and it could never give a full insurance) but it’s always safer to have tests.
Testing a software as complex as a game is tricky (even for a text based one). So that’s the point of having experimental releases for users to test. It’s the best way as my time is limited. Moreover, it gives me quick feed back on new content.
The 25th December, It will be the 3 years of AIdventure’s first public release (1.0.0)! Some fun facts:
Thank you for supporting me on Ko-fi!
You can support me, too, on Ko-Fi.
Help yourself, help me, because helping me will help me to help you better.
If you like my work and want to help me, please, review AIdventure on Steam or rate it on Itch! It’s very important and can help me a lot!
Thank you for reading this report :).
See you next time.