The motive for this access would be to improve the game engine in general where possible and solve the bugs IV don't have the time or distributed hardware to solve, but more specifically, to vastly increse the modibility of the engine (as this was something it was never desigend for) in the form of additional scripting accessbility (short term) and unit/building behavoir modification (long term).
Firstly, there is no set in stone mechanism for the way the code might be released;
- - An Uplink style Dev CD licence - pay your money, get a copy of the sourcecode
- Privately licencing the code for a period to a specific small group of individuals
- Privately licencing the code for a period to a specific individual
- Source code never released to anyone, suggeests taken by inhouse dev and worked forwards
As a small number of you know, I have contacted IV on a small number of occasions asking if they would be interested in any of the above choices at this time or in the near future. All of the correspondance has been between me and Mark Morris, and as the discussion has concluded as of late, I've asked (and been granted) permission to post about exactly what the deal is, just so people know.
Now, here is a semi official statement on the matter:
The staff at Introversion definately do not feel they are, or will be, in a position to support this sort of project at this time, or any time before the release of Multiwinia.
This position may change as Multiwinia comes very close to going gold, due to my lack of solid details on the precise motivation for this. This is my perception of IV's stance on the issue, and it may be inaccurate, but it is to the best of my knowledge correct.
Some further details (for example, some of the answer to the question "why?");
- - I have no more information than anyone else when multiwinia will be ready. This could be months or years.
- Icepick (obviosuly) isn't currently working on his moddable fork of the code, and hasn't been for well over a year.
- Part of their motivation may be gleened from the following statement made by Mark;
- "It'll be much better for us to provide decent mod support for both Darwinia and Multiwinia and I want you guys to get your hands on all that new content - just be patient!"
- So far as comments have made apparent, no one is currently working on movng the scripting and behavior changes in 1.5.x over to nix and mac. This was probably apparent to everyone by now anyway. IV seem focused on multiwinia, and the 1.5x was gimmicked towards the vista release anyway. This is however conjecture on my part
- Duration of time needed to perform minor and major engine overhauls isn't a factor in their position
- They seem to be (or at least Mark is) positive and keen on the idea of the project, although they haven't confirmed that this is the path they would like to take (eg they may do the majority of mod support for MW themselves and port it backwards). The original comment from Mark I received read as follows:
- "Thanks for your comments and thoughts on the issue. I actually agree with the core of your argument. It is so important to provide good mod support, as it enables the games to grow in a completely new direction with the next generation of fans adding new material and allowing the game to morph into directions that we had never previously considered. The problems generally occur toward the end of a project when we are working so hard to get the game out the door, that we tend to break a lot of the principles behind the game and thus make the release of quality modding systems more complicated - perhaps that is no excuse.
The reason that we are uncertain about kicking off this project prior to Multiwinia is really a technical one. The Darwinia and Multiwinia code base are now incredibly deeply intwined. If we were to make the Darwinia code available, it would come with the multiwinia code base and an early leak of that could be disastrous for us! In addition it would be difficult for you to produce a mod system that would still work once Multiwinia was out there. It would be far better to start the project when the Multinwinia code base was stable so we could ensure good support for Multiwinia too."
A final note; This is not really a discussion and I don't want to see people particularly trying to argue for or against their motivations, or if they're counterproductive or invalid or are based on a flawed notion of the project's objectives etc. This really is all about information, information I think everyone who might want to know should know
Plus I don't know how many people even care any more.