CM Development and the Eternal Loop

I want to preface this by saying I have genuine respect for the contributors and maintainers who put time into this game for free. This isn’t a “devs bad” post. But I’ve been watching CM’s development cycle long enough to notice a pattern

It goes like this:

  1. Contributor picks up ambitious project, new mechanic, rework, overhaul

  2. PR gets opened, looks promising, community gets excited

  3. Testmerge happens, feedback rolls in, some good, some bad

  4. PR gets pulled for “further work”

  5. Testmerge again a few months later

  6. Gets pulled again

  7. Sits in PR purgatory for 6-12 months

  8. Contributor moves on to a new project

  9. PR closed due to inactivity or contributor request

  10. Repeat forever

The graveyard of PRs that went through multiple testmerges, generated discussion, and then just quietly died is enormous. And the frustrating part isn’t that projects fail, that’s normal in open source development. The frustrating part is the cycle of hope. The community gives feedback, argues about balance, and then it just evaporates.

I don’t have a clean solution for this.

5 Likes

That is life. We just have to roll with the punches and or pick up where one Dev left off.

1 Like

Yeah that’s sadly how things go.

You should post some dead projects here - in hopes someone sees it and wants to continue them.

There’s a few I’ve seen die over the years which looked promising, but yeah I can’t remember them off the top of my head.

Here’s a few I want to come back:

There’s a lot more, but I can’t think of them off the top of my head sadly, and some didn’t make it to the PR stage.

Eh having been a longtime tg player who has kept up with the dev scene and has observed projects of similar size and ambition get developed and go through, it definitely makes me think the development bureaucracy here has some problems which should be addressed and solved


wyci

I mean I think it has a lot to do with the scale of CM’s projects, they’re usually much bigger in scope (the large ones that is). Also compare how many pull requests CM actually gets compared to TG, there’s 137 right now, it was at 180+ a few days ago. I could be wrong but CM maintainers have a lot more on their plate.

the bulk of our code standards/style is copypasted from tg’s. the only real difference is that we have specific approval requirements from sprite maintainers and map maintainers. sprite approval is necessary as we have a unique artstyle that is pretty uniform across most of our sprites - tg often suffers from codersprites and a mishmash of artstyles. mapping approval is also quite important with how small mapping changes can completely change the balance of a groundmap