Yes, It was essentially a port of another engine

sound3d wouldn't work with synthizer API changes, And even though if someone fixed it I recommend against using it because that thing is disgusting.

Since that's a fork, it's not the most up to date version anyways.

@126-129, yep, it was removed from github, see #132. Essentially, it was a pretty much unusable mess. I might rewrite it some day to not use such BGT style syntax and be more pythonic, but today will not be that day.

@134
I mean (1) you could maintain them and (2) part of why I can't justify maintaining them is that everyone had a year or so to adopt the library and no one did so.  Like sure, you can have predicted that I'd put them in maintenance mode all you want, but that's a self-fulfilling prophecy where everyone thinking like that stops progress being made.  Also I've both committed to reviewing PRs and to mentoring so if there's value in it for someone, then they can step up.  This is called open source, not Camlorn does an impossible amount of work and gets flack for saying that there's an impossible amount of work to be done and the thing that has to give is the thing no one is really using but here are instructions on how to help.  The core library is steadily proceeding and my average turnaround time on bugs is one week.

Additionally Python isn't busted, I've committed to making sure it's going to get critical fixes, and it will probably work for at least the next 10 years as it is without me touching it.  I'm not sure why everyone is equating me putting them in maintenance mode with it being broken.  Maintenance mode is a very well-defined term in the industry, it means that *maintenance* will happen.

What's there is more than what's in Pygame, last I checked.

I have yanked one project ever, and I only did so because it was completely broken and I couldn't get people to stop trying to get me to support it even after I said many times to many people that no I won't because it's completely broken.  That was also something like 8 years ago now--longer than 99% of this site has even been coding.

I don't really care if you do or don't use it.  But I would at least like you to criticize it for good reasons if you're going to come out and be all "I predicted this would happen" without prompting.  Maybe I' being oversensitive, but you saying what you're saying on what is I believe your project which (if I'm reading this correctly) you yanked from GitHub is just very meh to me.  Kind of the pot calling the kettle black.

I have said multiple times what maintenance mode means.  There is no excuse for that.  Ammo is targeting blind adults and is something I can and will push outside this community, otherwise I'd probably not bother honestly.  It's just...tiring.  And I think people need to come to understand that.  I've put multiple man-months and a bunch of my free time into my free projects that I don't get paid for, at least recognize that and don't be passive-aggressive about it if you're not going to help out.  Hell, I literally bought a new computer specifically to make Synthizer support Mac, that alone should be worth a lot of credit w.r.t. how seriously I take my code.  Maybe you need something that only bass has or something, but just say that instead.  "Synthizer doesn't work for me because..." is an actually useful statement--I may not do anything with it, but it at least is constructive and stuff.

@137 thanx for your hard work.
Just look at how many projects you actualy don't abandon, and how many you keep running and compare it to the people who has problems with what you do.

@134, says the one who brought down the regestration server of they're pade game 10 months after launch.