Topic: End of Development for First Strike
Due to the recent confirmation of a major stability issue with BF2142, the work on a stand alone version has stopped. The issue is that ever since EA dropped support and the master account server, the game crashes in singleplayer or coop shortly after a map restart. We just recently verified that it is a game engine bug. There have been reports in the past of strange crashes in First Strike singleplayer, but only when playing without an internet connection. Without the master account server, the crashes happen consistently. The means that the only way to play First Strike singleplayer or coop crash free is to restart the game before switching maps.
The bug is kit related. The kits are fine the first time the game is started but after a map change, that is when the kit will start to have issues. the map will load up, but as soon as the bots see each other and start to fight is when the crash happens. What we noticed is that most of the time the kits will appear fine, but every once in a while a weapon will be missing from a kit or a bot will be running around with no weapon. It appears that every time the map is switched at least one kit for one player or bot is bugged, which results in a crash.
I believe this is a an offline account bug. This was never a problem online. Multiplayer would probably still work, but considering that BF2142 is not available from EA and all support is dropped, there is no point in pursuing development.
I will clean up the work in progress of the First Strike BF2142 Mod beta version and release it as is. It's sad to see this come to and end, but now I can refocus on work on Star Wars Battlecry for the UE4 engine.