1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
.. _gamemaker-export:
GameMaker: Studio 1.4
---------------------
GameMaker: Studio 1.4 uses a custom XML-based format to store its rooms,
and Tiled ships with a plugin to export maps in this format. Currently
only orthogonal maps will export correctly.
Tile layers and tile objects (when no class is set) will export as "tile"
elements. These support horizontal and vertical flipping, but no
rotation. For tile objects, scaling is also supported.
.. warning::
The tilesets have to be named the same as the corresponding backgrounds
in the GameMaker project. Otherwise GameMaker will pop up an error for each
tile while loading the exported ``room.gmx`` file.
Object Instances
~~~~~~~~~~~~~~~~
GameMaker object instances are created by putting the object name in the
"Class" field of the object in Tiled. Rotation is supported here, and for
tile objects also flipping and scaling is supported (though flipping in
combination with rotation doesn't appear to work in GameMaker).
.. raw:: html
<div class="new new-prev">Since Tiled 1.1</div>
The following custom properties can be set on objects to affect the
exported instance:
* string ``code`` (instance creation code, default: "")
* float ``scaleX`` (default: derived from tile or 1.0)
* float ``scaleY`` (default: derived from tile or 1.0)
* int ``originX`` (default: 0)
* int ``originY`` (default: 0)
The ``scaleX`` and ``scaleY`` properties can be used to override the
scale of the instance. However, if the scale is relevant then it will
generally be easier to use a tile object, in which case it is
automatically derived from the tile size and the object size.
The ``originX`` and ``originY`` properties can be used to tell Tiled
about the origin of the object defined in GameMaker, as an offset from
the top-left. This origin is taken into account when determining the
position of the exported instance.
.. hint::
Of course setting the class and/or the above properties manually for
each instance will get old fast. Since Tiled 1.0.2, you can instead
use tile objects with the class set on the tile, and in Tiled 1.1 you
can also use :doc:`object templates <using-templates>`.
.. raw:: html
<div class="new new-prev">Since Tiled 1.1</div>
Views
~~~~~
.. figure:: images/gamemaker-view-settings.png
:alt: GameMaker View Settings
:align: right
Views can be defined using :ref:`rectangle objects <insert-rectangle-tool>`
where the Class has been set to ``view``. The position and size will be
snapped to pixels. Whether the view is visible when the room starts
depends on whether the object is visible. The use of views is
automatically enabled when any views are defined.
The following custom properties can be used to define the various other
properties of the view:
**Port on screen**
* int ``xport`` (default: 0)
* int ``yport`` (default: 0)
* int ``wport`` (default: 1024)
* int ``hport`` (default: 768)
**Object following**
* string ``objName``
* int ``hborder`` (default: 32)
* int ``vborder`` (default: 32)
* int ``hspeed`` (default: -1)
* int ``vspeed`` (default: -1)
.. hint::
When you're defining views in Tiled, it is useful to add ``view``
as class in the :ref:`Custom Types Editor <custom-property-types>`,
adding the above properties for ease of access. If you frequently use
views with similar settings, you can set up
:doc:`templates <using-templates>` for them.
Map Properties
~~~~~~~~~~~~~~
General
^^^^^^^
* int ``speed`` (default: 30)
* bool ``persistent`` (default: false)
* bool ``clearDisplayBuffer`` (default: true)
* bool ``clearViewBackground`` (default: false)
* string ``code`` (map creation code, default: "")
Physics
^^^^^^^
* bool ``PhysicsWorld`` (default: false)
* int ``PhysicsWorldTop`` (default: 0)
* int ``PhysicsWorldLeft`` (default: 0)
* int ``PhysicsWorldRight`` (default: width of map in pixels)
* int ``PhysicsWorldBottom`` (default: height of map in pixels)
* float ``PhysicsWorldGravityX`` (default: 0.0)
* float ``PhysicsWorldGravityY`` (default: 10.0)
* float ``PhysicsWorldPixToMeters`` (default: 0.1)
Layer Properties
~~~~~~~~~~~~~~~~
Both tile layers and object layers may produce "tile" elements in the exported
room file. Their depth is set automatically, with tiles from the bottom-most
layer getting a value of 10000000 (the GameMaker default) and counting up from
there. If you want to set a custom depth value you can set the following
property on the layer:
* int ``depth`` (default: 10000000 + N)
|
