Here comes a wall of text, but there are a few things to explain.
In fact, there was never an official version for this console. In the past, a developer who had terrible behavior and didn't know how to work in a team – and you can see that from the comments he made at the time, offending both the official team's work and the people themselves – made a version for the Xbox 360, claiming he had "improved" the engine. Thank goodness, that person is no longer part of the team.
The case of the Dreamcast port is almost the same, although there was an official version for a long time. However, it was discontinued due to several factors, such as the extra work involved in maintaining such an old system, the system's low RAM, among other things.
It's fine for people to be attached to old consoles and want to keep the engine updated for their system – as long as they maintain it and address questions (although I personally don't think that's a good idea because people will always end up asking about it here in the official community and, in a way, demanding support for something that is no longer supported).
The big problem with the Dreamcast version is that the person you mentioned
decided to attack both the work of the engine developers and the developers themselves, claiming that they didn't know how to program properly, among other things, just like the
Xbox 360 version developer did in the past.
No matter how good the person is, it's not an acceptable attitude expected of an adult.
But people, instead of building bridges, prefer to burn them.
I can't speak on behalf of the team because I'm no longer part of it officially, although I have a very close relationship with the developers. But there is no support for versions that are not official. Especially when there are behaviors like those mentioned above.
This community is quite friendly – one of the friendliest I've ever been a part of. The developers are very attentive and always willing to help, especially the lead dev
@DCurrent who does everything, including paying out of his own pocket, to keep everything running.
But that doesn't mean they have to accept any kind of behavior just because someone wants to help with development. There are rules, procedures, a whole logic to follow to maintain the project's scalability in the future. Unfortunately, there's a lot of legacy code that's a logical mess to solve, and if you try to fix one thing, you break two in the process.
Therefore, with version 4.0, it was decided that the rule of maintaining backward compatibility at all costs should be dropped – a wise decision.
Don't take anything I say personally; it's not a criticism of you. It just bothers me when something is publicly alleged, but, as I know what goes on behind the scenes, I know it wasn't quite like that.
