The time for "Action" has come! (Please do NOT post questions in this thread.)

[Nesquik]

I try to make a AI chopper hover


I try :
<chopperdriverName> action ["STR_ACTION_HOVER"],
<chopperName> action ["STR_ACTION_HOVER"],
<chopperName> action ["HOVER"],
<chopperdriverName> action ["HOVER"],

on a waypoint or in init field
And it don't work  :'(

help me

[Zombie]

I tried the action "heal" and my guys makes the moves like a medic working, not as if he is being healed.  What's the action for getting healed?

[McFly]

I parsed the Flashpoint.exe and got a list of the available actions in the engine...

Code: [Select]

USE MAGAZINE
DEACTIVATE MINE
TAKE MINE
HANDGUN OFF
HANDGUN ON
USER TYPE
DROP MAGAZINE
DROP WEAPON
SCUD START
SCUD LAUNCH
SALUTE
FLAPS UP
FLAPS DOWN
LAND GEAR
FIRE PUT DOWN
FIRE INFLAME
LADDEROFF
LADDERONUP
LADDERONDOWN
LADDERDOWN
LADDERUP
STROKEGUN
STROKEFIST
AUTOHOVER
NVGOGGLES
MANUALFIRE
DEACTIVATE
SETTIMER
TOUCHOFF
HIDEBODY
MOVETOCARGO
MOVETOCOMMANDER
MOVETOGUNNER
MOVETODRIVER
EJECT
CANCEL LAND
LAND
SITDOWN
WEAPONONBACK
WEAPONINHAND
TURNOUT
TURNIN
RETURN FLAG
TAKE FLAG
TAKE MAGAZINE
TAKE WEAPON
LOAD MAGAZINE
USE WEAPON
SWITCH WEAPON
ENGINE OFF
ENGINE ON
LIGHT OFF
LIGHT ON
GETIN CARGO
GETIN GUNNER
GETIN DRIVER
GETIN COMMANDER

I'll try to interpret the parameters later.  There might be other actions that I missed - they're near the bottom and in all caps.

[Doolittle]

NICE work McFly!

I wonder how you get the argument for "return flag"...

Doolittle

[Blanco]

Is there somebody here who knows how to use :

STR_ACTION_TAKEOFF_GOGGLES                                
Take off NV goggles
STR_ACTION_TAKEON_GOGGLES                                
Take on NV goggles

it's in the off. comref...

[McFly]

The "STR_ACTION" variables are string names - they don't actually do anything, they simply tell the engine what text to display in the action dialogue (which it looks up in \bin\stringtable.csv).  I don't know why the unofficial OFP reference refers to them that way as it's clearly confusing.

The action you want is thus:

unitname action ["nvgoggles"];

That will cause the unit to equip goggles if he has them, and also to take them off if he already has them equiped.  In other words, it acts like a toggle switch.

[Mr. S.A.S]

Just a little action I learned in a tutorial:

UnitName action["put","pipebomb"]
Makes a unit place a satchel charge (if he has one, obviously).

UnitName action"touchoff" (I think)
Makes the unit detonate any satchel charges he has placed.

It may not be much, but every little helps, right?

[Killswitch]

A new(?) finding on "SETTIMER" and a recap on the use of satchels as presented my Mr SAS just above:

To have a unit place a satchel that its carrying

Code: [Select]

dude fire ["put", "pipebomb"]To have that unit set the timer to 30 secs (or add another 30 secs to an already set time)

Code: [Select]

dude action ["settimer"]

// or, alternatively

dude action ["settimer",dude,0,0,"pipebomb"]To repeat from earlier posts, to have him blow the satchel(s)

Code: [Select]

dude action ["touchoff"]
Note the use of fire instead of action to actually place the satchels. I couln't make it happen using action.

[General Barron]

OMG! Great work McFly! Now a nicely formatted "action reference" needs to be made, where all the actions revealed in this thread are filled in with appropriate descriptions/parameters/other info, and then with blanks for the actions that still aren't figured out yet. HTML would work well, methinks. Anyone wanna put this together? It would be greatly appreciated.

And as a tip to anyone trying to figure out actions:

the "action" command takes an array of 5 parameters. If you pass it 6 params, it will give you an error saying "6 given, 5 expected". So in the case of:

dude action ["settimer",dude,0,0,"pipebomb"]

The first param is the action, the next is the person doing the action, and then there are two placeholders, and then the last parameter is what to do the action on. If 5 params aren't needed, then only one can be given. Ex:

dude action ["touchoff"]

So I'm assuming that other actions that would have parameters (such as USE MAGAZINE) would look like the first example.

But if it takes 5 parameters, then shouldn't there be an action that needs all 5? I suspect there may be one action like the "USER TYPE" one, which would use all 5, and the rest use either 1 or two and the two placeholders.

[h-]

Didn't see this action here so thought I'd post it up...
Although you all must know this by now...  

To make chopper auto-hover:
heloName action ["HOVER",heloName]

And to cancel it:
heloName action ["HOVER_CANCEL",heloName]

[Blanco]

he, found some new ones :  

Action code must be put in the on activation field of a WAYPOINT (like the switchmove/playmove commands) or in a script.NOT in an init!

Make sure the unit has a handgun.
unit action ["handgun on"]
unit action ["handgun off"]

unit action ["weapononback"]
unit action ["weaponinhand"]

;unit must be in safe behaviour
unit action ["sitdown"]

Gets on his knees and grab something...looks like take weapon, I think I need argument to make it work
unit action ["USE WEAPON"]

Damn those action are hard to find...

[macguba]

Attached is a zipped Excel spreadsheet which is a quick and dirty first draft collating all the information in this thread.


There are still a lot of gaps ......[/b][/size]

[Planck]

Unfortunately, we don't all have Excel.....hehehehe  ;D


Planck

[macguba]

Text version herewith, though the layout is not too clever.    

[Planck]

Ta muchly macguba.  


Planck