安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
7 
此主题已被锁定 
举报此帖
Well, this progress report also hilighted the glaring problems with code bloat that can occur if I continued down this path without better tools for modding. So I had to stop and take a very good look at the part of the mod that I can continue with and not need to worry about code-bloat becoming a problem down the line if I need to roll back some changes.
In it's non-modded state, Majesty will approach a state of the game engine slowing down as you play as your kingdom grows to having buildings and heroes in the near hundreds because of the code is has to execute for each entity that is present on the map. The mod will naturally make this occur sooner because the amount of code applied to each entity is increased directly with the amount of new code introduced, so until I can inhibit the amount of influence this can have. The item/equipment system is where this ends up being he most impactful to this problem in its current state. With better tools, I could cut the amount of code being executed by a vast amount, but as things are, the pool of items that can be used as equipment will have to be left here.