When you get a chance, could you make it an option to toggle the debug window to the SIDE of the browser in addition to its initial nestled point lengthwise at the bottom? :) Thanks. And AMAZING update with r141!!! WOW!

What Sargas said will work, too. I will usually set it every 0.1 seconds or so to give it that fraction of time be it needs to calculate a new path it the object being chased is always moving. The pathfinding acts rather smoothly then.

• Visible Path Finding paths and/or highlighted cells.
• The debug window with the option to decrease the don't size.
• The ability to automatically change variable or object parameter values during debug view from the debug window.
• Visible line of sight cone.
• Real-time event log of game as it plays.

CAPX - https://www.sugarsync.com/pf/D6025908_4317202_6987262

I've swapped out all my events and actions for my Enemy objects and replaced them with the AllEnemies family (all Enemy objects are in the family folder).

But for some reason, I cannot figure out why the enemies will not so much as move along the path via Path Finding. I've double-checked the ChaseStatus variable and that's good. Debug shows nothing out of the ordinary that I can see.

Is there something about the Families option that is preventing me from getting my enemies from moving along the paths via Path Finding?

(I can go into greater detail if you need me to...)

eldods - :) Man, Ashley hasn't even confirmed that it WILL be in C2. We still need him to confirm that he LIKES the idea. Thank you for the enthusiastic support, nonetheless! :D

Similar to Path Finding, I would like to recommend a Path Making behavior.

Where as Path Finding plots its path to a selected point according to the obstacles between Point A and Point B, Path Making would define a strict, straight, specific path the objects would follow...a patrol route, in essence.

This could be used for enemies in a top-down game to patrol prescribed zones or bosses in side-scrollers to follow a pattern to be discovered (revealing a weak point in the process).

At present, I'm trying to work out my own patrol system/Path Making behavior from the existing C2 engine, and I'm frequently hitting road blocks. What I've worked out so far is to create these "nodes", contain them with variables and/or arrays that define which directions are open for the character to pursue, and then tell it to find the path from that node to the next node. This has worked, with much pain and labor, but it's not perfect.

What I propose then, is that the Path Maker behavior will allow you to set similar nodes which will give you the option to define how the character will behave when it arrives at that node:

• will it randomly choose from all available path?
• will it be able to choose the path it arrived on?
• will it cycle through the paths in a sequential order?

You can further choose the angle the paths are set at as they branch out from each node (and of course, there will be the option to choose how obstacles are set).

The main difficulty I've had in setting up my own system like this is how to place each node in a way that, regardless of how I arrange the nodes, it will have the information it needs on which node to travel to next. But in this case, the character needs only to know to follow the patrol path established by whichever node it originates from. If that path leads to another node, then that path, though perhaps originating from another node, is considered a viable pathway (perhaps an option to make paths one-way regardless of its origins?).

In summary:

1. Nodes are origin points for paths.

2. Paths can be set at any angle.

3. Per-node options to dictate...

-- How the character will choose a new path.

-- Which paths are available to select from.

-- If paths are one-way or two-way.

-- The length of the path or if it is to end at another node it overlaps.

4. The character will strictly follow the path, similar to Path Finding.

5. Paths that overlap other nodes will be considered viable paths to select from unless the parameters of the originating node dictate otherwise.

(See my crude illustration here: https://www.sugarsync.com/pf/D6025908_4317202_6987563.)

This is probably an idea that would require some refinement if it's applied to updates to C2, but I hope it's a viable one.

Your thoughts?

Right now, setting an instance boolean variable is limited to toggling the true/false value of the variable. But I'd like to see a feature where I can set the boolean of one instance variable to the value of another boolean instance variable.

For instance...

Object 1 hits object 2. Both have a boolean instance value "is hit". Upon object 1 registering there is a collision, its "is hit" boolean changes to "true". Object 2 (for whatever reason) checks the value of Object 1's "is hit" (now "true") and says "set Object 2 'is hit' to the value of Object 1 'is hit'".

This way it works just like other variables where Variable1 can set its value to whatever Variable2's value is (be it string or number).

Can we do this?

Thank you, once again, — I'll look it over and see what I can work out. I'm probably gonna scrap my Patrol system (during Normal status) and try to simplify it... May I petition you for further help in the future?

blackhornet - I think I understand. So it won't hurt anything if I were to delete such Browser events/actions? (I'm gonna read up on the manual before I change anything, though.)

I noticed a couple of things, though, when I repositioned the patrol zones.

CAPX: sugarsync.com/pf/D6025908_4317202_6971329

1. The enemy does not automatically begin his patrol at the start of the game.

2. When the enemy approaches the upper-left Node, it seems to stutter.

3. I didn't change anything in my PatrolRoutes event sheet, but when the enemy approaches the upper-right Node, it never takes the occasional downward trip to the bottom-right Node. (I'm considering altering this set-up anyway - removing the random nature in which way the enemy will go when it reaches a junction.)

What can you see in light of these issues?

Rest well, Scirra Bros! Thank you for the heads up!

blackhornet - Okay, so here's where I stand with your changes...

Event: Your changes

Action: Set MyMind to "blown"

I never once thought to look into using the Browser object. CLEARLY I have some research to do!

In the meantime, can you give me a summary of what's actually going on with the use of the Browser object, please? Like, amongst other things, what's all the "Log in console" about?

Thank you so much! You've just helped me complete the final piece to what's been a three-month headache!!! lol

Thanks, — :D I'll check it out...