GTAMP

elypter wrote:comments when the line starts with ";"

elypter wrote:-sounds

elypter wrote:-point arrow at something + declare+switch off (doc page 18)

elypter wrote:-management of doors

TradeMark wrote:

elypter wrote:-sounds

Sound objects already are visible

TradeMark wrote:

elypter wrote:-point arrow at something + declare+switch off (doc page 18)

What does that mean? I didnt find anything about arrows on page 18...

DECLARE ARROW
This command ‘declares’ space for an arrow to be later used in the game. Currently, you really only need one arrow for each possible colour, but it’s possible to set up multiple arrows of the same colour. Current maximum is likely to be around 4 or 6, but this could be changed if necessary.

ARROW_DATA name

NOTE:
name: a unique namestring
POINT ARROW AT SOMETHING
Sets an existing arrow to point towards either a location, character, car or object. All items must be valid existing items. If target is an object, the arrow must be cancelled before object gets deleted.

POINT_ARROW_AT ( arrname, name )
POINT_ARROW_AT ( arrname, float x , float y , float z )

NOTE:
arrname: name of an arrow declared with an ARROW_DATA
name: name of either a car, character or object
xyz: must be a valid float (X,Y,Z) coordinate.

SWITCH OFF ARROW
Clears a previously created arrow

REMOVE_ARROW ( arrname )

NOTE:
arrname: name of an arrow declared with an ARROW_DATA

TradeMark wrote:

elypter wrote:-management of doors

Does this require modifying the map blocks?

DOOR DECLARE
Doors in GTA2 are one way - their primary use is on buildings for ‘garages’. They give the illusion of the player entering a building & dumping a car inside. They will usually be used in conjunction with a ‘PARK’ command to take the player inside & dump his/her car.

These may appear to be a little fiddly to set up properly, but they give you a lot of different power.. Doors must be declared & created at the top of your file outside any functions. At the moment, all doors are automatic & default to closed – barriers will come later.

Doors can either be single or double. If you select double, the game will automatically position another door to the ‘right’ of your coordinates, depending on the direction the door should face.
i.e. if facing top, it will generate one block to the right,
if facing bottom, it will generate one block to the left,
if facing right, it will generate one block to the bottom,
if facing left, it will generate one block to the top.

Double doors’ opening logic defaults to being over both blocks immediately in front of the two doors, instead of the single block in front that happens with single doors. You can now change this easily through the ‘check’ values – this is a float (XYZ) which is the centre of the range to check, plus a width & height giving the size of the area to check.

The “gr_id” is a single integer value telling the game what set of ‘graphics’ to use. This value is basically a reference to a DECLARE_DOOR_INFO. If you want this door to use the second door_info data, set this to 1, if you want the first,use 0.

Open_type is the rule for opening this door. See bottom of document for list. Basically, at the moment you can order doors to open for players, for any car, for particular cars you’ve created, for a particular model of car. If you want the door to open for a particular car, you need to give its name at the end of the line, see ‘somename’. If you want the door to open for a particular model, you need to give this as ‘somename’.

Close_type is the rule for closing the door. This is a little more straightforward. If you give the door a ‘close never’ type, it will stay permanently open & will let anything go through. All other types will only let the ‘type’ that opened it through, e.g the player, a particular car. Another common close type will be ‘delayed’ which waits a certain number of game cycles & then attempts to close the door.

One word of warning: at the moment, the game will not close the door while whatever opens the door is still standing on the opening trigger in front of the door…

DOOR_DATA name = style ( int X , int Y , int Z ) ( float check X , check Y , check Z , check width ,
check height ) face gr_id open_type close_type delay flip reverse
DOOR_DATA name = style ( int X , int Y , int Z ) ( float check X , check Y , check Z , check width ,
check height ) face gr_id open_type close_type delay flip reverse somename
DOOR_DATA name = style ( int X , int Y , int Z ) ( float check X , check Y , check Z , check width ,
check height ) face gr_id open_type close_type delay flip reverse value

NOTE:
name: unique string giving a name for this door
style: either SINGLE or DOUBLE to tell game what style of door it is
XYZ: integer values giving the coordinates of the block to put the door ‘on’
Check XYZ: floats describing the ‘door check’ trigger opening position…
Check width/height: width & height of the new trigger position
Set these check values to 0.0 to make the game automatically generate a trigger covering the area ‘in front’ of the door. (same way as GTA did it).
Face: facetype is either TOP, BOTTOM, LEFT, RIGHT detailing which face to
physically place the door on.
gr_id: an integer detailing which ‘DOOR_INFO’ to use. 0 is the first valid door_info!
open_type: An open_type string from the bottom of the document
close_type: Again, a close_type string from the bottom of the document
delay: Integer detailing the number of cycles to wait. 255 is the maximum wait.
flip: String which is either “FLIP_RIGHT” or “NOT_FLIPPED”
If flipright, the righthand door has its graphic flipped.
somename: Usually the name of a car or carmodel – only used with specific open_types
value: integer value not currently used – you do not need to worry about putting in
any sort of value for it.
Reverse: extra flag detailing “backwards door” – use this for the ‘fudged’ doors where you effectively have two doors on the one block. SEE ME!
Should be either REVERSED or NOT_REVERSED

BenMillard wrote:Good list. Do you include a placeholder image for tunnel_blocker? Something like the UK "ungated level crossing" sign might be nice.

TradeMark wrote: elypter, i dont know how should i display those arrows, they appear only at the player? while i cant really display a player in the editor, only startpositions

POINT_ARROW_AT ( arrname, float x , float y , float z )

• RADIO_STATIONs
• DESTRUCTORs
• Save point
• Start positions of the trains
• Some visual markers (or mouse-over?) for cars that are bulletproof, fireproof, no_collision, have a car alarm or emergency lights, etc.

Lantyz wrote:RADIO_STATIONs

Lantyz wrote:DESTRUCTORs

Lantyz wrote:Save point

Lantyz wrote:Start positions of the trains

Lantyz wrote:Some visual markers (or mouse-over?) for cars that are bulletproof, fireproof, no_collision, have a car alarm or emergency lights, etc.

TradeMark wrote:

Lantyz wrote:Save point

Command name please!

//[...]
FORWARD savethegame:
THREAD_TRIGGER trigger_savethegame = THREAD_WAIT_FOR_CHAR_IN_AREA ( player , X.x , Y.y , Z.z , Float:X , Float:Y , savethegame: )

savethegame:
PERFORM_SAVE_GAME ( trigger_savethegame , X.x , Y.y , Z.z , Float:X , Float:Y )
RETURN
//[...]

BenMillard wrote:Sound icon looks great, I guess that's a PYLON at the back? Displaying the type of sound on mouseover could be a neat enhancement.

BenMillard wrote:TOWER objects seem to be 2 blocks high. If you use (x,y,255.0) then I think the bottom part ends up underground, because they blocked my subway trains on MultiSlayer City by default.