3/20/09

CRYSIS WARS SDK F.A.Q.

Introduction
We've noticed many questions popping up throughout the community and we've compiled a short FAQ in order to try and answer some of the most common. Please read through the entire post before asking additional questions as repeated questions will just receive a copy and paste response.


quote:
Why is the SDK only for Crysis Wars?
We did this in order to keep the modding community focused on one title, as well as to allow for both singleplayer and multiplayer mods for this engine version. Adding singleplayer support to Wars is far more convenient than adding multiplayer support for Warhead. This also means that the community won't constantly be developing levels and mods for two titles, which is bound to cause confusion in many aspects of development.

Will maps or mods compiled in Crysis Wars be compatible with Crysis (and vice versa)?
By default yes, however there are a few aspects of the project that you must change before it will be playable on both titles. Any code in your mod must be recompiled for both titles using their respective SDK's and released separately. Also, if you using any models in your mod that are specific to Crysis or Crysis Wars, make sure they are included so that the users of the other game will be able to use them. Our suggestion would be to develop on the platform you plan to release on to keep it as simple as possible. This support is strictly for current projects/maps that would like to release on both Crysis Wars and Crysis.

Will the Crysis Wars SDK and Editor function with Crysis?
Theoretically yes. However we thoroughly recommend you use the game's respective editors for the levels as unforeseen consequences may occur through the use of the wrong editor that could cause many different issues with your mod or map. We will not be able to support projects that are using the updated version of the editor with Crysis.

Will the Crysis Wars SDK and Editor function with Crysis Warhead?
No these are not compatible, as the Crysis Warhead code base is different to that of Wars and consequently neither the editor nor SDK will function with this version.

Is it possible to have the editor and SDK installed for Crysis and the new SDK and editor for Crysis Wars at the same time?
Yes it is; both SDKs and Editors were built for different games and run off separate installations, so both SDKs and Editors will run as expected separately from one another.

Due to the re-enabled AI in Wars, is AI and co-op in multiplayer now possible?
AI in Wars doesn't mean that we've added AI to the multiplayer game; we have simply enabled it in the engine so that when Wars is played in singleplayer the AI will function as normal. This means that although AI will be available to use in Wars, multiplayer support for it is not included.

Is there an auto-downloader for mods included in Patch 4 for Crysis Wars?
No there isn't, however custom levels can still be downloaded with the auto-downloader.

Will we be able to download the Warhead .cry files?
Unfortunately we cannot provide these there is, however, we have a good reason for this. If users without Crysis Warhead were to obtain the .cry files, they'd be able to play the Warhead levels inside Crysis and Sandbox2 (of course with limited assets). This is to some extent piracy, so unfortunately we will not be providing editable versions of the levels for Warhead.

Will Crysis Wars have the singleplayer menu options?
The singleplayer menu has not been added to Crysis Wars as we want to avoid the confusion of it being branded a singleplayer title. As in Crysis, to play singleplayer maps on their own you must use the relevant map console command to load them in-game.


Conclusion
We hope this answers the more important questions about the Mod SDK and Editor, if you do have additional questions that aren't covered by this FAQ or the full notes for the editor then please feel free to ask them here, however, as stated before, questions that have already been covered here will just receive a copy and paste response, so please try and be constructive.

No comments: