Proportionate hitspark placement help

[Luigi-Master]

By the title, I mean the usage of a little code regarding the character's size and hitspark location.  From my own understanding, the code would be *const(size.xscale) for X values and *const(size.yscale) for Y values.  It works fine and all, but they all cause debug spam for whatever reason.  Is there an alternative to this, besides making the values constant irregardless of the character's size?

Speaking of which, you might be wondering why I want to use code for it instead of finding the exact location.  Well, let's just say I want it to be a feature to re-size the character to your liking, and the hitsparks and other things are of proportionate size and location.

Thanks in advance!

[Acey]

By the title, I mean the usage of a little code regarding the character's size and hitspark location.  From my own understanding, the code would be *const(size.xscale) for X values and *const(size.yscale) for Y values.  It works fine and all, but they all cause debug spam for whatever reason.  Is there an alternative to this, besides making the values constant irregardless of the character's size?

Speaking of which, you might be wondering why I want to use code for it instead of finding the exact location.  Well, let's just say I want it to be a feature to re-size the character to your liking, and the hitsparks and other things are of proportionate size and location.

Thanks in advance!

I completely understand why you might want to do something like this. If you put this code into a varset then it will chop off the decimals and then you should be able to use each of the the vars for the x and y position in the hitdefs.

Now I'm pretty sure that vars can be used as the sparkxy in the hitdef but if it doesn't work for some reason then you can just make the hitspark -1 (no hitspark) then use an explode sctrl with a "trigger = movehit" for the spark instead. I know explodes can use the vars as the position, but it should probably work for the sparkxy anyways.

[Luigi-Master]

Would you mind giving me an example?  Thanks!

[Acey]

in the hitdef it might look like this:
spritexy = var(1),var(2)

with an explod it might look something like this:
pos= var(1),var(2)

also make the varsets (in statedef -2 probably)
var(1) = (enemynear,const(size.ground.front)) * (enemynear,facing) * (-facing);x distance
var(2) = floor(pos y-enemynear,pos y);top of head

You could also add values to the vars is you need adjustments (e.g. -60 to var(2)), either in the varset or in the pos.

I havn't tested this particularly but this should give you a starting place.

[ClubSyN-X-TReME]

This might help.

http://clubsyn-x-treme.net/-X-Base/index.php?showtopic=38

[Alexziq]

People do this often in grabs where theres no actual hitdef, and a - add life is used for damage. I just added in the scale = 0,0 line of code to change the size

I just coded one last week. I can post an example later which might be a little easier. I m working now, and cant remember it off the top of the head.

[O Ilusionista]

I want it to be a feature to re-size the character to your liking, and the hitsparks and other things are of proportionate size and location.

There is a easy way to solve this case when you use projectiles, explods and helpers:

scale = 0.5*const(size.xscale),0.5*const(size.yscale)

The 0.5 is the value you want (on my case, I want it cutted by half). So, if you want the normal size, just use:

scale = 1*const(size.xscale),1*const(size.yscale)

Since you're multiplying, you don't need to add .0 (like 1.0). But if we would make a division, we should use 1.0.
Mugen has a known bug handling real numbers.

For the position, its the same logic, just need to round the number:

pos = ceil(-28*const(size.xscale)),ceil(-38*const(size.yscale))

-28 and -38 are the values I want when my scale is 1.0

On the Acey code, you need to use a triggerall = NumEmeny, or it will give debug flood in some cases.


Post Merge: May 03, 2011, 12:56:45 PMif you need it for a helper, the scale follow the same logic too:

[State 0, Helper]
type = Helper
trigger1 = !time
helpertype = normal ;player
name = "Fazedor de geladinho"
ID = 1005
stateno = 1005
pos = ceil(35*const(size.xscale)),0
postype = p1    ;p2,front,back,left,right
facing = 1
ownpal = 1
size.xscale = 1*const(size.xscale)
size.yscale = 1*const(size.yscale)

[Luigi-Master]

Ilusionista got the code right!  I knew I could count on him!  Thanks man!   

pos = ceil(-28*const(size.xscale)),ceil(-38*const(size.yscale))

Question, will this also work for velocities?  Since when a character changes his size, the moves might not work right due to the new size, especially launchers and the like.

[O Ilusionista]

you are welcome. Knownledge is made to share.

yes, it will work for velocities too, like:

type = VelSet
X = 4*const(size.xscale)

4 is the base velocity. If you make the char smaller, it will go slowly. If you make it bigger, it would go faster.

using this method you can change your scale freely. This is what I use at PDC.

[Luigi-Master]

I suppose it also works for hit velocities as well, right?  Thanks again!

[O Ilusionista]

probabily, but I never tested it.


Like I never tested if it works when the stage change your scale. As far as I know, it works, but I need to test.