It's so beautiful! :')

I still don't fully understand the logic of this but it works!

Thank you vee41!

Just to be clear:

When I say "Burst-Fire", I mean a gun shooting a number of successive rounds with a single pull of the trigger.

With the code I have so far, I can make an Automatic/Semi-Automatic Rifle/SMG/Pistol/Shotgun/Spreadgun. You name it.

But for the love of god I am struggling to figure out how to make it burst-fire.

I've tried using loops and calling the same function within itself to no avail.

Here is a the section of my code:

• At the top is the conditions that need to be met for the function to be called.
• the "weapon.bulletsPerBurst" is what determines the weapon to be a single-shot or spread-shot.
• "weapon.burstRate" is what I use to determine how many times that weapon shoots successively.

Event Sheet Snapshot

<img src="http://i.imgur.com/ol5oQVe.png1" border="0">

Any help to make this work will be appreciated.

I still think that providing more expressions

[ie. TargetX, TargetY, TargetInstanceVariable("") {even if by string} ]

to the turret behaviour can help cut down the total number of events, yet more importantly, increase the scaleability of a project.

Just my little thoughts. And thank you fellows for your help. :)

Thank you Guizmus! This should be perfect!

The sub-events solution seemed simple enough, but for the love of god I just could not work my way around to implementing it. Like you said, it can become extensive the more targets you add, and I was really looking for a short and concise solution.

Unfortunately, I was really hoping that short and concise solution did not involve families seeing how I am using the free edition. Sadly, I have no other options do I?

Nevertheless, thank you very much for the assistance Guizmus!

How did I not see that button?!

The is embarrassing.

Thank you blackhornet for clearing this up for me.

Link to .capx file (required!):

[Withdrawn]

Notes:

• Sprites have a large number of animations.

Steps to reproduce:

1. Set team2 sprite to an animation lower in the list (ie. "Purple", "LightBlue", "Black")

2. Wait until a number of units have been spawned.

3. Shoot at armed units until bullets suddenly pass through (Takes a while, but usually occurs in under 20 kills)

Observed result:

• Observed with animations lower in the list ("Purple", "LightBlue", "Black").
• Has not occurred with animations higher in the list ("Blue", "Green")

Bullets will collide with the enemy sprite, but on some instances, the bullets only pass over them for some reason.

Shoots long enough, and the bullets will 'eventually' collide and destroy the target.

(Points of interest are bookmarked in the event sheet.)

Expected result:

All bullets to collide when I command them to.

Browsers affected:

Chrome: yes

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

Windows 8 64-bit

Construct 2 version:

    r137 32-bit

Hi BluePhaze, and thanks for the reply!

Movement should not be an issue as I am using both the Turret and Path-finding behaviours in tandem, unless path-finding is not the optimal choice.

In addition, I have tried using the "Pick Object" condition, but my struggle with it is that it can only pick 1 object(not in terms of instances but unique project objects like a sprite or tiled background).

My issue is that my turret has more than 1 unique sprite in its target list, and that is where my struggle begins.

If you, or anyone else, would kindly shed more light on this or provide a .capx example, I would appreciate it very much.

or use Spawn: choose("speople1", "speople2")

Wow, how did I not know about this expression? Thank you California!

I don't have a well worded thought about this question yet, but I wanted more access to possible turret expressions.

Right now, I have a situation where I would like an AI to be able to move towards a target acquired. In other words, I want access to:

• TargetX; and
• TargetY

In another situation I thought of is being able to access target instance variables. It may be impossible as targets vary, but I was wondering 'What if it was called by a string?'

All in all, I simply hoped there would be more expressions for the turret behaviour when I went looking. Sadly there were only four. :(

Is there a way in which I can work around these hurdles? Much help would be appreciated.

scirra.com/arcade/addicting-shooter-games/6083/destroy-all-wasabis

Please and thank you.

Edit: To whomever this may concern, thank you.

Link to .capx file (required!):

https://www.dropbox.com/s/umndm18ob93nk55/Game_pathfindingTest.capx

Steps to reproduce:

1. Setup 2 different spawn areas. (two teams, ie. blue and green)

2. Create a blue team sprite with pathfinding behaviour (custom obstacles).

i.   Spawn in respective spawn area.

ii. Add opposing team spawn area to obstacle list.

iii. Regenerate obstacle map.

iv. Find a path somewhere in the layout.

v.   Travel along path.

3. Same as step 2 but with the green team.

i - ii - iii - iv - v

(Optional) If spawn areas placed to far for viewing, setup a method to observe the results. (eg, player sprite with 8Direction and ScrollTo behaviour)

Observed result:

Only one team actually moves as.

From my personal observation, green team spawns and finds a way around but never into blue area; blue team, on the other hand, does not give a single pixel about the fact that green in infesting the area.

Expected result:

Adding green spawn area to blue's obstacles list allows blue to wander everywhere but into green spawn area.

Vice-versa for green.

Browsers affected:

Chrome: yes

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

OS: Windows 8

SP: ?

Construct 2 version:

Construct 2: r132

Hey peoples! How's it going?

First off, I love the aggregation of so many elements in this behavior that really compacts the number of events and variables in my project.

Thank you JohnJ !

My main concern with this behavior is that when I have more than one instance of the same gun, whenever the gun is commanded to shoot, bullets only come from the first instance of the gun.

I don't know if it's because of the way I have it set up, but my head is aching at the moment and I want someone with a fresher mind that can help shed some light into alternative methods.

Here's the project I was talking about:

No map design & Shoooting activated.

Shooting deactivated w/ Map design (just for watching pathfinding work its magic)