(Ignoring level_vertex_id may cause spawned objects to fall through the ground.) Why 1, not level_vertex_id()? We checked and found not significant difference which level_vertex_id(), although in some cases a valid vertex is required without it an object might spawn somewhere other than planned. For example:Īnd so, to spawn, for instance, a blot under an actor's feet, we write:Īlife ( ):create ( "bolt", db.actor:position ( ), 1, db.actor:game_vertex_id ( ) ) Whereas level_vertex_id() is calculated for the level, game_vertex_id() is for the whole game, and is necessary to indicate which map to spawn the object on (I could not come up with a more sensible explanation).Ĭorrespondingly, to spawn an object on a different map, it is enough to set game_vertex in the fourth parameter. The next parameter is much more interesting game_vertex_id() is almost the same thing as level_vertex_id(), except that it is a global value! I do not really understand why most likely for precise positioning of objects.įor example, you can get the vertex nearest to an actor - db.actor:level_vertex_id().
All objects consist of polygons, each polygon contains vertices. Lets move from the simple to the complex. Position can be created with vector():set(x,y,z), where x, y, and z are coordinates of a point in the level in which we are spawning the object.įurther on it gets complicated and difficult for me to describe. I guess, position needs no explanation, except one nuance: height is Y, not Z. For instance: mil_killer_respawn_2 - spawns a killer sniper. There are also objects that move between online and offline modes these are NPCs, monsters, etc. For instance: "bolt", "med_kit" - are simple sections, simple objects. The first parameter - ltx section describing the object. There is a single script function responsible for spawning objects:Īlife ( ):create (section, position, levelvertex, gamevertex ) Strictly speaking, there are two: create and create_ammo, but the differences between them are minimal.
0 kommentar(er)
