Move Buffer

Started by Guillier, December 01, 2009, 04:12:22 PM

Previous topic - Next topic

Guillier

Heya everyone.
I have a question and i need help.
It's a move i've seen from DIO of warusaki where he goes into super move with a pause then, at that point, you have to press buttons and dio will perform the moves later on after the pause.
How do i make that move?
How do i make a buffer of attack moves during pause and perform it later afterward?

kakkoii superhero

#1
I think , your move command would need to be stored as variable (by pressing the command you set a var)
and that variable would be used as a trigger for the followup.

Cyanide

pause has a buffer parameter that stores a limited number of commands (1) after the pause. The .cmd also takes a buffer.time parameter. How many moves does Dio perform. 1, or a large number based on how many commands you entered?


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.

aokmaniac13

It's the tandem attack, you can input up to 40 moves to do during the pause, and then his stand will perform them in order after the pause.
The player is free to do whatever he wants while the stand does its thing.

http://www.youtube.com/watch?v=LHcs_iCuKVk
Here's a video of that.

PotS

(If only I had a nickle for each time that guy did that on me. ;P)
You can help with Ikemen GO's development by trying out the latest development build and reporting any bugs on GitHub.
My Mugen and Ikemen content can also be found here.

Cyanide

Up to 40? Good grief. In the sequence you entered them? Same move more than once? You're going to need a helper to manage this. You're going to need a variable that counts how many moves have been performed. You're going to need variables that store EACH move and some sort of linker to say where within the sequence that move has been performed.

I'm thinking each state can be accessed by a specific variable range and the var itself places it in the queue

var(24) = 3400

state 3400, 24th move entered. Upon entering said state your counter variable is decreased by one. You really do need a spare helper for this though. I wouldn't want to bet on a stand not making use of some of your 40 variables. Unique variable's also are classed as "Off" when they = 0 or, if that's actually made use of in some manner -1. The player will no longer change check the variable if it's -1.

Ugh, that's awkward and annoying. state change = var(number-var(counter)) > 0 or something. I have my math wrong there though.


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.

aokmaniac13

I say up to 40 because theoretically the pause is long enough to input 40 commands although it is not humanly possible.

Blame KFM for figuring that out.

Cyanide

So you could probably cut it down to 10-15, that's still rather a decent variable chunk


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.

Guillier

#8
Quote from: Insanius on December 01, 2009, 09:48:20 PM
It's the tandem attack, you can input up to 40 moves to do during the pause, and then his stand will perform them in order after the pause.
The player is free to do whatever he wants while the stand does its thing.

http://www.youtube.com/watch?v=LHcs_iCuKVk
Here's a video of that.

That's it.
That was the move i was talking about.
But the one that will do it is the player himself instead of stand.
Can't figure out how to do it.
I gotta think.

Quote from: Cyanide on December 01, 2009, 11:51:31 PM
Up to 40? Good grief. In the sequence you entered them? Same move more than once? You're going to need a helper to manage this. You're going to need a variable that counts how many moves have been performed. You're going to need variables that store EACH move and some sort of linker to say where within the sequence that move has been performed.

I'm thinking each state can be accessed by a specific variable range and the var itself places it in the queue

var(24) = 3400

state 3400, 24th move entered. Upon entering said state your counter variable is decreased by one. You really do need a spare helper for this though. I wouldn't want to bet on a stand not making use of some of your 40 variables. Unique variable's also are classed as "Off" when they = 0 or, if that's actually made use of in some manner -1. The player will no longer change check the variable if it's -1.

Ugh, that's awkward and annoying. state change = var(number-var(counter)) > 0 or something. I have my math wrong there though.

That was a nice idea.
But, I don't have any idea how do i make my character move afterwards.
Like while on the "Pause".
Lets say, I press X(state 200), Y(state 210), Z(state 220).
Then afterward, my character will change to those states respectively.
Yeah. It's really somewhat awkward but a good stuff in addition to a character.
I wonder how can I do It.
Really need a help.  ???

I'm wondering also about the "Pause sctrl".

endcmdbuftime = bt (int)

This is the number of ticks during the end of the pause in which the player's move commands will be buffered. Buffered
commands will be detected by the "command" trigger immediately after the pause ends. The buffering applies only to
players who are unable to move during the pause (see movetime parameter). Valid values for endcmdbuftime are from 0
to t, where t is the value of the time parameter. Defaults to 0.



It's like what I'm talking about.
But I'm kinda confused about the "The buffering applies only to players who are unable to move during the pause".
Wasn't that the enemy who's unable to move during the pause?


Cyanide

You're not worried about parameters in the pause any more.

Each time you do a command, you increment a variable by 1. And set a specific variable to the value of the attack it's going to.

After the "pause" is over just use a changestate to the variable that's been set while your counter is greater than 0.

In this case, cos it's a large number of var's. I'd have a helper to record them and the parent using redirection to work out what var's he needs. This is a short example.

Say you've pressed 4 commands and have 4 states to run through

parent, command1 = var(1) = 200
parent, command2 = var(2) = 210
parent, command3 = var(3) = 220
parent, command4 = var(4) = 1000

counter = 4

changestate
counter > 0
value = var(1)

changestate
counter > 0
value = var(2)

Needs more tweaking than that and i'd have to actually do it to iron out the bugs.



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.