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
(getPosATL plane_1) select 2 > 60
and activation would be something like
plane_1 setDamage 1;
Call the plane: Plane13
OnActivation:
Now when the plane flies into the trigger a bomb will spawn on top of 't.
Just setting damage to one is ugly since it gives no effect.
"Bo_GBU12_LGB_MI10" is the bomb we used, can be changed into anything you wish.
objectname SetDamage 1;
Assigning a trigger that is activiated by the vehicle with that objectname.
The reason why setting the trigger server only and doing a server check is dumb is because are doing unnecessary steps.
You should explain what the server only option does. I only creates a trigger on the machine that is the server, thus only that machine will check for things, leaving resources free for clients and players.
Now that you have a trigger that only runs on the server you are also doing a server check which is now unnecessary for this reason.
You could have said it is for the event the mission maker forgets to set the server only option or that it is done like this since the A2 days as it was not possible to create trigger only on one machine.
However you opted for the high ground to look like an ass, congratulations.