I am not sugguesting working on the same source files/codes, but any help with the project on itself is welcome. I've tried to include others into it with my repair-ai thread, but it only fired up a discussion about what to do first, and who's repair-order was best.
I am not trying to get people to compete against each other, but i am working on a project that will help the community making better and easier missions.
I've worked a couple of weeks on IUnit. I know most of the credit for finding out how it all works goes to hooman, but i was the one to make it into a nice little useable class, without even spilling 1 byte of source code onto the "noob" coder. Two reasons for that: [ol type=\'1\'][li]the code is kinda messy, and hacks into outpost2 pretty bad;[/li][li]for a coding "noob" it might not be easy to understans how it works. This way i save myself the explanations and the source is easily modified to screw up outpost 2 to the point it won't run the missions anymore that use it.[/li][/ol]Same goes for the events-code, that i haven't released yet. Again, no source will be given, only a useable library, that can be compiled into your mission.
This Groups projects is probably a lot more work, and consists of more source files, that could be done by different individuals. The final library will still have to be approved (and modified if necessary), and linked by 1 person.
I haven't started yet; i first want to release Renegades 1.0 B)