1) Hmm. Insane amount of loop, huh? How much do you reccomend?

2) RotateAngle() comes out as "RotateAngle(Start, End, Step)" when you pick it out from system expressions, so I assume it's meant to 'rotate' the value from start to end, using the "step" parameter for how much per step. Of course, this obviously means having to re-work the event.

3) Ah, I see, now. Though, I'm not sure what the bottom one does exactly.

LATEST UPDATE: The below problems are more or less out of the way mainly because of r86, except for number (2), for a particular reason.

I've isolated the angle problem that this engine is having, to TWO main possible factors. It can only be one or the other, not both, I presume.

a) The anglelerp(a, b, x) expression. It's supposed to replace the RotateAngle() expression from Classic, but I have a feeling it's not working right. I'm gonna ask Ashley about it via PM.

b) The collision detection system might not be working properly in this instance, though I can't see how it would cause spontaneous and virtually random changes in angle.

------

I've been trying to port a Sonic engine someone else made from Construct Classic to Construct 2, but there's been a few issues that has halted progress. Three main issues:

(1) I'm pretty sure the "While" condition is completely redundant, but if not, how do you create a work-around for them?

(2) Construct 2 doesn't have the "RotateAngle" expression, resulting in the player unable to rotate properly.

<img src="http://dl.dropbox.com/u/919275/Screenshots/AOD/RotateAngleExpression.png" border="0">

(3) Construct 2 doesn't have the "Sign" expression... Whatever the hell that is.

<img src="http://dl.dropbox.com/u/919275/Screenshots/AOD/SignExpression.png" border="0">

I'll provide the caps here:

Classic .cap (Version r2, requires the MagiCam and Slgor's input system plugins.)

Construct 2 .capx, release 86, requires Standard license (requires the Function Plugin)

Go to the "Player_Code" event sheet on both, and open up two groups:

• Motion Management -> Tools (Whole group, for (1) and (2), I'm going to replace the "Parameter" function with a variable to get around the "Else" problem)
• Movement Routines -> Movement (look at the "Calculate Sub-Step" events for (3))

If anyone has any idea on how to work around these issues, I'd be grateful.

Tested, pretty much perfect on my Win 7 laptop, except for that odd alpha thing going on with certain objects, but otherwise, pretty much perfect.

I'm eager to see this properly implemented as an export!

Well, to actually save stuff, like changes to tiles, and whatnot. Probably the only file format to hold data like that would work with HTML5, it's not like we're gonna be using ini files. :p

Arrays for storing tile data during runtime, XMLs for saving them. That works.

Well, that's fascinating. That being said, I imagine it would require two main things: Arrays/XML files, and being able to save arrays/XMLs. And C2 can only do arrays, but not save them. So... Yeah. A bit of a problem.

For those who haven't played Terraria,

It doesn't show things like air pockets, but still.

Long story short, I can imagine doing something like this could be somewhat complex, especially without "Offset Collision" conditions that Classic has. And I personally am not sure where to start with something like this, though I would really like to be able to create proper fluid dynamics, even if they're blocky fluids.

So, yeah. Any ideas? I imagine some of you smart fellows might take this request as a challenge, heh.

Edit: Hell, if any of you guys somehow take it one step further and do proper fluid dynamics like in that "Where's my water?" game on the iOS, that would be awesome as well. I'm really curious as to how those developers managed to pull it off. Probably asking a bit much, but, one can hope. <img src="smileys/smiley36.gif" border="0" align="middle">

Oh, yeah, it does. That's why I suggested it. <img src="smileys/smiley4.gif" border="0" align="middle" /> Lemme list the features that are in the Classic version but not in this one...

General Features:

• Predictive aiming
• Being able to have a list of objects as targets
• A reload timer to make it easier to allow for a short amount of time between bullets
• Targeting options: "Follow first in range", or "Always the nearest".

Behaviour settings:

• Reload time
• Target Method (Two options: "Follow first in range", or "Always the nearest")
• Turret Rotation toggle
• Predictive aiming toggle
• Bullet Speed (Used for predictive aiming)

Conditions:

• Is always picking nearest
• Is always picking first in range
• Is using predictive aim
• On Shoot

Actions:

• Acquire Target
• Add Object to target
• Clear targets (clear the whole list, not just one target)
• Set Base Object
• Unaquire Target
• Set Activated
• Set Range
• Set Reload Time
• Set Rotation Enabled
• Set target method
• Set use predictive aim

Mind you, there are some features in the Classic version of the behavior that isn't in this plugin. Maybe you could work on implementing those. Predictive aiming, especially, that would be extremely handy for, say, tower defense games.

You guys might wanna actually check out the cap before you go making suggestions. It's a pure event-driven system that utilizes quite a few sensors.

For reference, I'm gonna toss up my own version of that cap that's a WIP of trying to implement individual working players, complete with picking. My method for picking may not be entirely sound, however, though it does seem to work on my end.

dl.dropbox.com/u/919275/SonicConstructMultiReDo.cap

Just asking out of curiosity, to be perfectly honest. *Shrug*

... I think I phrased that question badly, because I am perfectly aware of that. >>

Speaking of "Else", any reason why the "While" and "On Loop" conditions aren't implemented either?