Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
For that matter, by in-house I meant that they didn't build the engine with purpose of marketing it, the way Unreal or Cryengine are. They, if I'm remembering correctly, built it as they went when making mount and blade. I didn't mean to imply that you wouldn't be able to get permissions to use it for your own game. Although, I wouldn't want to try to make my own game in that engine, as it's a little heavy on the coding front, enough so that I would actually rather just make my own engine and thus not have the restraints and limitations of the mount nad blade engine.
It uses a pretty heavily modified version of the warband engine.
How it gonna perform in the full game isnt certain but since taleworlds did the changes, i guess it gonna be pretty good.