Yeah, x is simply a stand in for a variable of your choosing. For example, you could use:

(sin((time * 1000) + 270) + 1) * 49.5 + 1

Alternatively, if you want the silky smoothness of sine, you could just set your variable to:

(sin(x + 270) + 1) * 49.5 + 1

This is intended - you may have cases where you want to interact with an invisible object. Just check if your object is visible in the click event if you want to avoid interacting with it when it's not.

No problem, man - let me know if you run into anymore problems.

I had some suspicions that your problems were caused by incorrectly placed hot spots and that is indeed the case.

Your 'PainBox' object has a hot spot that is far right of center, resting in a position such that - given that the X and Y coordinates represent this point - your player's position will always be left of X relative to that object. Centering the hot spot on the 'PainBox' will fix your knock back problems.

For the health bar, your hot spot is once again out of alignment based on the effect you want. Placing the health bar's hot spot on the left edge of the image will result in the image extending towards the right relative to the hot spot, just as you want.

As a nifty little trick - which you may already know - while editing hot spots in the image editor, you can use the number pad on your keyboard to quickly position it to the edges/center/corners of your image. So, for example, 4 sets it to the left edge, vertically centered; 5 to the center; etc.

I hope all of this helps you out. <img src="smileys/smiley4.gif" border="0" align="middle" />

Well, I can tell you how to fix number 3. For each frame the player's health is equal to zero it will keep resetting the "Death" animation over and over again which means it never finishes - adding a "Trigger once while true" condition after the health check condition in event 6 should fix that by making the event run once.

I can't be sure what's wrong in the first two cases - I have no context for what the objects are or how they're set up. If you provide your CAP file I'll be glad to look at it and help you out.

I'll just mention that setting the X position of HealthBar won't do anything as HealthBar.X and your 'Location' variable are equal without changing.

I waited two solid minutes for it load on my Playbook but it never left the white screen - I'm running OS2.1.

This all comes down to an issue of reflexes - it's difficult to hold down a key for a single frame, thus the key may remain held for an additional one or two frames unintentionally causing unwanted movement.

My solution

I introduced a three frame timer into the equation to solve the problem. By moving once upon a key first being pressed, then utilizing a timer to delay movement a few frames before resuming movement, you can now move one pixel at a time and yet still move with a largely imperceptible input delay.

I hope this helps. :)

If you post a CAP file, I can check it out and see what's going on.

Whoops, sorry I missed this - let's see what I can do for ya.

Unfortunately I'm not sure I can answer your question about the link error - however, If I remember correctly, the 8 direction movement is working off a much older version of the SDK, and I believe some dependencies changed along the way, so that's probably the likely culprit.

As for question two, I actually needed something similar for my gravitation behavior. What I'd suggest is adding a static CRunObject* to your class declaration in Main.h after the ACE function declarations. In Runtime.cpp you'll have to define it - I have it after the #ifdef RUN_ONLY line.

Main.h:

////////////////////////////////////////////////////
// Data members

// Use when private variables (OF_PRIVATEVARIABLES) are enabled.
//vector<ExpStore> privateVars;

// Initialize the vector of object pointers for accessing data across objects
static CRunObject* playerObject;

//////////////////////////////////////////////////////////////////////////////////
// Runtime functions
//////////////////////////////////////////////////////////////////////////////////
#ifdef RUN_ONLY

CRunObject* ExtObject::playerObject;

The difference is mostly in how they're setup - in "Main.h" there's a line near the top that starts with:

#define IDE_FLAGS

#define IDE_FLAGS OF_MOVEMENTPLUGIN

#define IDE_FLAGS OF_MOVEMENTPLUGIN | OF_NODRAW

pLink->info.x

this->info.x

The source for quite a few of the built in behaviors can be found on the Construct Classic SVN. Source for many of the plugins is also up there. In addition, here's a basic plugin tutorial from the old wiki.

It's recommended that you have a basic working knowledge of C++ to work with the SDK - not that I let that stop me. <img src="smileys/smiley17.gif" border="0" align="middle">

If you have any specific questions on how things work, go ahead and ask - there should still be a few people around here who can help you out, myself included.