Many weeks passed since I wrote the first entry! It is, what it is. Let’s not focus on the time passed, but the things being done. And I actually worked on #Project2 and also updated one of my tileset. What a way to starts the new year!
New Year, New updates.
So, I worked on that second project of mine. For context, on my last WeeklyLog, I was saying I’ll focus on only two projects. The second one being very simple, it was obviously the one I went back on to (also, the #Project1 still need some refactoring).
The second update is about one of my most popular tileset on itch.io, the Cave & Rails tileset. Nothing crazy, but well needed, as the last update dated from … well a long time ago.
Project 1: version 0.1.2
So this week, I essentially worked on the menu of the game. Especially the way the window open and close. Instead of just crudely flashing the white backdrop of the menu, I now use a sliding up and down motion. Good opportunity to play with tweens in Godot.
That being quite easy to put in action, I took the opportunity to challenge myself a bit and add a feature letting the user to drag down the menu close with a finger gesture. Not sure if required for that kind of project, but fun to code, I could, possibly add the same feature to open up the menu.
Caves & Rails: version 1.2
Last time I updated that asset was on march 2020, where I added some new tiles, like a Minecart! This update is focused essentially on the reorganization of the files. Instead of having one big file containing all the tilesets, I split them in different ones. Should be easier to work on them and update the asset package at the end.
Though, I still worked on some new tiles. All rail tiles now got a “broken” variation. Also started to work on some ores tiles, but still need to work on the colour palette. The total of tiles available in that pack are now 181.
More info and download link on the itch.io page :
Caves and Rails Tileset: v1.2 Update
Anyway, that’s all for this week!
Cheers.
w.
This week marks the start of my Weekly Logs! I’m sharing updates on my various game projects—what’s been tested, improved, and what’s coming next. I also plan to write some project-focused devlogs. I’ve got way too many projects started and abandoned here and there, so it’s high time to get things organized.
Side_side_side_side_project_version_finale_2.exe
It was long overdue to clean up and organize all these infamous game projects and other side projects I love to stockpile. I started this work a few weeks ago (read Cosmic Zombies Attack! : post-mortem), and this week got some good motion. I decided to focus on two projects only. I won’t share specifics yet, as there isn’t much to show.
Project 1: Started 2019/2020
- Engine history: Began in HaxeFlixel, later ported to Godot 3.5. Everything from HaxeFlixel was restored, Android export worked, possible future in-game ads integrated.
- Hiatus: Moved to another country, then Covid happened.
- 2024 revival: Switched to Godot 4.3 (Godot 3.5 was released 2 years old at that time). Gap between versions + learning curve → full refactor.
- Current status: Project still exports to Android, but many features are broken or incomplete. I’m starting again, but this time smarter: I created a GitHub repository.
It was first started using HaxeFlixel for the engine. It’s a simple, cute game aimed for Android. I later switched the engine to Godot (version 3.5), managing quite easily to bring back everything to the level I had with HaxeFlixel. Export to Android was working, integration of possible future in-game ads working too. Then, I moved to another country, followed by Covid.
Around summer 2024, I wanted to go back to it, alas the gap between my version of Godot and the new one was quite important (v4.3 was released in August 2024). Adding that I was still discovering the engine, I preferred then to switch to the new engine. Operating, at the same time, a full refactor.
Though, it seems that I stopped in the middle of it!
The project still exports successfully to Android, but a lot of features aren’t working anymore, or simply didn’t have been rewritten at the time. I’m gonna start back from that, even if it went through my mind that scrapping everything may be a better way. Anyway, the project is on rails again. And this time I’m going to try to be a bit smarter: I created a repository on Github.
Project 2: Started 2025
- Engine: Godot (recent version).
- Progress: First minor release (v0.1.0) committed; some mechanics already working.
- Goal: Simpler project, mainly to experience publishing on the Google Play Store.
- Next steps: Continue development and prepare for first publish.
It’s another Android app made with Godot. Though, this time, more recent, as I started it this year. I just committed my first minor release this week (v0.1.0), and some mechanics are already working as intended. Nothing especially to show for now. The concept of this one is quite simpler than the other, it’s mostly because I want to use that one as one that will let me experience my first publish on the Google Play Store. The project is simpler, but it will nonetheless be a challenge, as the publication of the app will be a first for me.
That being said, can’t wait to continue the work!
Errata memento
These Weekly Logs are also about remembering dumb mistakes, erratic tips, random shortcuts, and a plethora of things I learned.
This week: launching remote debug on Android from Godot v4.3.
- Problem: It worked perfectly in v3.5 on older projects, but nothing in v4.3.
- First attempt: Reinstalled the full development environment—no luck.
- Discovery: The reason was simple and easily forgotten.
In Godot 3.5: Click the little Android icon in the top-right corner of the window.
It was imprinted in my mind, you needed to click on the android that was sitting on the left of the media icon.
In Godot 4.3: The icon is slightly different, almost indistinguishable from others. Clicking it shows all available terminals for remote debug. A tiny UX change caused a whole day of frustration. Lesson learned: sometimes a “bug” is just a UX issue!
If only I had been curious enough to do so, I would have discovered that it then show all available terminals for remote debug. I would also have saved a day.
For what I know, it doesn’t seem that it’s possible to start a remote debug from the main project menu. So if you miss that icon, and had some problems by the past with android export in general, your first reflex is not going to think it’s just an UX problem!
Anyway, that’s all for this week!
Cheers.
w.
En cette fin d’année 2024 faisons un bond en arrière en se plongeant dans les vieux dossiers.
Et prenons ce projet qui remonte à loin, très loin. D’ailleurs la date de la dernière compilation est du 29/10/2011.
C’est un projet que j’avais mis en attente, dans la catégorie “Celui-ci, c’est sûr, je vais m’y mettre et le finir“. Autant dire que c’est une catégorie conséquente chez moi, et il est venu le temps de fermer ce dossier et d’en profiter pour faire le point.
Tout d’abord, un petit rappel du dit-projet !
Ce projet intitulé “Cosmic Zombies Attack!”, ou dans un premier temps “Paul against zombies!” avait pour objectif de créer un jeu pour Windows et navigateurs web, inspiré par des jeux de l’époque comme Canabalt ou encore Jet Pack Joyride.
Commencé en octobre 2011, le moteur de jeu que j’avais choisi était Construct 2. Moteur de jeu que je découvrais juste alors. Je ne me souviens plus vraiment pourquoi j’avais choisi ce moteur, mais je me souviens que la communauté était vraiment bienveillante. Cela m’avait appris tout un tas de chose intéressante, que ce soit sur le développement ou la façon de créer un jeu.
Mais en cherchant un peu sur le net, je vois que le moteur venait juste de sortir de sa beta début 2011 et sortait donc au grand public à la fin août 2011. Je le découvrais donc complètement aux premiers pas de sa sortie !
Pour un parfait néophyte, l’approche de Construct 2 était alléchante et permettait grâce à son interface centrée sur les events de créer des démos rapidement.
Au début de ce projet de jeu, l’objectif était à ce moment-là de tester ce moteur et de faire une petite démo. S’improvise ainsi un thème et une idée : faire un ersatz d’infinite-runner avec des zombies et d’exporter le tout pour le web. HTML5 était à son apogée et j’avais vraiment envie de toucher à tout ça.
Bien que Construct 2 permettait “donc”magiquement” de faire un jeu-vidéo sans avoir à coder, je me suis quand même retrouvé face à des complications. Notamment des latences dues à ma gestion du background qui devait afficher de façon aléatoire des éléments graphiques. Mais aussi par ma très mauvaise gestion des ennemis qui arrivaient sans cesse depuis la droite pour s’en aller vers la gauche, c’est-à-dire en dehors de l’écran. Hors de l’écran, mais pas disparus de la mémoire consommée ! Après quelques minutes de jeu, la chute des FPS était inévitable !
Pause ad vitam
Je décidais donc de mettre en pause ce projet et me consacrer à autre chose. Malheureusement, entre temps, la fin du support de Construct 2 fût annoncée et le passage à Construct 3 s’accompagnait de la mise en place d’un abonnement mensuel. C’était la fin indiquée de mon projet.
Je pourrais reprendre mon idée et la porter sur HaxeFlixel ou Godot, mais je crois qu’après 13 ans de mise en attente, le plus simple est donc de tourner la page. Bien que techniquement, je n’aurais pas appris tant de chose que ça, j’en tire la leçon que bien choisir son moteur est important, et plus que tout bien définir son projet et ses objectifs. Il n’en reste pas moins que tout n’est pas à enterrer, et c’est pour cela que je mets à disposition les assets graphiques que j’avais créés.
Peut-être que ça servira à quelqu’un d’autre !
Vous pouvez aussi retrouver sur itch.io la démo jouable de la dernière build de ce projet :
Insert coins!
C’est donc après cette pause de 14 ans que s’achève ce projet. Quand bien même c’est encore un autre projet non fini, cela devient aussi ma première démo de jeu publiée. Donc un vrai plus !
La tête un tout petit peu plus libre, on va pouvoir vider la corbeille en cette fin d’année et continuer de se recentrer sur les projets déjà bien avancés !
À bientôt.