Give me proof that it's not a bug in AFKMud and
not a form of user error -- of course, to do that, we'd need more information from Apoc. But in the meantime, you don't really have any evidence. If there were serious bugs in the distribution, a whole bunch of people would have noticed in a whole bunch of places, and not just one relatively small program in a relatively small portion of the very large space of open source projects. In fact, for that reason, there is some plausibility that this is in fact a bug in AFKMud, but not having looked at the source I'm not going to make that claim at the moment. Not being able to reproduce the error makes it hard to debug, obviously, for both of us.
I'm not sure what you're implying when you say that you're paying attention to output. You're jumping to very strong conclusions based on rather partial information. You have no idea what else went on in between compilation and running the program.
Even assuming for the sake of the argument that Mint is in fact busted, that's a very far cry
from saying that Debian and Ubuntu are also busted. Due to plain empirical evidence, they are not.
If your claim is now that Mint is busted, I will still ask for proof, but that is a very different claim than what was originally being made.
Anyhow, this has been beaten to death enough, so I will say no more for now and eagerly await empirical evidence on this matter one way or the other.