Chat
Discord
12-17-2015, 07:33 PM
no shadow and no gravity
well pretty poor options. first there should be a tag called "shadow", so you can choose which shadow are you going to use or none. coz a big bug of lf2 is that knife have the same shadow with a big attack like fire explosion.
even thought there are y_acc and y_vel (if its not yet it must be), I think there should be values for gravity. well since there is an y_acc, we know that gravity is an acceleration. So in fact there is no need of such kind of tag. lets say we want to make 3 frames with gravity, so we just use the y_acc value. anyways maybe for higher acuity and easy-using putting making this tag more functional would be good.
Same applies for friction. As we know every object have it's own friction (lf2 object or bg area).
Now lets talk about priority. here you can think about parent-child object but I am first referring to global fields of the objects aka tags in bmp part (if there will be one
). So for high practically I suggest to put a priority level on tags such as gravity. So if I want to quick modify any object I can just put a gravity=0/no gravity with a high level and so the whole object become without gravity. or let's say in a system with 10 levels of priority 0 lowest, I can have frames with different gravity levels. say some frames with level 1 and some others with 4 and some other with 7. now if I want to quit grav in some frames (which I have consider that don't need that much gravity and have marked them low in priority) I just put gravity=0 with priority 6 on the top of the file and so only those frames with p7 will "survive" the change. Or maybe an advanced concept would be to write in which frames this priority tag will be applied. so lets give an example frames_where_apply= 10-12 14-20 220-500
how do u think?
well pretty poor options. first there should be a tag called "shadow", so you can choose which shadow are you going to use or none. coz a big bug of lf2 is that knife have the same shadow with a big attack like fire explosion.
even thought there are y_acc and y_vel (if its not yet it must be), I think there should be values for gravity. well since there is an y_acc, we know that gravity is an acceleration. So in fact there is no need of such kind of tag. lets say we want to make 3 frames with gravity, so we just use the y_acc value. anyways maybe for higher acuity and easy-using putting making this tag more functional would be good.
Same applies for friction. As we know every object have it's own friction (lf2 object or bg area).
Now lets talk about priority. here you can think about parent-child object but I am first referring to global fields of the objects aka tags in bmp part (if there will be one
). So for high practically I suggest to put a priority level on tags such as gravity. So if I want to quick modify any object I can just put a gravity=0/no gravity with a high level and so the whole object become without gravity. or let's say in a system with 10 levels of priority 0 lowest, I can have frames with different gravity levels. say some frames with level 1 and some others with 4 and some other with 7. now if I want to quit grav in some frames (which I have consider that don't need that much gravity and have marked them low in priority) I just put gravity=0 with priority 6 on the top of the file and so only those frames with p7 will "survive" the change. Or maybe an advanced concept would be to write in which frames this priority tag will be applied. so lets give an example frames_where_apply= 10-12 14-20 220-500how do u think?