- #FREECOL 0.10.7 CODE#
- #FREECOL 0.10.7 WINDOWS#
FreeCol 0.8.2 - released "fixes several bugs and includes new or updated translations for 36 languages"."Standalone servers are restarted automatically" after a win "fixes several bugs". FreeCol 0.8.1 was released on 21 February 2009.But the big thing is reportedly the ability to use XML to define gameplay mechanics.
#FREECOL 0.10.7 WINDOWS#
It too works fine on Windows Millennium Edition.įour new nations new sound effects and terrain graphics units slide (somewhat jerkily) instead of jumping. FreeCol 0.8.0 - Released 15 January 2009 (after a few months of alpha versions).0.7.4 plays well on Windows Millennium Edition operating system, which cannot be said of every modern game release. Map editor trade and negotiations with other Europeans. 0.6.1 two weeks later fixed a few things. FreeCol 0.6.0 - Released 16 April 2007 - lots of new features.0.5.1 and 0.5.2 made some fixes later in 2006, and 0.5.3 released in December became SourceForge's "Project of the Month" in February 2007. More features such as tax, LCRs, and war of independence. Computer players and royal expeditionary force get AI, allowing single-player game. FreeCol 0.4.0 - Released 23 June 2005 compatible with J2SE 5.0.Many new features, not least the ability to play and win (multiplayer).
#FREECOL 0.10.7 CODE#
FreeCol 0.3.0 - Released 30 September 2004 code redesigned to make development easier. FreeCol 0.2.0 - Released 26 March 2003 all in Java. FreeCol 0.1.0 - Released 2 January 2003 "Server written in C++ and the client in Java". It devotes a web page to nearly every release, linking to them on its Releases page. A saved game in the failed state will not be enough.FreeCol has had a score of released numbered versions since the project started in 2002. If you wish to report one of these bugs, we will need a saved game, and instructions on what to do to make the problem happen. These tend to depend strongly on what happened just before. These problems have caused crashes, all reported cases of which are fixed, but we are not that confident there are no more.įinally, there are still various hard to reproduce problems where the active unit is not correctly displayed. The map has been fixed so new games are safe. There are also lurking problems with old saved games using the America_large map, due to some lake tiles with null regions and single isolated river tiles. Such reports will be closed with a `Wont Fix' status. Unfortunately, a fully backward compatible fix would be quite complex and thus likely to cause worse problems and delay this release, so please do not report this as a bug. New games should not have this problem, but existing saved games are vulnerable. This can lead to very enjoyable levels of bell production. There were also several other bugs fixed, including one that can result in certain bonuses (e.g. These are coding bugs and belong on the bug tracker. Raise translation issues there, except in cases where you see messages containing percent-delimited words %like% %this%. FreeCol is translated by the volunteers at. Note also, we do not handle translation directly. Too many bug reports get stalled, sometimes indefinitely, because of a missing log file (which is almost always needed in the case of a crash or hang) or missing saved game (almost always needed to replay some sort of strange behaviour). Very few bugs are easily reproducible from just a textural description. When reporting please try think about what the developers would need to reproduce the bug. Bug reports remain crucial to improving FreeCol. Two other pre-0.10.6 bug reports were also fixed. Since FreeCol 0.10.6 was released there have been 18 new bug reports, of which 8 are fixed in 0.10.7, one (roads are sometimes ignored) is partially fixed, 4 were invalid, 3 can not be reproduced or are otherwise awaiting clarification, one was a duplicate and one was a content contribution. The only newįeature present is some improvements to the graphics. This is a bug fix release to correct some serious gameplay problems in 0.10.6.
0 kommentar(er)
