i just noticed that the first input is actually the frame itself - thats pretty damn neat
now how about adding centerx/y and other values d:
edit:
theres are one/two things i really really could use this for
wpoint(/cpoint) positioning and weaponact(/action)
because for itrs/bdys i usually create/select the areas as i draw/render the spritesheet and thus its usually right in first place (unless its a really complicated combo/juggling(-possibility) move thing) and hence i would only use this to quickly check whether its all lookin good
with wpoints(/cpoints) you cant really do that - you may get the general area where it needs to go - and the angle(/frame) that might fit - but then you really need to test it in action, with several items(/characters) - doing it manually would take even more effort and time
now how about adding centerx/y and other values d:
edit:
theres are one/two things i really really could use this for
wpoint(/cpoint) positioning and weaponact(/action)
because for itrs/bdys i usually create/select the areas as i draw/render the spritesheet and thus its usually right in first place (unless its a really complicated combo/juggling(-possibility) move thing) and hence i would only use this to quickly check whether its all lookin good
with wpoints(/cpoints) you cant really do that - you may get the general area where it needs to go - and the angle(/frame) that might fit - but then you really need to test it in action, with several items(/characters) - doing it manually would take even more effort and time
favorite dcing techniques: wpoint | double key inputs | holding back | alternate basic moves