This isn't a framework, this is just a bunch of glue code that I used over the last few years. But now feels like I've a more solid parts that I can share some of the details with other folks. And with that I can discuss about it.

So this the first part, I've more in the oven cooking. But this is is about what makes a good logger (at least for me) to have in the Godot projects.

Keep in mind, all code is AGPL, so if you copy this code your codebase will be AGPL.

All feedback is welcomed.

no comments (yet)

sorted by: hot top controversial new old
there doesn't seem to be anything here
1 comment in c/godot@programming.dev view that post
[–] 1 point 2 weeks ago

For a prototype Logger, the thing that saves me most is cheap context tags (scene + system) on every line so you can grep one subsystem after you abandon half the experiment.

Second: a "debug only" channel that is a no-op in export builds — keeps the habit of logging freely without shipping noise.

Curious how you handle log volume when a prototype runs for weeks and the file grows — rotate, ring buffer, or just wipe between sessions?

  • source