mvBarracuda sent us a press release regarding the development of FIFE, an open-source engine for isometric cRPGs resembling Fallout as closely as possible - but with many tweaks and features added.<blockquote>Now that three months since our first public release have passed, it is time to bring you update on the current status of FIFE. As lacking transparency was surely one of the biggest problems of IanOut, our aim is to be as honest as possible about the progress we made but also about the problems we've encountered.
So we start with some bad news first: our old lead coder Chris has stepped down from his position as he felt burned out and wants to focus on real-life activities now. He stated himself that this might not be a final decision but however he won't return for the next months.
We recognized that heavily relying on a single person is no good long-term solution so we decided to replace the old lead coder position with several "engine core coders". The idea is to split up the pressure and the responsibility to three / four core coders instead of a single programmer. We were able to fill one is these engine coder positions with Phoku. He does a great job improving the engine, however we don't want to end up with the same situation as before. So we're still searching for advanced C++ coders who are interested in taking the challenge of participating in a large-scale Fallout project.
This project is in development for seven months so interested coders shouldn't be afraid that it would be as complicated as starting something from scratch. Our project organization structure encompasses bi-weekly IRC meetings, a development wiki, a public Subversion sourcecode repository and a quite active mailing list, so we are just lacking core developers to use this basis
If you're interested in FIFE we suggest to take a look at our developer guide. It contains all necessary information about the project e.g. how to get the sourcecode, how to compile FIFE and how to contact the development team:
http://wiki.fifengine.de/index.php?title=Getting_started
However there are also of course some good news to report. Our coder Skybound worked on the GUI code of FIFE and was able to recreate a kind of Fallout 2 with FIFE. Here are two example screenshots:
<center>
</center>
And we are happy to welcome Cheesesucker to the team. He will be working on our upcoming editor suite for FIFE: FIFEdit. Here is a work in progress screenshot from the new zoom feature that allows you to view complete Fallout maps in a single window:
<center>
</center>
With the current lack of engine core developers we cannot announce a release date for the next public FIFE release. Although you can always get the most recent SVN code and compile it yourself.
If we are not able to attract new coders we won't let our baby die
It will just take some serious amount of time till the next release. So we would really appreciate any help in the coding department.</blockquote>
Link: http://www.fifengine.de
So we start with some bad news first: our old lead coder Chris has stepped down from his position as he felt burned out and wants to focus on real-life activities now. He stated himself that this might not be a final decision but however he won't return for the next months.
We recognized that heavily relying on a single person is no good long-term solution so we decided to replace the old lead coder position with several "engine core coders". The idea is to split up the pressure and the responsibility to three / four core coders instead of a single programmer. We were able to fill one is these engine coder positions with Phoku. He does a great job improving the engine, however we don't want to end up with the same situation as before. So we're still searching for advanced C++ coders who are interested in taking the challenge of participating in a large-scale Fallout project.
This project is in development for seven months so interested coders shouldn't be afraid that it would be as complicated as starting something from scratch. Our project organization structure encompasses bi-weekly IRC meetings, a development wiki, a public Subversion sourcecode repository and a quite active mailing list, so we are just lacking core developers to use this basis
If you're interested in FIFE we suggest to take a look at our developer guide. It contains all necessary information about the project e.g. how to get the sourcecode, how to compile FIFE and how to contact the development team:
http://wiki.fifengine.de/index.php?title=Getting_started
However there are also of course some good news to report. Our coder Skybound worked on the GUI code of FIFE and was able to recreate a kind of Fallout 2 with FIFE. Here are two example screenshots:
<center>
And we are happy to welcome Cheesesucker to the team. He will be working on our upcoming editor suite for FIFE: FIFEdit. Here is a work in progress screenshot from the new zoom feature that allows you to view complete Fallout maps in a single window:
<center>
With the current lack of engine core developers we cannot announce a release date for the next public FIFE release. Although you can always get the most recent SVN code and compile it yourself.
If we are not able to attract new coders we won't let our baby die
It will just take some serious amount of time till the next release. So we would really appreciate any help in the coding department.</blockquote>Link: http://www.fifengine.de
