New Guide to itr: Kind: 8

[Marshall]

^Going through all the trouble just to see you post is totally worth it

hope you'll tell us your method too

[Sinow Rappy]

My method was really simple. Basically, I just created a ball and made it invisible, then had the ball opoint the dummy character. This works because when an object is invisible, all type: 0 objects that it creates are also invisible, as pretty much everyone finds out the first time they play as Rudolf.

Of course, the ball goes to frame 0 once it becomes invisible, but i've found that in general frame 0 is not a very important frame in type: 3 data and you can easily use other frames instead for the first flying frame.
Thus, this method does not require additional data files. If you also use some additional itr/kind: 8 in the type: 3 object's frame 0, you can have the object jump to different frames that will create different dummy frames, if you need to create various dummies for different moves or something.

I implemented this method when I was experimenting with input holding and charge up blasts. It worked for my purposes, although I got to a point I would've had to used additional type: 3 data files to hide all of the Coms, so ultimately this method that you've presented here seems like it is generally more elegant.

Marshall edited this post 07-06-2010 10:41 PM because:

i think your method sounds easier to understand though and it's still v elegant

[mfc]

I do never want to get warned by grave-digging on this but i have to tell the main flaw of this tut...
It is really good to get rid of com logos by being invisible like rudolf.
But as AI tries to attack visible chars; AI is afraid of invisible chars...
When you are invisible with rudolf; you can see that AI always try to stay away from your exact position...
So being invisible doesn't solve the AI problem.
Btw i must say i'm impressed when i learnt that we can control the t0 objects with wpoint tags... Thank you Marshall...

---

In this case, my opinion to get rid of com logos without bugs is this:
1) Create a ball with state 3000 which has a special body.
2) Let the ball opoint the "t0 frame you want which has a wait: 0 and next: 1000" in it's hit frames.
3)Give a "itr which can hit that ball" to your itrk8 related move...
-With this way; com logo will be shown for a very very short moment but it will do its job.
And you can't even see that com logo without debugging with F2 ...
Aaaand this is a solution for general static com problems but it can be implemented to different amazing dc thingies... It is what i did in my teleporter...

[Mesujin]

Ye, gravedigging, but i just want to make it better...

Actually didn't realize this kind of trick already invented '-'
But, the way to immediately using weaponact: that lead to the frame you're wanted it to go to was a bad idea bcs type:0 has a chance to be spawned late by 1tu when it being spawned from opoint:. Means sometimes, this trick won't work.

It should be looks like this. (the type:3's code)

DC-Code: <frame> 0 x pic: 99 state: 3005 wait: 0 next: 1 centerx: 0 centery: 0 <frame_end> <frame> 1 x pic: 99 state: 3005 wait: 0 next: 2 centerx: 0 centery: 0 opoint: kind: 2 action: 1299 oid: % opoint_end: #% was depends on which type: 0 that you are using. Also, remember it’s opoint: kind: 2 wpoint: kind: 1 x: 0 y: -1 weaponact: 1299 cover: 1 wpoint_end: <frame_end> <frame> 2 x pic: 99 state: 3005 wait: 0 next: 1000 centerx: 0 centery: 0 wpoint: kind: 1 x: 0 y: -1 weaponact: $ cover: 1 wpoint_end: #$ is the specific frame of type: 0 that you want it to go to <frame_end>

Well the way i provide from that Code are more to make an invisible type:0 at specific frame.. but yes it's also works to just make an invisible type:0 for ik8 purpose by changing the next:1000.

Tbh i forgot there's 3 pages in this Thread, and found out the way better to just make an invisible "Com"..
(https://lf-empire.de/forum/showthread.ph...0#pid95710)
But it's just a "Com" not an "invisible Com that may do type3's stuff"..

Important! Dispite the goodness of this trick, there's a big flaw that you'll need to care on..
When there's multiple type:0 that being Opoint-ed with kind:2 at EXACTLY same position, the Higher/Lower (i tho the higher) ObjNum will somehow magically get transferred/bugged to the lower ObjNum's wpoint (i guess) which causing that object to bugged on it's Frame 0 weirdly.

Well, the way to fix it are quite simple, just give the frame0 of type0 a next:1000...
Or, you can use st8xxx that transform into type:0 to fix the problem (i guess it'll works, yet tried by myself bcs it's way slower)

Tho actually this could be a way to make a multiple same obj at exactly same position to become one Obj instead of multiple Objs.