@M:C team:
Hi guys,
I know I am giving advices without having been asked.
But currently your development seems quite chaotic too people outside your team and sometimes even your team members seem to not know what is currently going on,
where to get the current sources or what to test.
1) You need to have one
"Single Point of Truth" where
team members will always find the current revision to work on.
(Keep it simple for
less experienced modders.)
Especially if your
own team members and partners are confused, you should start to worry.
In
RaR this "Single Point of Truth" is our
SVN.
Thus there is never any confusion, where to get the current (internal) version to work on or to test.
2) When working in a bigger team you will need to establish some
project structures:
Planing, Work Organisation, Quality Control, ...
Especially if several modders are working on DLL.
Otherwise you will get problems some day.
To be honest, I see almost nothing of that here. It seems like you all just mod what you like and in the end just throw together what you just did.
(But maybe I simply don't know what you are doing internally.)
3) Throwing almost
untested internal revisions at community and then have
masses of bugfix patches afterwards is a
very bad idea.
Most of community does not want to be your testers. They want to be players that enjoy stable and balanced releases.
I have seen lots of great games and mods totally ruining their (potentially much bigger) communities with publishing behaviours like this.
Also, only very very few people from community will be willing to regularly check for bugfix patches they need to install.
(Most of them won't know at which bugfix patch they currently are a few days later.)
When you will get bug reports, you will have
big problems analyzing because people won't know the exact revision.
------------
See, you guys do have skills and you do have very interesting ideas.
But from the things I read here,
1. You do not seem to work like a real (organized, structured and efficient) team yet. (Efficiency and Quality)
2. Your strategy of publishing almost untested revisions / not having strong quality control is quite problematic. (User Satisfaction and Analyzing Bugs)
Maybe you should seriously rethink the way you are organized.
------------
So again, sorry for getting involved without being asked.
(But I do wish only the best for this modding community.)