安装 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(越南语)
Українська(乌克兰语)
报告翻译问题




The multisize behaviour is what allows objects to be "dragged" out to different sizes.
In the "map" you define the max size version of the object, always start with that and set the minSize in the multisize behaviour to the same as the maxSize. This makes it a fixed size object.
Once this is working as intended, you can define how the object shrinks at smaller sizes.
So for example, first set the minSize just 1 less than the maxSize.
removeColumn tells it which column of your "map" to remove as the object shrinks in the x direction.
This is relative to the "o" which is the "origin" of your map coordinate system.
For complex objects you will want to use removeColumns which takes a series of numbers to remove different columns each time. Like: 3,7,4,2.
Look at and try modding some examples from the base game to get a feel for how it works. Hope that helps. :]