|
|
@@ -67,33 +67,33 @@ In addition to collaborating through project branches, Defold allows you to shar
|
|
|
This is a list of all the available building blocks for creating apps and games. They are listed together with the icon used for the type of building block in the Defold editor.
|
|
|
|
|
|
Game object
|
|
|
-: {.image-left} See above for a description of game objects.
|
|
|
+: {.left} See above for a description of game objects.
|
|
|
|
|
|
Collection
|
|
|
-: {.image-left} See above for a description of collections.
|
|
|
+: {.left} See above for a description of collections.
|
|
|
|
|
|
Script
|
|
|
-: {.image-left} See above for a description of scripts.
|
|
|
+: {.left} See above for a description of scripts.
|
|
|
|
|
|
Sound
|
|
|
-: {.image-left} The sound component is responsible for playing a specific sound. Currently, Defold supports soundfiles of the type WAV.
|
|
|
+: {.left} The sound component is responsible for playing a specific sound. Currently, Defold supports soundfiles of the type WAV.
|
|
|
|
|
|
Collision object
|
|
|
-: {.image-left} Collision objects are components that extend game objects with physical properties (like spatial shape, weight, friction and restitution). These properties govern how the collision object should collide with other collision objects. The most common types of collision objects are kinematic objects, dynamic objects and triggers. A kinematic object gives detailed collision information that you have to manually respond to, a dynamic object is automatically simulated by the physics engine to obey Newtonian laws of physics. Triggers are simple shapes that detect if other shapes have entered or exited the trigger.
|
|
|
+: {.left} Collision objects are components that extend game objects with physical properties (like spatial shape, weight, friction and restitution). These properties govern how the collision object should collide with other collision objects. The most common types of collision objects are kinematic objects, dynamic objects and triggers. A kinematic object gives detailed collision information that you have to manually respond to, a dynamic object is automatically simulated by the physics engine to obey Newtonian laws of physics. Triggers are simple shapes that detect if other shapes have entered or exited the trigger.
|
|
|
|
|
|
Factory
|
|
|
-: {.image-left} See above for a description of factories.
|
|
|
+: {.left} See above for a description of factories.
|
|
|
|
|
|
Sprite
|
|
|
-: {.image-left} A sprite is a component that extends game objects with graphics. It displays an image either from a Tile source or from an Atlas. Sprites have built-in support for flip-book and bone animation. Sprites are usually used for characters and items. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
+: {.left} A sprite is a component that extends game objects with graphics. It displays an image either from a Tile source or from an Atlas. Sprites have built-in support for flip-book and bone animation. Sprites are usually used for characters and items. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
|
|
|
Atlas
|
|
|
-: {.image-left} An atlas is a set of separate images that are compiled into a larger sheet for performance and memory reasons. You can store still images or flip-book animated series of images. Atlases are used by Sprite and ParticleFX components to share graphics resources. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
+: {.left} An atlas is a set of separate images that are compiled into a larger sheet for performance and memory reasons. You can store still images or flip-book animated series of images. Atlases are used by Sprite and ParticleFX components to share graphics resources. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
|
|
|
|
|
|
|
|
|
Tile source
|
|
|
-: {.image-left} A tile source describes a texture that is composed of multiple smaller images, everyone with the same size. The component support flip-book animation. You can define animations over a sequence of images in the tile source. Tile sources can also automatically calculate collision shapes from image data. This is very useful for creating tiled levels that object can collide and interact with. Tile sources are used by Tile map (and Sprite and ParticleFX although Atlases are usually to prefer) components to share graphics resources. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
+: {.left} A tile source describes a texture that is composed of multiple smaller images, everyone with the same size. The component support flip-book animation. You can define animations over a sequence of images in the tile source. Tile sources can also automatically calculate collision shapes from image data. This is very useful for creating tiled levels that object can collide and interact with. Tile sources are used by Tile map (and Sprite and ParticleFX although Atlases are usually to prefer) components to share graphics resources. See the [2D graphics documentation](/manuals/2dgraphics) for more information.
|
|
|
|
|
|
|
|
|
|
|
|
@@ -102,47 +102,47 @@ Tile source
|
|
|
|
|
|
|
|
|
Tile map
|
|
|
-: {.image-left} Tile map components display images from a tile source in one or more overlaid grids. They are most commonly used to build game environments: ground, walls, buildings and obstacles. A tile map can display several layers aligned on top of each other with specified blend mode. This is useful to, for example, put foilage on top of grass background tiles. It is also possible to dynamically change the displayed image in a tile. That allows you to, for instance, destroy a bridge and make it impassable by simply replacing the tiles with ones depicting the broken down bridge and containing the corresponding physics shape.
|
|
|
+: {.left} Tile map components display images from a tile source in one or more overlaid grids. They are most commonly used to build game environments: ground, walls, buildings and obstacles. A tile map can display several layers aligned on top of each other with specified blend mode. This is useful to, for example, put foilage on top of grass background tiles. It is also possible to dynamically change the displayed image in a tile. That allows you to, for instance, destroy a bridge and make it impassable by simply replacing the tiles with ones depicting the broken down bridge and containing the corresponding physics shape.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ParticleFX
|
|
|
-: {.image-left} Particles are very useful for creating nice visual effects, particularly in games. you can use them to create fog, smoke, fire, rain or falling leaves. Defold contains a powerful particle effects editor that allows you to build and tweak effects while you run them real time in your game. The [ParticleFX documentation](/manuals/particlefx) gives you the details on how that works.
|
|
|
+: {.left} Particles are very useful for creating nice visual effects, particularly in games. you can use them to create fog, smoke, fire, rain or falling leaves. Defold contains a powerful particle effects editor that allows you to build and tweak effects while you run them real time in your game. The [ParticleFX documentation](/manuals/particlefx) gives you the details on how that works.
|
|
|
|
|
|
|
|
|
|
|
|
GUI
|
|
|
-: {.image-left} A GUI component contains elements used to construct user interfaces: text and colored and/or textured blocks. Elements can be organized into hierarchial structures, scripted and animated. GUI components are typically used to create heads-up displays, menu systems and on-screen notifications. GUI components are controlled with GUI scripts that defines the behavior of the GUI and controls the user interaction with it. Read more in the [GUI documentation](/manuals/gui).
|
|
|
+: {.left} A GUI component contains elements used to construct user interfaces: text and colored and/or textured blocks. Elements can be organized into hierarchial structures, scripted and animated. GUI components are typically used to create heads-up displays, menu systems and on-screen notifications. GUI components are controlled with GUI scripts that defines the behavior of the GUI and controls the user interaction with it. Read more in the [GUI documentation](/manuals/gui).
|
|
|
|
|
|
|
|
|
|
|
|
GUI script
|
|
|
-: {.image-left} GUI scripts are used to define the behaviour of GUI components. They control GUI animations and how the user interacts with the GUI.
|
|
|
+: {.left} GUI scripts are used to define the behaviour of GUI components. They control GUI animations and how the user interacts with the GUI.
|
|
|
|
|
|
Font
|
|
|
-: {.image-left} A Font is built from a TrueType or OpenType font file. The Font specifies which size to render the font in and what type of decoration (outline and shadow) the rendered font should have. Fonts are used by GUI components.
|
|
|
+: {.left} A Font is built from a TrueType or OpenType font file. The Font specifies which size to render the font in and what type of decoration (outline and shadow) the rendered font should have. Fonts are used by GUI components.
|
|
|
|
|
|
|
|
|
|
|
|
Input binding
|
|
|
-: {.image-left} Input binding files define how the game should interpret hardware input (mouse, keyboard, touchscreen and game pads). The file bind hardware input to high level input _actions_ like "jump" and "move_forward". In script components that listens to input you are then able to script the actions the game or app should take given certain input. See the [Input documentation](/manuals/input) for details.
|
|
|
+: {.left} Input binding files define how the game should interpret hardware input (mouse, keyboard, touchscreen and game pads). The file bind hardware input to high level input _actions_ like "jump" and "move_forward". In script components that listens to input you are then able to script the actions the game or app should take given certain input. See the [Input documentation](/manuals/input) for details.
|
|
|
|
|
|
|
|
|
|
|
|
Camera
|
|
|
-: {.image-left} Camera components helps to decide what part of the game world should be visible and how it should be projected. A common use case is to attach a camera to the player game object, or having a separate game object with a camera that follows the player around with some smoothing algorithm.
|
|
|
+: {.left} Camera components helps to decide what part of the game world should be visible and how it should be projected. A common use case is to attach a camera to the player game object, or having a separate game object with a camera that follows the player around with some smoothing algorithm.
|
|
|
|
|
|
Material
|
|
|
-: {.image-left} Materials define how different objects should be rendered by specifying shaders and their properties.
|
|
|
+: {.left} Materials define how different objects should be rendered by specifying shaders and their properties.
|
|
|
|
|
|
Render
|
|
|
-: {.image-left} Render files contains settings used when rendering the game to the screen. Render files define which Render script to use for rendering and which materials to use.
|
|
|
+: {.left} Render files contains settings used when rendering the game to the screen. Render files define which Render script to use for rendering and which materials to use.
|
|
|
|
|
|
Render script
|
|
|
-: {.image-left} A Render script is a Lua script that controls how the game or app should be rendered to the screen. There is a default Render script that covers most common cases, but you can write your own if you need custom lighting models and other effects.
|
|
|
+: {.left} A Render script is a Lua script that controls how the game or app should be rendered to the screen. There is a default Render script that covers most common cases, but you can write your own if you need custom lighting models and other effects.
|
|
|
|
|
|
Collection proxy
|
|
|
-: {.image-left} A Collection proxy is used to load and enable collections on the fly while an app or game is running. The most common use case for Collection proxies are to load levels as they are to be played. See the [Collection proxy documentation](/manuals/collection-proxy) for details.
|
|
|
+: {.left} A Collection proxy is used to load and enable collections on the fly while an app or game is running. The most common use case for Collection proxies are to load levels as they are to be played. See the [Collection proxy documentation](/manuals/collection-proxy) for details.
|
|
|
|
Mikael Säker