Creating Custom Events - Revision history

Sanglorian at 23:03, 7 October 2017

2017-10-07T23:03:27Z

← Older revision		Revision as of 23:03, 7 October 2017
Line 20:		Line 20:
	'''core/components/event/conditions/core.py'''		'''core/components/event/conditions/core.py'''

	~~<code>~~
	python		python
	...		...
Line 28:		Line 27:
	return True		return True
	...		...
	~~</code>~~

	Notice that ''every'' condition must have these two parameters:		Notice that ''every'' condition must have these two parameters:
Line 39:		Line 37:

	Here's an example of what you might get back as a condition you define in [http://www.mapeditor.org Tiled]:		Here's an example of what you might get back as a condition you define in [http://www.mapeditor.org Tiled]:
	~~<code>python~~

	~~>>>~~ condition		python
			condition
	{'id': 3,		{'id': 3,
			'operator': 'is',
	'operator': 'is',		'parameters': '1',
			'type': 'always_true',
	'parameters': '1',		'x': 1,
			'y': 3}
	'type': 'always_true',

	'x': 1,

	'y': 3}
	~~</code>~~

	After creating your condition, you can now open up [Tiled](http://www.mapeditor.org) and create a new event with your condition!		After creating your condition, you can now open up [Tiled](http://www.mapeditor.org) and create a new event with your condition!
Line 66:		Line 57:

	'''core/components/event/actions/core.py'''		'''core/components/event/actions/core.py'''
	~~<code>python~~

	...		python
			...
	def say_hello(self, game, action):		def say_hello(self, game, action):
			print "Hello World!"
	~~<nowiki> </nowiki>~~print "Hello World!"		print " Action:", action
			...
	~~<nowiki> </nowiki>~~print " Action:", action

	...
	~~</code>~~

	Notice that ''every'' action must have these two parameters:		Notice that ''every'' action must have these two parameters:
Line 88:		Line 74:

	Here's an example of what an action might look like:		Here's an example of what an action might look like:
	~~<code>python~~

	>>> action		python
			>>> action
	('say_hello', 'Hi', '3', 1)		('say_hello', 'Hi', '3', 1)
	~~</code>~~

	After creating your action, you can now open up [http://www.mapeditor.org Tiled] and include it in your event!		After creating your action, you can now open up [http://www.mapeditor.org Tiled] and include it in your event!

Sanglorian: /* Creating conditions */

2017-10-07T23:00:37Z

Creating conditions

← Older revision		Revision as of 23:00, 7 October 2017
Line 19:		Line 19:

	'''core/components/event/conditions/core.py'''		'''core/components/event/conditions/core.py'''
	<code>python
	...		<code>
	def always_true(self, game, condition):		python
	print "This will always return True!"		...
	print " Condition:", condition		def always_true(self, game, condition):
	return True		print "This will always return True!"
	...</code>		print " Condition:", condition
			return True
			...
			</code>

	Notice that ''every'' condition must have these two parameters:		Notice that ''every'' condition must have these two parameters:

Sanglorian: /* Creating conditions */

2017-10-07T22:58:05Z

Creating conditions

← Older revision		Revision as of 22:58, 7 October 2017
Line 20:		Line 20:
	'''core/components/event/conditions/core.py'''		'''core/components/event/conditions/core.py'''
	<code>python		<code>python

	...		...

	def always_true(self, game, condition):		def always_true(self, game, condition):
			print "This will always return True!"
	~~<nowiki> </nowiki>~~print "This will always return True!"		print " Condition:", condition
			return True
	~~<nowiki> </nowiki>~~print " Condition:", condition		...</code>

	~~<nowiki> </nowiki>~~return True

	...
	</code>

	Notice that ''every'' condition must have these two parameters:		Notice that ''every'' condition must have these two parameters:

Sanglorian at 22:56, 7 October 2017

2017-10-07T22:56:45Z

← Older revision		Revision as of 22:56, 7 October 2017
Line 20:		Line 20:
	'''core/components/event/conditions/core.py'''		'''core/components/event/conditions/core.py'''
	<code>python		<code>python

	...		...

	def always_true(self, game, condition):		def always_true(self, game, condition):

	<nowiki> </nowiki>print "This will always return True!"		<nowiki> </nowiki>print "This will always return True!"

	<nowiki> </nowiki>print " Condition:", condition		<nowiki> </nowiki>print " Condition:", condition

	<nowiki> </nowiki>return True		<nowiki> </nowiki>return True

	...		...
	</code>		</code>
Line 36:		Line 42:
	The <code>condition</code> parameter will give you access to the condition that was defined in the map file. This is good if you want to check for other parameters that your condition might require.		The <code>condition</code> parameter will give you access to the condition that was defined in the map file. This is good if you want to check for other parameters that your condition might require.

	Here's an example of what you might get back as a condition you define in [~~Tiled](~~http://www.mapeditor.org):		Here's an example of what you might get back as a condition you define in [http://www.mapeditor.org Tiled]:
	<code>python		<code>python

	>>> condition		>>> condition

	{'id': 3,		{'id': 3,

	'operator': 'is',		'operator': 'is',

	'parameters': '1',		'parameters': '1',

	'type': 'always_true',		'type': 'always_true',

	'x': 1,		'x': 1,

	'y': 3}		'y': 3}
	</code>		</code>
Line 58:		Line 71:
	'''core/components/event/actions/core.py'''		'''core/components/event/actions/core.py'''
	<code>python		<code>python

	...		...

	def say_hello(self, game, action):		def say_hello(self, game, action):

	<nowiki> </nowiki>print "Hello World!"		<nowiki> </nowiki>print "Hello World!"

	<nowiki> </nowiki>print " Action:", action		<nowiki> </nowiki>print " Action:", action

	...		...
	</code>		</code>
Line 75:		Line 93:
	Here's an example of what an action might look like:		Here's an example of what an action might look like:
	<code>python		<code>python

	>>> action		>>> action

	('say_hello', 'Hi', '3', 1)		('say_hello', 'Hi', '3', 1)
	</code>		</code>

Sanglorian at 22:55, 7 October 2017

2017-10-07T22:55:24Z

← Older revision		Revision as of 22:55, 7 October 2017
Line 22:		Line 22:
	...		...
	def always_true(self, game, condition):		def always_true(self, game, condition):
	print "This will always return True!"		<nowiki> </nowiki>print "This will always return True!"
	print " Condition:", condition		<nowiki> </nowiki>print " Condition:", condition
	return True		<nowiki> </nowiki>return True
	...		...
	</code>		</code>
Line 60:		Line 60:
	...		...
	def say_hello(self, game, action):		def say_hello(self, game, action):
	print "Hello World!"		<nowiki> </nowiki>print "Hello World!"
	print " Action:", action		<nowiki> </nowiki>print " Action:", action
	...		...
	</code>		</code>
Line 81:		Line 81:
	After creating your action, you can now open up [http://www.mapeditor.org Tiled] and include it in your event!		After creating your action, you can now open up [http://www.mapeditor.org Tiled] and include it in your event!

	[http://i.imgur.com/WlKvYkL.png]		http://i.imgur.com/WlKvYkL.png

	Now run Tuxemon and go to your map and see what happens! You should see the console printing everything you defined in your action and condition!		Now run Tuxemon and go to your map and see what happens! You should see the console printing everything you defined in your action and condition!

Sanglorian at 22:53, 7 October 2017

2017-10-07T22:53:40Z

← Older revision		Revision as of 22:53, 7 October 2017
Line 4:		Line 4:
	The Tuxemon event engine begins by first loading all of the events defined in the currently loaded map. After all the map's events have been loaded, the event engine will, ''every frame'', loop through each event and check to see if all the conditions for that event are <code>True</code>. If each condition returns <code>True</code>, it will execute all of the actions defined in that event in order (e.g. <code>act1</code>, <code>act2</code>, etc.).		The Tuxemon event engine begins by first loading all of the events defined in the currently loaded map. After all the map's events have been loaded, the event engine will, ''every frame'', loop through each event and check to see if all the conditions for that event are <code>True</code>. If each condition returns <code>True</code>, it will execute all of the actions defined in that event in order (e.g. <code>act1</code>, <code>act2</code>, etc.).

	[http://i.imgur.com/6LvZrBv.png]		http://i.imgur.com/6LvZrBv.png

	The actual ''methods'' that define ''what'' to check for (in the case of conditions) or ''what'' to execute (in the case of actions) are all defined in the <code>core.components.event</code> module. '''Any method defined in this module will be available for you to use in the map editor.''' When Tuxemon is first initialized, the event engine will go through this module and make ''all'' the methods available as conditions or actions to execute during the main loop. Because of this, you '''must ensure that all new method names are unique'''.		The actual ''methods'' that define ''what'' to check for (in the case of conditions) or ''what'' to execute (in the case of actions) are all defined in the <code>core.components.event</code> module. '''Any method defined in this module will be available for you to use in the map editor.''' When Tuxemon is first initialized, the event engine will go through this module and make ''all'' the methods available as conditions or actions to execute during the main loop. Because of this, you '''must ensure that all new method names are unique'''.

Sanglorian: Created page with "== Introduction == The Tuxemon event system is designed to easily allow users to create new actions and conditions that you can use in-game. This page will show you how to cre..."

2017-10-07T22:52:34Z

Created page with "== Introduction == The Tuxemon event system is designed to easily allow users to create new actions and conditions that you can use in-game. This page will show you how to cre..."

New page

== Introduction ==
The Tuxemon event system is designed to easily allow users to create new actions and conditions that you can use in-game. This page will show you how to create your own "Hello World" action, but first, a brief explanation about ''how'' the event system works.

The Tuxemon event engine begins by first loading all of the events defined in the currently loaded map. After all the map's events have been loaded, the event engine will, ''every frame'', loop through each event and check to see if all the conditions for that event are <code>True</code>. If each condition returns <code>True</code>, it will execute all of the actions defined in that event in order (e.g. <code>act1</code>, <code>act2</code>, etc.).

[http://i.imgur.com/6LvZrBv.png]

The actual ''methods'' that define ''what'' to check for (in the case of conditions) or ''what'' to execute (in the case of actions) are all defined in the <code>core.components.event</code> module. '''Any method defined in this module will be available for you to use in the map editor.''' When Tuxemon is first initialized, the event engine will go through this module and make ''all'' the methods available as conditions or actions to execute during the main loop. Because of this, you '''must ensure that all new method names are unique'''.

This might all be a little complex at first, but once you go through an example, things might start making more sense.

== Hello World Example ==
Now that you have a basic overview of how the event system works, let's try creating an example action and condition!

=== Creating conditions ===
To create our first condition, we'll need to define a new method in any of the files located in the <code>core.components.event.conditions</code> module. Your condition will work in any file in this module, but try and include it in the most relevant one (e.g. if it's NPC related, put it in the <code>npc.py</code> file).

To make things simple, we'll create a condition that will always be true. Let's call our new condition "always_true":

'''core/components/event/conditions/core.py'''
<code>python
...
def always_true(self, game, condition):
print "This will always return True!"
print " Condition:", condition
return True
...
</code>

Notice that ''every'' condition must have these two parameters:
* <code>game</code>
* <code>condition</code>

The <code>game</code> parameter will give you the main Tuxemon game object which will give you access to all in-game variables. You can use these in-game variables to check for whatever conditions you'd like.

The <code>condition</code> parameter will give you access to the condition that was defined in the map file. This is good if you want to check for other parameters that your condition might require.

Here's an example of what you might get back as a condition you define in [Tiled](http://www.mapeditor.org):
<code>python
>>> condition
{'id': 3,
'operator': 'is',
'parameters': '1',
'type': 'always_true',
'x': 1,
'y': 3}
</code>

After creating your condition, you can now open up [Tiled](http://www.mapeditor.org) and create a new event with your condition!

http://i.imgur.com/9PVkLyZ.png

=== Creating actions ===
Creating actions is very similar to creating conditions. Instead of returning <code>True</code> or <code>False</code> if a condition is met or not though, you can create actions that will make in-game changes. To create our first action, we'll need to define a new method in any of the files located in the <code>core.components.event.actions</code>. Your action will work in any file in this module, but try and include it in the most relevant one (e.g. if it's NPC related, put it in the <code>npc.py</code> file).

To make things simple, we'll create an action that will simply print "Hello World!" on the command line. We'll also print out the <code>action</code> parameter so you can see what that looks like. Let's call our new action "say_hello":

'''core/components/event/actions/core.py'''
<code>python
...
def say_hello(self, game, action):
print "Hello World!"
print " Action:", action
...
</code>

Notice that ''every'' action must have these two parameters:
* <code>game</code>
* <code>action</code>

The <code>game</code> parameter will give you the main Tuxemon game object which will give you access to all in-game methods and variables. You can use these in-game methods and variables to carry out any action you'd like.

The <code>action</code> parameter will give you access to the action that was defined in the map file. This is good if you want to check for other parameters that your action might require.

Here's an example of what an action might look like:
<code>python
>>> action
('say_hello', 'Hi', '3', 1)
</code>

After creating your action, you can now open up [http://www.mapeditor.org Tiled] and include it in your event!

[http://i.imgur.com/WlKvYkL.png]

Now run Tuxemon and go to your map and see what happens! You should see the console printing everything you defined in your action and condition!