YesNoOk
avatar

Command move problem (Read 851 times)

Started by AlumDixon, March 28, 2009, 07:57:22 pm
Email this topic
View printable version
Share this topic:
Page 1 of 11   Go Down

AlumDixon

Command move problem
#1  March 28, 2009, 07:57:22 pm
  • **
  • Kung Lao - 70% Almost ready to release!
I'm tryin to make a projectile throw with a certain command.
Here's the code:
[command]
Name = "hatthrow"
Command = ~B,F,x

It don't work though but If I put it like just back front without the ~ it works. I also tried it without the ~
Any help?

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

bushinryu

Re: Command move problem
#2  March 28, 2009, 08:21:06 pm
  • avatar
~ sign means neutral joystick position i think,it may be messing up with this kind of CMD back forward, not but if it is working without the ~ why dont you just leave it like this?

try ~20$B,F,x
(~20$B) = you have to hold back for 2 sec

or just make another cmd for Kung lao hat throw dude

good luck

AlumDixon

Re: Command move problem
#3  March 28, 2009, 08:37:29 pm
  • **
  • Kung Lao - 70% Almost ready to release!
no i mean it back and forward is working without the ~ but doesnt work with it adding x

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Cyanide

Re: Command move problem
#4  March 28, 2009, 09:42:10 pm
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
Lemme guess. A punch comes out instead? Change the order of your changestates. More complex commands, like this one should be above less complex command changestates, like X.

This is detailed in the FAQ as well.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

AlumDixon

Re: Command move problem
#5  March 29, 2009, 01:40:14 am
  • **
  • Kung Lao - 70% Almost ready to release!
Cyanide said, March 28, 2009, 09:42:10 pm
Lemme guess. A punch comes out instead? Change the order of your changestates. More complex commands, like this one should be above less complex command changestates, like X.
This is detailed in the FAQ as well.
Quote from the FAQ. My attack isn't coming out
The .CMD file is read from top to bottom. If you have the changestate for a more complex command occuring after a simple command the simple command will be read in. As such, the complex command will never be read. Order should be complex then simple.


Does that mean i gotta put it at the very top before x?

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Bastard Mami

Re: Command move problem
#6  March 30, 2009, 07:00:09 pm
  • ******
  • [E]
    • Mexico

  • Online
yes

AlumDixon

Re: Command move problem
#7  March 31, 2009, 12:49:15 pm
  • **
  • Kung Lao - 70% Almost ready to release!
weird because the code is on top of x  and all the other single buttons. What else could be wrong?

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Bastard Mami

Re: Command move problem
#8  March 31, 2009, 05:44:54 pm
  • ******
  • [E]
    • Mexico

  • Online
there are two types of code, the par in which you define the command (that one does not matter) and the part where you put the changestate, that's the one in which order matters.

DKDC

Re: Command move problem
#9  March 31, 2009, 07:00:01 pm
  • ******
I wonder if he even gave the correct triggers for the changestate.
If I struggled to the end of my determination, to the end of my way of life with my followers, if the result is ruin, then this ruin is inevitable. Grieve. Shed tears. But you cannot regret.

AlumDixon

Re: Command move problem
#10  March 31, 2009, 08:48:25 pm
  • **
  • Kung Lao - 70% Almost ready to release!
i did because if i put the move as Back and forward, it works perfect but adding a button doesnt.

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

DKDC

Re: Command move problem
#11  March 31, 2009, 08:59:18 pm
  • ******
Then check E's (Frederica's) reply.
If I struggled to the end of my determination, to the end of my way of life with my followers, if the result is ruin, then this ruin is inevitable. Grieve. Shed tears. But you cannot regret.

AlumDixon

Re: Command move problem
#12  April 01, 2009, 05:14:34 am
  • **
  • Kung Lao - 70% Almost ready to release!
Ill just post my full cmd. Might help more.
Spoiler, click to toggle visibilty

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Cyanide

Re: Command move problem
#13  April 01, 2009, 05:26:25 am
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
Quote
[Command]
name = "hatspwn"
command = ~B, F, x
time = 20
Is the more normal way to do it. I shall assume that you've forgotten you deleted the changestate from your CMD before you posted it. As you have been using the move, perhaps you would care to add it back in where it's supposed to be?


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

AlumDixon

Re: Command move problem
#14  April 01, 2009, 05:30:33 am
  • **
  • Kung Lao - 70% Almost ready to release!
i added the ~ line again. The changestate is still there.
[State -1, hatspwn]
type = Changestate
value = 6000
triggerall = command = "hatspwn"
trigger1 = statetype = S
;trigger1 = statetype = S && ctrl
trigger1 = ctrl


Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Bastard Mami

Re: Command move problem
#15  April 01, 2009, 05:51:12 pm
  • ******
  • [E]
    • Mexico

  • Online
slightly unrelated, never use statetype=S or statype =C, normally it's enough to use statetype != A then add a command = holddown check for crouching/standing attacks.

DKDC

Re: Command move problem
#16  April 01, 2009, 07:17:53 pm
  • ******
The ~ only means "release the key". So the command will be recognized when you
-hold (for as long as you want) or just press back
-release the back direction
-hit fwd
-hit x
in that order.

Quote
The changestate is still there.
... Where "here" ? You put it in the middle of the taunt, after the block that goes
Quote
;Stand Light Punch
;—§‚¿Žãƒpƒ“ƒ`
[State -1, Stand Light Punch]
type = ChangeState
value = 200
triggerall = command = "x"
triggerall = command != "holddown"
trigger1 = statetype = S
trigger1 = ctrl
trigger2 = stateno = 200
trigger2 = time > 6
Mugen reads from top to bottom.
If you press back, forward, x, it will start reading the cmd file, find the block I just quoted, figure that you just pressed x, execute it, and never read the block that has
Quote
;Taunt
[State -1, Taunt]
type = ChangeState
value = 195
triggerall = command = "start"
trigger1 = ctrl
;Hat
[State -1, hatspwn]
type = ChangeState
value = 6000
triggerall = command = "hatspwn"
trigger1 = statetype = S
;trigger1 = statetype = S && ctrl
trigger1 = ctrl
because that block is after the previous one.
Move the hatspwn block above the "Stand Light Punch" block.
If I struggled to the end of my determination, to the end of my way of life with my followers, if the result is ruin, then this ruin is inevitable. Grieve. Shed tears. But you cannot regret.
Last Edit: April 01, 2009, 07:23:08 pm by Byakko

AlumDixon

Re: Command move problem
#17  April 01, 2009, 09:20:30 pm
  • **
  • Kung Lao - 70% Almost ready to release!
holy fk it works. Thx very much. I thought i had to move the actual command for the buttons to get it right not the code of the change state. Thx again

Making Stick Figures in MS Paint is Fun....
Continuing Kung Lao =]

Cyanide

Re: Command move problem
#18  April 02, 2009, 08:03:09 am
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
Sigh, i missed the hat throw changestate.

Disappointing that what you've now done to make it work is what we've been telling you to do the whole thread and what's in the FAQ

Quote
My attack isn't coming out
The .CMD file is read from top to bottom. If you have the changestate for a more complex command occuring after a simple command the simple command will be read in. As such, the complex command will never be read. Order should be complex then simple.

As it seems this never penetrated properly, how would you advise it's reworded to be more understandable?


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

DKDC

Re: Command move problem
#19  April 03, 2009, 12:19:30 am
  • ******
This is the problem
alum2 said, March 31, 2009, 12:49:15 pm
weird because the code is on top of x  and all the other single buttons. What else could be wrong?
(he was only looking at the first part, it should be specified it's the statedef -1 that matters) And it's xhat E said afterward, this should have been the solution
Frederica Bernkastel~ said, March 31, 2009, 05:44:54 pm
there are two types of code, the par in which you define the command (that one does not matter) and the part where you put the changestate, that's the one in which order matters.
And I pointed it out again afterward too
Byakko said, March 31, 2009, 08:59:18 pm
Then check E's (Frederica's) reply.
So don't worry, the problem isn't you, it's alum2 who really didn't get it :P
If I struggled to the end of my determination, to the end of my way of life with my followers, if the result is ruin, then this ruin is inevitable. Grieve. Shed tears. But you cannot regret.
Page 1 of 11   Go Up