安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
I think I should just remove this
what are you guys talking about simfphys is still here!
I feel my best!
:
:
:
:
:
Here's how it's used in trailers reborn:
Addon adds callback to list of "FLEX" callbacks with id of "Trailers".
A table containing required data (connection positions and types + few optional ones) is added to car definition in simfphys vehicle definition list as a `FLEX { Trailers = { inPos = Vector(0,0,0) } }`
FLEX is just a simple script that will call trailers's callback with data of FLEX { Trailers }.
When car is spawn, "FLEX" loads car definition and checks if it has field named "FLEX".
If it does, it goes through every member checking if callback for it is registered, if it is, it runs it.
So...
vehicle is spawn -> load it's definition -> it has field named "FLEX" and it's a table (list of key and value pair) -> go through every member of this list -> check if there's a callback registered with same key -> call it.
list.Set("FLEX", "Test", function(entity, spawndata)
print(spawndata)
end)
-- somewhere in vehicle spawnlist
vehicle = {
-- ...
FLEX = {
Test = 12345
}
-- Members = {...}
}
ok!
Nice!