Ok, synopsis... not good.
There is a lot of good, but a lot of extremely bad decisions.
First off. 15 minute game, this is my ENTIRE infolog:
[f=0000000] [] Error: Joystick 0 not found
[f=0000000] [] Warning: AI Interface property 'supportsLookup' could not be found.
[f=0000000] [] Warning: AI Interface property 'supportsLookup' could not be found.
[f=0000000] [] Error: [LoadFeaturesFromMap] unknown map feature type ""
[f=0000000] [Sound] Warning: Unable to open audio file: FailedCommand
[f=0000000] [Sound] Warning: CSound::GetSoundId: could not find sound: FailedCommand
I cannot troubleshoot with an infolog like that. Infolog should report EVERYTHING! I have no idea why in the world you would castrate the 1 and almost only troubleshooting tool we have.
---
Loading screen... Yeah sure, it looks all fine and good. Now change it back. I did loadscreens specifically for the previous method. So did many other projects. Why you decided that changing it was a good idea I will never know, but at the very least you should have A: asked us, B: given the option to revert it. Seriously, is a progress bar so damn difficult? Don't display any text, just have a progress bar that progresses a notch further at every loading step. It's not that hard. I should not be the only one capable of suggesting this.
Springsettings was not in my portable that I downloaded. Is that an oversight?
Game speed changes and viewradius changes no longer report in the chat. This is bad on so many levels. This also goes back to infolog reporting.
Ogg soundstream is broken again. Seriously guys, it's not freaking funny. Please fix the playing of ogg files. Any halfway crappy windows vb app can play an mp3 file without sucking. Why is a big production like spring so bad at it?
You have NO BUSINESS RELEASING this in it's current state. These are gigantic breaking bugs. We don't need another round of 7 .x releases because it wasn't done right the first time.
Why has no one else mentioned this stuff? Am I honestly the only one who bothered to look?