Mission Editor – ArmA: Armed Assault Talk
Jump to navigation
Jump to search
m (seperating the article, removed answerMe tag.) |
m (Talk:ArmA: Mission Editor - User Interface moved to Talk:ArmA: Mission Editor: it's about more than just the UI) |
(No difference)
| |
Revision as of 02:54, 2 May 2007
Could anyone with the knowledge please help confirm or add to the following parts:
- Trigger - Effects - Environment : Don't know how this effects normal environmental sounds, or why you'd ever want to use it.
- Waypoint - Effects - Environment : as above
- Waypoint - Effects - Trigger : Couldn't get this to do anything at all.
- A trigger is deactivated as soon as the condition is false again. --raedor 02:31, 29 March 2007 (CEST)
- That's what I thought, but it seems only repeatable triggers can deactivate, except for Radio type triggers which never execute the on deactivation code. Know of any other exceptions? --Ceeeb 03:41, 29 March 2007 (CEST)
I put a bit more information about Triggers (esp. the new seized by... type) to this page and also fixed time out description:
Triggers
--Maruk 14:56, 17 April 2007 (CEST)
Paragraphs
I think this page is too long. Instead of trying to describe everything, it should link to the pages describing individual features. This way we could also avoid duplicate information.
Example: ArmA: Mission Editor - User Interface#Waypoints Mode (F4) - part about "Guard" should most likely link to Waypoint:Guard. --Suma 16:27, 17 April 2007 (CEST)
- The article did get a bit out of hand, going well beyond the scope of the title. However, I'm not really sure how to break it up while keeping the information easily accessible to the wiki illiterate (including myself). --Ceeeb 04:06, 18 April 2007 (CEST)