Construct 2 Timer Before Event Can Happen Again

If you're new to Construct 2'southward events, this department will outline how they piece of work. This is essential reading for beginners! You will exist able to make much amend and more reliable games with a thorough agreement of how events work.

To learn how to add together and edit events, run into Outcome Canvass View.

Events are designed to be easily readable and to intuitively "just work". Notwithstanding, they accept specific, well-divers means of working which is described here.

Events piece of work by filtering specific instances that come across some weather condition. The actions then run for those instances simply. For example, consider the following event:

In this example, when a Bullet collides with a Monster the consequence condition is met. The specific instances of Bullet and Monster that collided in the game are "picked" by the event. Actions simply run on the "picked" instances. If at that place are other instances of Bullet and Monster in the layout, they won't be affected by the Subtract one from health and Destroy deportment. It would exist very difficult to brand good games if every bullet hurt every monster!

Another fashion to remember about an event is "If all atmospheric condition are met then run deportment on the instances coming together the weather condition".

Multiple atmospheric condition

Adding more than weather to an result progressively filters the instances to run deportment on. For example:

This event runs like this:

1. Start all Monsters that are on-screen are picked.
2. So, of those on-screen, it is reduced to those with less than five health.
3. The activeness makes all monsters that are both on-screen and accept less than 5 health expect directly at the histrion. Monsters that are off-screen or accept five or more health are not afflicted.

Therefore, using multiple conditions you can run deportment on just the instances meeting several criteria. Users from programming languages or other tools might recognise this as a logical "AND". All conditions of an outcome must be met for the actions to run. If no monsters are on-screen or none of those on-screen take less than 5 health, the actions exercise not run at all.

Unreferenced objects

Have a look at the post-obit event:

If the user presses Spacebar and the Player's PowerupEnabled boolean is set, the activity does Monster: Destroy. Note that there aren't any atmospheric condition that filter or choice Monsters in this event. In this case, all Monster instances are destroyed. In other words, if an upshot doesn't reference an object in its conditions, deportment apply to all the instances of that object.

Think of conditions as starting with all instances beingness picked, and progressively filtering them from there. If there were no weather, there are nonetheless all instances picked, so the activity affects all of them.

Picking resets between events

After an consequence ends, the side by side event begins from scratch. Its weather condition will start picking from all instances once again.

On the other hand, sub-events (which appear indented) carry on from where its parent event left off. A sub-issue will farther filter the instances left over by the event that came before it. If an consequence has two sub-events, they both choice from the same set of instances the parent left - the 2nd sub-event is non affected past the first. In other words, events at the same indentation level e'er option from the same gear up of instances, and events at a lower indentation level are ever working with the instances handed down from above.

The Arrangement object

In Construct 2 the Organization object represents built-in functionality. It has no instances. This means most system conditions do non pick whatever instances: they are either true or false. If they are false the event stops running, otherwise the event continues without the picked instances having been inverse. There are exceptions, though: if a arrangement condition uses an object, such as Pick random instance, that will affect the picked objects.

System deportment practice non run on any picked objects: they but run if all of the event'due south weather condition were met.

Events run tiptop to bottom

The social club of events is important. Every result is checked once per tick (about threescore times a 2d on almost computers), and they are run from summit to lesser in the event sheet. The screen is drawn one time every event has been run, then the process starts once again. This means if one consequence does something and the next effect undoes information technology, you'll never see that anything happened.

The aforementioned applies within events: conditions are checked from meridian to lesser, and the deportment run from top to bottom.

Even so, triggers are an exception. Run across the light-green pointer to the left of Keyboard: On Space pressed from the previous example:

This indicates the result is triggered. Rather than running once per tick, this upshot just runs (or "fires") upon something actually happening. In this case, the event runs when the user hits the Spacebar key on the keyboard. It is never checked whatever other fourth dimension. Since triggers run upon an outcome happening, they aren't checked in top-to-bottom order like other events. This means the ordering of triggers relative to other events is not of import (except relative to other triggers of the same type, since triggers still burn down top-to-bottom).

In that location tin can only be 1 trigger in an result, because two triggers cannot fire simultaneously. However, multiple triggers tin be placed in 'Or' blocks (see the adjacent section).

'Or' blocks

As mentioned earlier, all weather condition have to be met for an event to run. This is called a 'Logical AND', considering "condition 1 AND condition 2 AND condition iii..." etc. must be truthful. However, you can change an event to run when any condition is true. This is called a 'Logical OR', because the outcome will run if "condition 1 OR condition 2 OR condition iii..." are true.

Normally blocks work equally 'AND' blocks. To make an 'OR' block, right-click the block and select Brand 'Or' block. Information technology will then brandish with - or - between each condition, equally shown beneath.

Note that because OR blocks run if any condition is true, it's possible the event will still run if some atmospheric condition were faux and did not pick whatsoever instances. In this case the actions will withal run, but possibly with zippo instances picked for any objects where no instances met the condition. If whatsoever actions are run for objects with no instances picked, nothing happens.

Likewise note normally you can only put one trigger in an event, but you can put multiple triggers in an 'Or' block, and the upshot will run if any of triggers run.

Y'all can combine the cake types by using sub-events. This allows you to build upward more advanced logic, such equally an 'Or' block followed by an 'And' block.

Looping conditions

Some events loop, which simply ways they repeat their actions many times. Note the green round arrow in the below instance to indicate this.

This means when the layout starts, the Create object action repeats x times. The terminate result is 10 monsters are created at random positions in the layout on startup.

At that place tin also be more weather condition following the Repeat status. These are tested on each of the repeats as well, and must be true for the actions to run. There can fifty-fifty be more one loop in an event, simply this is rare.

Families and containers

Note families pick their instances entirely separately from whatever of the object types in the family unit. For more data, see the section Picking families in events in the manual entry on Families.

Containers are an avant-garde feature that can also make groups of instances always be picked together. For more than information see the manual entry on Containers.

Summary

Using this event arrangement it'south possible to make sophisticated logic for games apace and hands. It is a very powerful alternative to scripting or programming languages but much easier for non-technical people to use.

Although this section has described the essential parts of the event system, it still has not covered everything. The rest of the Events section covers more features you can apply in events. The Behavior reference, Plugin reference and System reference as well embrace all the conditions, actions and expressions in Construct 2.

allenoaccurescry.blogspot.com

Source: https://www.construct.net/en/construct-2/manuals/construct-2/project-primitives/events/events-work

Share this post