The Mugen Fighters Guild - Let's update Kung Fu Man

Vans

Re: Let's update Kung Fu Man

#161 February 24, 2017, 10:18:48 am

I fully agree, Iced. It is far more productive to spend this time writing a tutorial or solving another problem instead of arguing whether Japanese one-liners would pass a professional code review or not.

I am not angry and I never insulted anybody. However, I do want to point out that a Mugen Guild administrator calling my code unreadable or littered in public before asking me a question directly is not exactly right, either. We are all role models here, a voice giving out such a strong statement and judgement regarding a piece of code can scare people away from attempting to use it or read it, this goes against the "sharing" aspect of this forum.

If you want to give me pointers on how to present my code better, then by all means, I made a topic purely dedicated to the reflector and it has exactly 0 replies in it.

I'm trying my best to produce notes in 3 languages so that it is easier for people to follow, the code itself is already easier than most code shared and produced 5 or 7 years ago. Go a little easier on me, I again plead you to see it from my point of view.

This is a wip topic for Kung Fu Man, so let's not derail it any further.

Last Edit: February 24, 2017, 11:52:15 am by Vans

XGargoyle

Re: Let's update Kung Fu Man

#162 February 24, 2017, 10:24:34 am

Hedgehog Whisperer
Red Bull addict

XGargoyle: Battle posing since 1979
http://xgargoyle.mgbr.net
http://www.pandorabots.com/pandora/talk?botid=e71c0d43fe35093a <-- Please click that link
http://paypal.me/XGargoyle <-- Donations welcome!

JustNoPoint

Re: Let's update Kung Fu Man

#163 February 24, 2017, 02:02:43 pm

Vans, I really wanted to drop this. I was being pedantic about your phrasing that everything was noted and easy to apply. And I never said your code was unreadable in fact I said I read the code to figure out what went where. I couldn't read the Japanese labels so instead of instantly knowing a state wasn't needed I had to be sure by following the state paths. That are spread through the reflector states.

I'd rather you stop making it an issue that I thought it was more difficult than you had implied. What I said was accurate to how I felt but I apologized. I don't expect an apology but I'd rather you not keep on painting me as someone trying to hurt your image by me stating something with facts.

You said it was all noted and easy to apply. Obviously you didn't mean that to the degree I thought you did. Likewise you're making what I said too big of a deal too. I may be admin but I'm also a learning creator trying to make things easier for others. I only wanted assistance adding more notes and to be sure I only added the essentials. I had no idea mentioning it was slightly tougher to read would be an issue.

Jesuszilla

Re: Let's update Kung Fu Man

#164 February 24, 2017, 04:23:23 pm

Loyal to the Game

Vans isn't the one making it an issue, Iced is. That's who Vans was replying to, not you. I thought you two settled it pages ago, so I'm confused as to why you're replying like that, JNP.

JustNoPoint

Re: Let's update Kung Fu Man

#165 February 24, 2017, 04:26:56 pm

Vans said, February 23, 2017, 06:26:20 pm

Try to see it from my point of view. I was just sitting trying to study for an article I have to write for college and then I see someone with a big voice calling my code unreadable. :/

Vans said, February 24, 2017, 10:18:48 am

However, I do want to point out that a Mugen Guild administrator calling my code unreadable or littered in public before asking me a question directly is not exactly right, either. We are all role models here, a voice giving out such a strong statement and judgement regarding a piece of code can scare people away from attempting to use it or read it, this goes against the "sharing" aspect of this forum.

I thought he was reiterating this again for some reason.

JustNoPoint

Re: Let's update Kung Fu Man

#166 February 24, 2017, 07:41:51 pm

Anyway, I got it all finished and notated. I think it's pretty clear now. Feel free to add to it or make corrections.

Spoiler: Kung Fu Zankou (click to see content)

Code:

;The Kung Fu Zankou will teach you how to properly make a move that acts as a projectile reflector
;See State 1500 for details on the actual projectile

;---------------------------------------------------------------------------
; Light Kung Fu Zankou
; CNS difficulty: easy
[Statedef 1400]
type    = S
movetype= A
physics = N
juggle  = 4
poweradd= 50
velset = 0,0
anim = 1400
ctrl = 0
sprpriority = 2

[State 1400, 1]
type = PlaySnd
trigger1 = AnimElem = 3
value = 0, 3

[State 1400, Friction]
type = VelMul
trigger1 = 1
x = 0.5

;---------------------------------------------------
;This helper will act as a reflector
[State 1400: Helper]
type = helper
trigger1 = !NumHelper(1435);use this trigger so the helper will not be created multiple times in 1 move
trigger1 = AnimElem = 4
id = 1435
pos = 0,0 ;50
postype = p1
facing = 1
stateno = 1435
keyctrl = 0
ownpal = 1
supermovetime = 0
pausemovetime = 0
persistent = 0
;---------------------------------------------------

[State 1400, 2]
type = HitDef
trigger1 = Time = 0
attr = S, SA
animtype  = Hard
damage    = 100, 6
priority  = 4
guardflag = MA
pausetime = 12,12
sparkxy = 0,-65
hitsound   = 5,3
guardsound = 6,0
ground.type = Low
ground.slidetime = 12
ground.hittime  = 17
ground.velocity = -9
ground.cornerpush.veloff = -15 ;To push far away when p2 is in corner
guard.velocity = -9
air.velocity = -2,-5
airguard.velocity = -3.5,-4.5
air.fall = 1

[State 1400, 3]
type = PosAdd
trigger1 = AnimElem = 2
trigger2 = AnimElem = 3
trigger3 = AnimElem = 4
x = 10

[State 1400, 4]
type = VelSet
trigger1 = AnimElem = 4
x = 2

[State 1400, 5]
type = PosAdd
trigger1 = AnimElem = 8
x = 10

[State 1400, 6]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

Spoiler: Reflector Helper (click to see content)

Code:

;---------------------------------------------------------------------------
;This is the helper created in Kung Fu Zankou
;this state sets a sysvar that the projectile "talks" to and destroys
;---------------------------------------------------------------------------
;Reflector Helper 
; CNS difficulty: hard
[Statedef 1435]
type = S
movetype = A
physics = N
ctrl = 0
velset = 0, 0
anim = 1430
sprpriority = 4

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR REFLECTOR / 飛び道具を跳ね返するHELPERで	;
;sysvar(0) = 262144　　                	;
;=======================================;
[State 1435, COMPATIBILITY]
type = VarSet
trigger1 = !time && !prevstateno
sysvar(0) = 262144
;=======================================;

[State 1435, REFLECTOR]
type = ReversalDef
trigger1 = time = 0
reversal.attr = SCA,NP,SP,HP
pausetime = 0,0
sparkno = -1
sparkxy = 0,0
p1stateno = 1436
p2stateno = 1437
id = 1435
numhits = 0

[State 1435, projs only]
type = HitBy
trigger1 = 1
value = SCA, NP, SP, HP
ignorehitpause = 1

[State 1435, override]
type = HitOverride
trigger1 = !time
attr = SCA, AA, AP, AT
stateno = 1436
time = -1
ignorehitpause = 1

[State 1435]
type = BindToParent
trigger1 = 1
pos = 0,0
ignorehitpause = 1

[State 1435, Assert];redundant since it wouldn't cast a shadow anyway because there is no sprite in anim 1430. You'd want this if they used an energy shield to reflect
type = AssertSpecial
trigger1 = 1
flag = noshadow
ignorehitpause = 1

[State 1435, DestroySelf]
type = DestroySelf
trigger1 = root, StateNo = [1400,1420]
trigger1 = root, AnimElemTime(5) >=0
trigger2 = root, MoveType = H

Spoiler: Successful Reflection (click to see content)

Code:

;---------------------------
;Successful Reflection
[Statedef 1436]
type = S
movetype = I
physics = N
ctrl = 0
velset = 0, 0
anim = 1
sprpriority = 4

[State 1436, VarSet]
type = VarSet
trigger1 = numtarget
var(0) = target,ID
persistent = 0
ignorehitpause = 1

[State 1436, DEBUG]
type = DisplayToClipboard
trigger1 = 1
text = "var(0) = %d proj = %d ID = %d";Buff = %d GNDTYPE = %d"
params = var(0),numprojid(262144),gethitvar(chainid)
ignorehitpause = 1

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR PROJECTILE / 飛び道具で              	;
;sysvar(0) = 131072                     ;
;sysvar(1) = REFLECTED_BEHAVIOR_STATE   ;
;FOR REFLECTOR / 飛び道具を跳ね返するHELPERで	;
;sysvar(0) = 262144　　                   ;
;sysvar(1) = SPECIAL                    ;
;=======================================;
[State 1436, VarSet]
type = VarSet
;RETURNING YOUR OWN PROJECTILE
;自分の飛び道具を跳ね返す。
trigger1 = Gethitvar(chainid)&2**17
sysvar(1) = sysvar(0)
[State 1436, ChangeState]
type = ChangeState
trigger1 = PlayerIDExist(var(0))
trigger1 = (PlayerID(var(0)),sysvar(0)=131072) 
;RETURNING YOUR OWN PROJECTILE
;自分の飛び道具を跳ね返す。
trigger2 = Gethitvar(chainid)&2**17
value = 1441
ctrl = 0
;=======================================;

[State 1436, DestroySelf]
type = DestroySelf
trigger1 = time = 30

Spoiler: Reflecting A Helper projectile (click to see content)

Code:

;---------------------------
;Reflecting A Helper projectile
[Statedef 1437]
physics = N
movetype = I
ctrl = 0

[State 1437, DEBUG]
type = DisplayToClipboard
trigger1 = 1
text = "sysvar(0) = %d pao pao cafe = %d";Buff = %d GNDTYPE = %d"
params = sysvar(0),sysvar(0)&2**17
ignorehitpause = 1

[State 1437]
type = SelfState
trigger1 = sysvar(0)&2**17
value = sysvar(1)
ctrl = 0

[State 1437]
type = DestroySelf 
trigger1 = IsHelper
trigger1 = time = 5
ignorehitpause = 1

[State 1437]
type = SelfState
trigger1 = !IsHelper
value = 0
ctrl = 1

[State 1437, Anim]
Type = ChangeAnim2
Trigger1 = !Time
Value = 1 ;don't forget to add this anim to your .air -1,-1, 0,0, 1
;the anim number does not have to be 1

Spoiler: Special Reflection (click to see content)

Code:

;---------------------------
;Special Reflection
[Statedef 1441]
type = S
movetype = A
physics = N
ctrl = 0
velset = 0, 0
sprpriority = 5

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR REFLECTOR / 飛び道具を跳ね返するHELPERで	;
;sysvar(0) = 262144　　                	;
;=======================================;
[State 1441, INFORMATION SHARING] 	;
type = Projectile 			;
trigger1 = sysvar(1)&2**18 		;
projid = sysvar(0)			;
projanim = 1			;
projhitanim = -1			;
projremanim = -1			;
projremovetime = 2			;
projscale = 0,0			;
projpriority = 0			;
velocity = 0,0			;
postype = p1			;
offset = 0,0			;
persistent = 0			;
ignorehitpause = 1			;
;=======================================;

[State 1441, ChangeAnim]
type = ChangeAnim
trigger1 = !time
value = 1

[State 1441, StateTypeSet]
type = StateTypeSet
trigger1 = root,movetype = H
trigger2 = cond(PlayerIDExist(var(0)),(PlayerID(var(0)),movetype=I),0)
movetype = I        ;I,A,H

[State 1441, PosSet]
type = PosSet
trigger1 = !time || time
trigger1 = PlayerIDExist(var(0))
x = PlayerID(var(0)),Pos X
y = PlayerID(var(0)),Pos Y

[State 1441, DestroySelf]
type = DestroySelf
trigger1 = time > 2
trigger1 = !PlayerIDExist(var(0))

Spoiler: Board Throw (click to see content)

Code:

;---------------------------------------------------------------------------
; Board Throw
; CNS difficulty: easy
;in this state we learn how to make your character throw a projectile
;Helpers are the best way to create a projectile
;the actual Projectile controllers are far too limited
[Statedef 1500]
type    = S
movetype= A
physics = S
poweradd= 60
velset = 0,0
anim = 1500
ctrl = 0
sprpriority = 2

[State 1500, Button Detect]
type = VarSet
trigger1 = !Time && !AILevel
var(2) = cond((command = "Board Throwx"), 0, 1);this sets the var depending on button pressed when using the move

[State 1500, 1]
type = PlaySnd
trigger1 = AnimElem = 3
value = 0, 4

;This is the helper that we use for the projectile. In this case a solid piece of wood
[State 1500, Helper]
type = Helper
trigger1 = AnimElem = 3
name = "Board"
ID = 1510
stateno = 1510
pos = 20,-60
postype = p1    ;p2,front,back,left,right
facing = 1
ownpal = 1

[State 1500, 6]
type = ChangeState
trigger1 = AnimTime = 0
value = 0
ctrl = 1

Spoiler: Board Projectile Helper (click to see content)

Code:

;---------------------------------------------------------------------------
; Board Projectile Helper
; CNS difficulty: hard
[Statedef 1510]
type    = A
movetype= A
physics = N
;juggle  = 6 Note that if you actually use juggle points for the helper they will only add to the helper's juggle points. Not the root's (KFM's)
anim = 1510
ctrl = 0
sprpriority = 5
hitcountpersist = 1
movehitpersist = 1

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR PROJECTILE / 飛び道具で              	;
;sysvar(0) = 131072                     ;
;sysvar(1) = REFLECTED_BEHAVIOR_STATE   ;
;=======================================;
[State 1510, COMPATIBILITY]
type = VarSet
trigger1 = !time 
sysvar(0) = 131072
[State 1510, REFLECTED STATE]
type = VarSet
trigger1 = !time
sysvar(1) = 1520 ; use the stateno your reflected projectile is located at
;If you do NOT wish for the projectile to be reflected then set it back to the original projectile state
;in this case 1510
;=======================================;

;IF this was a fireball you would use this. As a piece of wood we will allow it to cast a shadow
;[State 1510, NoShadow]
;type = AssertSpecial
;trigger1 = 1
;flag = noshadow
;ignorehitpause = 1

[State 1510, Button Detect]
type = VarSet
trigger1= !Time && !PrevStateNo
var(2) = Root, var(2) ;sets the helper var to be the same as the root's var

[State 1510, VelSet]
type = VelSet
trigger1 = Time >= 0
x = Cond(var(2) = 1, 6,3) ;If Var(2) is 1 then this moves faster, if not 1 it moves slower
y = 0

[State 1510, Velocity]
type = VelSet
trigger1 = Movecontact ;stop moving when the board connects
x = 0
y = 0

[State 1510, NotHitBy]
type = NotHitBy
trigger1 = Time >= 0
time = 1
value = SCA, NA, SA, HA, NT, ST, HT ; The helper can't be hit by anything except Projectiles
ignorehitpause = 1

[State 1510, HitBy]
type = HitBy
trigger1 = Time >= 0
value = SCA, NP, SP, HP ; Only Projectiles will hit. This allows other projectiles to destroy this one
time = 1
ignorehitpause = 1

[State 1510, HitOverride]
type = HitOverride
trigger1 = Time >= 0
slot = 1
time = 1
stateno = 1511   ; when hit the Projectile will go to this state. It's destroyed state
attr = SCA, AA, AP, AT
ignorehitpause = 1

[State 1510, Hitdef]
type = HitDef
trigger1 = AnimElem = 1
id = 1510 ;set as same as stateno
attr = A, SP ; VERY IMPORTANT always remember to set your attr to NP, SP, or HP (Normal, Special, Hyper Projectile)
animtype  = hard
damage    = ceil(ifElse(root,fvar(11) * 20 < 7, 7, root,fvar(11) * 20)), 0
priority  = 4,Hit
guardflag = MA
hitflag = MAF
pausetime = 0,10
sparkxy = 0,0
hitsound   = 5,2
guardsound = 6,0
ground.type = high
air.type = low
ground.slidetime = 16 ;20
ground.hittime  = 16 ;20
ground.velocity = -7.8,0
guard.velocity = -7.5
air.velocity = -5.8,-3
airguard.velocity = -5, -4
envshake.time = 5
envshake.ampl = 4
envshake.freq = 176
fall.envshake.time = 10
fall.envshake.ampl = 4
fall.envshake.freq = 176
yaccel = 0.5
air.fall = 0
fall.recover = 1
ground.cornerpush.veloff = 0
air.cornerpush.veloff = 0
down.cornerpush.veloff = 0
airguard.cornerpush.veloff = 0
guard.cornerpush.veloff = 0
getpower = cond(p2movetype=H,40,140), 10 ; if P2 already in a hit state you get less power from hitting them
givepower = 35,35

[State 1510, Guardshake]
type = envshake
trigger1 = moveguarded
time = 4
ampl = 6
freq = 176
ignorehitpause = 1

[State 1510, Fade]
type = changestate
trigger1 = movecontact ;destroyed state
value = 1511
ignorehitpause=1

[State 1520, End];this destroys the projectile when it goes too far
type = DestroySelf
trigger1 = pos x != [-200,200]

Spoiler: DESTROY Board Projectile Helper (click to see content)

Code:

;---------------------------------------------------------------------------
; DESTROY Board Projectile Helper
; CNS difficulty: easy
[Statedef 1511]
type    = A
movetype= A
physics = N
anim = 1511
ctrl = 0
sprpriority = 5

;[State 1511, NoShadow]
;type = AssertSpecial
;trigger1 = 1
;flag = noshadow

[State 1511, Snd 1]
type = PlaySnd
trigger1 = !Time
value = F5,2
[State 1511, Snd 1]
type = PlaySnd
trigger1 = Time = 3
value = F5,3

[State 1511, DestroySelf]
type = DestroySelf
trigger1 = p2movetype != H
trigger1 = time >= 27         ;This destroys the projectile when time = 27 which is the end of the board break animation. But ONLY when P2 is NOT in a hit state. While in a hit state this will stay on the final frame so any hits that follow will add to the combo counter

Spoiler: REFLECTED Board Projectile Helper (click to see content)

Code:

;---------------------------------------------------------------------------
; REFLECTED Board Projectile Helper
; CNS difficulty: hard
[Statedef 1520]
type    = A
movetype= A
physics = N
;juggle  = 6 Note that if you actually use juggle points for the helper they will only add to the helper's juggle points. Not the root's (KFM's)
anim = 1510
ctrl = 0
sprpriority = 5
hitcountpersist = 1
movehitpersist = 1

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR PROJECTILE / 飛び道具で              	;
;sysvar(0) = 131072                     ;
;sysvar(1) = REFLECTED_BEHAVIOR_STATE   ;
;=======================================;
[State 1520, COMPATIBILITY]
type = VarSet
trigger1 = !time 
sysvar(0) = 131072
[State 1520, REFLECTED STATE]
type = VarSet
trigger1 = !time 
sysvar(1) = 1510 ; Use the StateNo you use to fire your projectile
;=======================================;

[State 1520, Turn];turn the projectile around
type = Turn
trigger1 = !time

;IF this was a fireball you would use this. As a piece of wood we will allow it to cast a shadow
;[State 1061, NoShadow]
;type = AssertSpecial
;trigger1 = 1
;flag = noshadow
;ignorehitpause = 1

[State 1520, VelSet]
type = VelSet
trigger1 = Time >= 0
x = Cond(var(2) = 1, 6,3) ;If Var(2) is 1 then this moves faster, if not 1 it moves slower
y = 0

[State 1520, Velocity]
type = VelSet
trigger1 = Movecontact ;stop moving when the board connects
x = 0
y = 0

[State 1520, NotHitBy]
type = NotHitBy
trigger1 = Time >= 0
time = 1
value = SCA, NA, SA, HA, NT, ST, HT ; The helper can't be hit by anything except Projectiles
ignorehitpause = 1

[State 1520, HitBy]
type = HitBy
trigger1 = Time >= 0
value = SCA, NP, SP, HP ; Only Projectiles will hit. This allows other projectiles to destroy this one
time = 1
ignorehitpause = 1

[State 1520, HitOverride]
type = HitOverride
trigger1 = Time >= 0
slot = 1
time = 1
stateno = 1511   ; when hit the Projectile will go to this state. It's destroyed state
attr = SCA, AA, AP, AT
ignorehitpause = 1

[State 1520, Hitdef]
type = HitDef
trigger1 = AnimElem = 1
affectteam = F ; This makes the projectile hurt your own team/char
;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定                   ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR PROJECTILE / 飛び道具で              	;
;sysvar(0) = 131072                     ;
;sysvar(1) = REFLECTED_BEHAVIOR_STATE   ;
;=======================================;
id = sysvar(0)
;=======================================;
attr = A, SP ; VERY IMPORTANT always remember to set your attr to NP, SP, or HP (Normal, Special, Hyper Projectile)
animtype  = hard
damage    = ceil(ifElse(root,fvar(11) * 20 < 7, 7, root,fvar(11) * 20)), 0
priority  = 4,Hit
guardflag = MA
hitflag = MAF
pausetime = 0,10
sparkxy = 0,0
hitsound   = 5,2
guardsound = 6,0
ground.type = high
air.type = low
ground.slidetime = 16 ;20
ground.hittime  = 16 ;20
ground.velocity = -7.8,0
guard.velocity = -7.5
air.velocity = -5.8,-3
airguard.velocity = -5, -4
envshake.time = 5
envshake.ampl = 4
envshake.freq = 176
fall.envshake.time = 10
fall.envshake.ampl = 4
fall.envshake.freq = 176
yaccel = 0.5
air.fall = 0
fall.recover = 1
ground.cornerpush.veloff = 0
air.cornerpush.veloff = 0
down.cornerpush.veloff = 0
airguard.cornerpush.veloff = 0
guard.cornerpush.veloff = 0
getpower = cond(p2movetype=H,40,140), 10 ; if P2 already in a hit state you get less power from hitting them
givepower = 35,35

[State 1520, Guardshake]
type = envshake
trigger1 = moveguarded
time = 4
ampl = 6
freq = 176
ignorehitpause = 1

;=======================================;
;PROJECTILE REFLECTION COMPATIBILITY    ;
;飛び道具を跳ね返し行動設定               ;
;by Vans                                ;
;GUIDE:                                 ;
;FOR PROJECTILE / 飛び道具で          	;
;sysvar(0) = 131072                     ;
;sysvar(1) = REFLECTED_BEHAVIOR_STATE   ;
;FOR REFLECTOR / 飛び道具を跳ね返するHELPERで;
;sysvar(0) = 262144　　                  ;
;=======================================;
[State 1520, Turn]
type = Turn
trigger1 = movecontact
trigger1 = root,NumProjID(262144)
persistent = 0
ignorehitpause = 1
[State 1520, ChangeState]
type = ChangeState
trigger1 = movecontact
trigger1 = root,NumProjID(262144)
value = sysvar(1)
ctrl = 0
ignorehitpause = 1
;=======================================;

[State 1520, Fade]
type = changestate
trigger1 = movecontact ;destroyed state
value = 1511
ignorehitpause=1

[State 1520, End]
type = DestroySelf
trigger1 = pos x != [-200,200]

Spoiler: .cmd (click to see content)

Code:

;---------------------------------------------------------------------------
;Board Throw
[State -1, Board Throw]
type = ChangeState
value = 1500
triggerall = command = "Board Throwx" || command = "Board Throwy"
trigger1 = ctrl
trigger1 = !NumHelper(1510);this prevents you from throwing more than 1 while another is alive
trigger2 = Numhelper(1510)
trigger2 = helper(1510), StateNo = 1511
trigger2 = ctrl;trigger2s allow you to throw another while the 1st board is in it's hit state

All I need to do now is make the EX Projectile that hits multiple times and test it with the reflector. Then I'll be finished with this portion. @JMorphMan: Didn't you come up with a good way to have multi hitting projectiles get destroyed in the manner they should? The reflector may need to be adapted to that as well, not sure yet.

After that I only need to add charge coding, Juggle Points, and reversed command fix and I think he'll be ready for release!

DW

Re: Let's update Kung Fu Man

#167 February 24, 2017, 07:57:05 pm

@Vans: What about the sealing property done by Chizuru? Do you have a tutorial for that? Also, will it be implemented into this KFM update?

Project Thread/Request Thread/Dream Thread ~R.I.P Tamez

JustNoPoint

Re: Let's update Kung Fu Man

#168 February 24, 2017, 08:05:20 pm

He hasn't yet. What does it do? Is it something that's typically in fighters like projectile reflection?

Niitris

Re: Let's update Kung Fu Man

#169 February 24, 2017, 08:17:09 pm

Seals the usage of all special and super moves. Not quite as common, but at least it's not Nicotine's control reversal.

JustNoPoint

Re: Let's update Kung Fu Man

#170 February 24, 2017, 08:27:04 pm

Is this something we feel should be a standard? There are a lot of things that need standards to work. And the more we stuff into KFM the harder he will be to learn with.
@DW: @Niitris:

Last Edit: February 24, 2017, 11:01:55 pm by Just No Point

Hannah Montana

Re: Let's update Kung Fu Man

#171 February 24, 2017, 09:07:55 pm

The Best of Both Worlds
SuperStar

hello everybody.
i already released a 0101 DOS Kfm with new stuff.
This new one in project is welcome.

DW

Re: Let's update Kung Fu Man

#172 February 24, 2017, 11:25:36 pm

^And you posted that why...?

Just No Point said, February 24, 2017, 08:27:04 pm

Is this something we feel should be a standard? There are a lot of things that need standards to work. And the more we stuff into KFM the harder he will be to learn with.
@DW: @Niitris:

Should it be a standard? No, but I feel the same way about the reflection stuff.

As for it making KFM harder to learn from, I don't see it. There's more, yeah, but one will only take from him what they want. It just gives more options overall. Also, since you're doing a pretty good job of labeling everything, it shouldn't be difficult. One need only apply themselves.

EDIT:

Let me clarify. It being a standard, yes. As far as the var(s) used and everything, so everything matches up. It has to be that way if it's going to work. I didn't explain that well enough. I more so mean that it isn't something that HAS to be implemented, though, would be nice to include. So people who may want to implement it, have a primer in which to apply it from. The reflection and the sealing.

Project Thread/Request Thread/Dream Thread ~R.I.P Tamez

Last Edit: February 24, 2017, 11:33:11 pm by DW

Jmorphman

Re: Let's update Kung Fu Man

#173 February 25, 2017, 04:39:02 am

If you’re gonna reach for a star...
reach for the lowest one you can.

Just No Point said, February 24, 2017, 07:41:51 pm

All I need to do now is make the EX Projectile that hits multiple times and test it with the reflector. Then I'll be finished with this portion. @JMorphMan: Didn't you come up with a good way to have multi hitting projectiles get destroyed in the manner they should? The reflector may need to be adapted to that as well, not sure yet.

I recently updated Guile to fix his EX projectile (which hits twice), and it more or less behaves the way multi-hit special projectiles do in SFA and CvS (where they die immediately after colliding with another any other projectile, including single hit ones, even if they're supposed to hit multiple times). But I'm not sure if that behavior should be used for Kung Fu Man; perhaps a more simple projectile behavior would be best, like the one from SFIV (wherein a projectile has a certain number of hits, and when it's exhausted all of its possible hits, whether by hitting an opponent or colliding with a projectile or what have you, it dies).

The latter just seems more simple and intuitive, and it's also how multi-hit super projectiles work in SFA and CvS. there is a smallish issue, though).]And also there's a small issue that the former method has in MUGEN because MUGEN sucks.[/url]

GhostFox12

Re: Let's update Kung Fu Man

#174 February 25, 2017, 06:38:35 am

The fox who doesn't know where he's going.

I've created a "Burned" sprite for your Kung Fu Man:

Also, I realized that I never gave you the code for Dash Collision. The code was original made by Team Z2, I only edited a little to make it compatible with Kung Fu Man.

First put this in the AIR file:

Code:

; Dash Collision - HDBZ
[Begin Action 950]
950,0, 0,0, -1

; Grabbing when win
[Begin Action 951]
Clsn1: 1
  Clsn1[0] = 1, -86, 83, 0
800,0, 0,0, 1

;Dash Collision check
[Begin Action 128950]
-1,0, 0,0, -1

Then put this block of code in Statedef -2 (or Statedef 100 if you want):

Code:

;==| DASH COLLISION ACTIVATION |================================================
[State -2, Dash Coll]
type = Changestate
triggerall = enemy,stateno=100 || enemy,stateno=950
triggerall = p2bodydist X = [-30,30]
trigger1 = enemy,selfanimexist(128950)
value = 950
;===============================================================================

Finally, add Statedef 950, 951, and 952 anywhere in kfm.cns

Code:

;===========================================================================
; DASH COLLISION
;===========================================================================
[Statedef 950]
type = S
physics = N
movetype = A
anim = 950
ctrl = 0
velset = 0,0
sprpriority = 2


[State 800, ABORT]
type = Changestate
trigger1 = p2stateno != 950 && p2stateno != 951 && time >= 4 && time<50
value = 952 ;when it fails
ctrl = 1

[State 1000]
type = PosAdd
trigger1 = P2bodydist X < 10
X = -8
[State 1000]
type = PosAdd
trigger1 = P2bodydist X < 25
X = -5
[State 1000]
type = PosAdd
trigger1 = P2bodydist X < 35
X = -2
[State 1000]
type = PosAdd
trigger1 = P2bodydist X < 40
X = -1

[State 1000]
type = width
trigger1 = 1
edge = 50,40

[State 800, Grab SND]
type = PlaySnd
trigger1 = time=5
value = 0,3

[State 4500, 1];Scream
type = PlaySnd
trigger1 = time=5
value = 5,0
volume = 255

[State 1000, shake]
type = EnvShake
trigger1 = !(time%4)
time = 8
freq = 20
ampl = 1+0.1*time

[State 800, count]
type = VarSet
trigger1 = !time
var(30) = 0
[State 800, count]
type = VarAdd
trigger1 = command="x" || command="y" || command="z" || command="a" || command="b" || command="c" || command="start"
;trigger2 = command = "up" || command = "down" || command = "back" || command = "fwd"
var(30) = 1

[State 800, count]
type = Changestate
triggerall = time = 80
trigger1 = var(30) > enemy,var(30)
value = 951

[State 800, count]
type = Changestate
triggerall = time = 80
trigger1 = var(30) < enemy,var(30)
value = 0
ctrl = 0

[State 800, count]
type = Changestate
triggerall = time = 80
trigger1 = var(30) = enemy,var(30)
value = 105
ctrl = 0


;Grabbing
[Statedef 951]
type = S
movetype = A
physics = S
juggle = 15
velset = 0,0
ctrl = 0
anim = 951
sprpriority = 1
facep2 = 1
poweradd = 20

[State 800, Do_not Guard]
type = attackdist
trigger1 = 1
value = 0

[State 800, hit]
type = hitdef
trigger1 = animelem=1
attr = S,NT
hitflag = M- 
priority = 1,Miss 
sparkno = -1
p1facing = 1
p2facing = 1
p1stateno = 810
guard.dist = 0
fall = 1
fall.recover = 0

;Abort Dash Collision to avoid bugs
[Statedef 952]
type = S
physics = N
movetype = A
ctrl = 1
velset = 0,0
sprpriority = 2

[State 0, ChangeState]
type = ChangeState
trigger1 = 1
value = 0
ctrl = 1

There, you're done.

XGargoyle

Re: Let's update Kung Fu Man

#175 February 25, 2017, 09:15:25 am

Hedgehog Whisperer
Red Bull addict

GhostFox12 said, February 25, 2017, 06:38:35 am

Also, I realized that I never gave you the code for Dash Collision. The code was original made by Team Z2, I only edited a little to make it compatible with Kung Fu Man.

Bro, do you realize that JNP is a member of Team Z2??

Vans

Re: Let's update Kung Fu Man

#176 February 25, 2017, 09:26:37 am

Just No Point said, February 24, 2017, 08:27:04 pm

Is this something we feel should be a standard? There are a lot of things that need standards to work. And the more we stuff into KFM the harder he will be to learn with.
@DW: @Niitris:

I don't think it should be. I wrote a small tutorial in Chizuru on how to add the compatibility, maybe I should make a post in the forum?

Just No Point said, February 24, 2017, 07:41:51 pm

Anyway, I got it all finished and notated. I think it's pretty clear now. Feel free to add to it or make corrections.

It looks very good!

As for multi-hitting projectiles, I believe there shouldn't be too much of an issue with those. When one of those collide with a reflector, then they would automatically be sent to the reflected behavior. At this point, this state can specify if the projectile should lose "health", keep full life or do something else. I tested the reflector with projectiles such as Sakura's hadouken from Street Fighter Alpha 3 and a fully charged Kaiser Wave from Rugal.

One thing that does need to be done with a little more care is a reflector that stays alive for a fixed amount of time (like Aegis Reflector). However, the only issue in this case is that the reflected projectiles could theoretically cancel each other (think of the Aegis Reflector being bombarded with a bullet hell, some of those bullets will clash with themselves).

By the way, there's something very special I wanted to mention about State 1441.

If you look at the reflector, the logic of the states is as follows (if it comes in contact with a compatible projectile):

Reflector => Succesful reflection => Special reflection.

The "Special reflection" state is very important as it fixes a MUGEN bug:

In MUGEN it is impossible to block one of your own objects, even if it has the flag of affectteam = F.

What this state does is that it takes the (now dead) reflector object and it "sticks" to the reflected projectile. What this does is that it allows P2 to detect a "hostile" object and thus allowing them to block.

This state is very important.

Last Edit: February 25, 2017, 09:30:46 am by Vans

JustNoPoint

Re: Let's update Kung Fu Man

#177 February 25, 2017, 12:20:42 pm

Yeah I was kinda worried about multihitters. Wasn't sure if I needed to code how they act or what yet. Nice to know it'll all depend on how I coded the reflected one.

I'm waking up and getting ready for work so I'm going off memory but state 1441 uses the projectile that was made in the reflection to do this? That's pretty neat. Another thing I should teach that JMM agreed would be better is the explod method for destroyed fireballs. Basically I'd make an invisible explod get fired with the helper. When the helper leaves its attack state the explod plays it's getting destroyed anim. This would fix the issue where killing a helper with reversaldef doesn't create the destroyed anim of the fireball. Like the only good thing about using the projectile controllers for fireballs lol

For reflection you'd simply code the explod to go invisible again in the reflected state.

GhostFox12 said, February 25, 2017, 06:38:35 am

I've created a "Burned" sprite for your Kung Fu Man:

Awesome thank you! And yeah, if I thought it was needed I'd easily put the code for dash collision. I'm just putting in optional anims to represent them. I'm not adding code to activate them all

This does remind me that I need to share the updated dash collision code. There's a bug in the old code. Me and XG fixed it.

Vans

Re: Let's update Kung Fu Man

#178 February 25, 2017, 12:30:43 pm

Ah, I see.

You can also use a projectile controller to play animations if need be, I sometimes use those as glorified explods so I can have afterimage effects on them.