Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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 = {...}
}