06-03-2010, 09:54 PM
(06-03-2010, 09:38 PM)Blue Phoenix Wrote:
DC-Code:opoint: kind: 1 x: 40 y: 79 action: 0 dvx: 0 dvy: 0 oid: 5 facing: 20 opoint_end:
This is the opoint from rudolf's +man-sequence. The facing-value tells the app to create two objects with the id: 5 and let them face the same direction as your char (1 would turn the object around). So you will not need to change that part for having them all into the same direction.
However, what I'd do is the following: in one frame of your attacking sequence, you opoint out the 3 objects behind your characters. In the next frame, the two additional ones in front (or whereever you want to have them). Link these two frames together with a certain wait-value, let's say "1". The opointed objects will have to run through different frames, similar to this little illustration here:
This way, you can time your stuff, even when you create objects at different frames.
Now, since facing will let your objects move apart from each other, you might want to try adding a "dvz: 550" into your opointed object-frames. That should prevent them from moving along the z-axis.
Wow, that's a downright impressive illustration...
- Would it work with a wait value of 0? It is quite crucial to the sequence I'm using. Difference is, I'm not sure whether the opoint takes place immediately as you enter the frame.
- I shall test this dvz trick in a moment and see if it works.
Well, doing this in the opoint didn't work... shall I add the code and a screenshot?

Chat

![[Image: 95179121.jpg]](http://img571.imageshack.us/img571/8140/95179121.jpg)