Curiosity: How do bugs get prioritized for fixing?

To be SUPER clear - this is not a critique / complain / anything like that - just curious how an open source project like this works.

There are a couple of bugs right now that are just killing me - specifically the weather bug that lights you up at night and the rapid consumption of wood, I think as a result of the 1s move.

Short of relearning C++ and learning the CDDA code, which is sadly not going to happen soon, how do I influence the bug fixing priority? or is it just a zen-thing where it just happens?

1 Like

There is no system, every developer decides for him- or herself what to work on and everyone has his or her own priorities. Posting a usefull bugreport on github helps obviously.

1 Like

Projects are working basically the same way: all issues are being triaged and assigned some priority, then higher priority issues (e.g. crashes, issues preventing compilation, etc) are usually being fixed quicker. There are no SLA for any of the priorities, nobody owes anything to other people and everything is done voluntarily. Usually we do not even apply issues with priority tags. Nevertheless, major issues are resolved pretty quickly as “developers” are also “users” of the software and they are interested in getting things working.

Also there are long-term goals for next stable release ( and any outstanding bugs are being fixed before stable release (or moved to backlog for next stable version).

There are multiple ways you can assist with bugs in the project. The best thing you can do is fix bugs by yourself. You can report new bugs - You can confirm bugs and provide reproduce steps with savegame for unconfirmed issues ("(S1+-+Need+confirmation)").

You should also know that you are not obliged to use bleeding edge experimental version. If you are annoyed by bugs, just use stable version or revert to older experimental version (you can find binaries here -

1 Like