? What's hard about that ?
Create a helper to display the panel, and then... well how do you move around and how do you pick up which command to do ? Have the panel detect the parent's commands to... I don't know, what does the panel do, move around, highlight the various commands ? Then have the parent react to the action determined by his helper (the panel).

First figure out EXACTLY the DETAILS of WHAT you want to do, and then translate that to code. You can't do much if you don't know exactly WHAT you want to do. You can't just say "I want the same thing as in this game" if you don't know everything about how that game works. What does your panel do ? How does it react to your key inputs ? How does your character react to your key inputs ? How do the actions of the character relate to the panel's situation ? Make sure yo know all that.

Now...Seems to be working perfectly in the vid...But Attacking isnt triggered off of where the cursor is placed..Anyone know how to make it so that it is?

Quote

I thought that was already established.... I said that already...

And I said already what you needed to do for that. And yet you keep saying the same thing. So what, did you not read what I was telling you to do ? You rather keep telling us the same thing and act like we weren't reading you the first time around ? If you didn't understand, why don't you say it ?
The helper checks the parent's commands and selects the right action according to your direction inputs.
When you press a button, in your cmd file, you check what the helper is currently selecting, and then you make a changestate depending on that. What else do you want ? This is as clear as it can be. What do you not understand in that ? If you don't know how to do it, can't you say it instead of acting like that ?

[mcode]type = Helper[/mcode]Create a helper, create a statedef to start the helper at. In that statedef, you display the panel's animations.
In the helper's state, you dedicate a variable to the current position of the arrow. Helpers have their own sets of variables separated from the character's, so you don't worry about that.
Still in the helper's state, you constantly check for the parent's command (with trigger redirection). If the parent (your character, i.e. yourself) presses up or down, you change the helper's variable accordingly.
When you press a button and you have control and everything, you also add a trigger that looks for the current value of the helper's variable (trigger redirection again). And so you can make the changestate to whatever action you want. If the helper's variable says the panel is pointing at "attack", then you have the changestate send you to the attack state, and so on.

If there is anything (something specific) in this that you don't understand in this or don't know how to do, you should say it (and have a look at the docs if you don't find something about it if you look for the right keywords, I believe what I say up here should give you enough of these keywords to find info about it in the docs).

Helpers work exactly the same way as the character, they go through statedefs the same way as the character.
The variable for the helper is used to know what the cursor is currently highlighting. Say, if var(1) = 1, you declare that "attack" is highlighted. If var(1) = 2, it's "magic".
In your cmd, you make the changestate triggered by the key press - adding the trigger "helper([the ID of your helper]),var(1) = 1" because you know that "attack" is highlighted if the helper's var(1) is 1.

Quote

but how do I make it so that it checks where The parent is...?

What do you mean by "where the parent is" ? Your character creates a helper. So the helper is the panel, and the panel's parent is the character - that is, you. So you have two "objects", the character and the helper. The panel is the one that knows what is currently highlighted.

Nope, that's bad.

With your current state, (entered with Y) create a helper. Changestate out when it's released, as you had previously. Create a SECOND state for the helper.

Enter all your previous code there.

Also add the following to make things simple

[state parentvarset]
type = parentvarset
trigger1 = 1
v = 0
value = var(0)

We don't need to fuck round with redirects that way. Once you have THAT.

Lets invent some values. Attack is highlighted. Your var(0) = 0. All attacks that  are allowed when attack is highlighted are triggered normally but you add

triggerall = var(0) = 0 to them as well, this is in your .cmd file.

I preferred your previous one due to simplicity. But as we're onto helpers now we may as well stick with them.

Is var(0) = 2 when you have magic selected? As you're making use of var(0) = 0, you're probably using var(0) = 1 for magic.