Huh. HitsMOs = 0 doesn't have any negative ramifications? I guess I should try that out in the future.

Personally I feel it's proper respect to crush your teammate's face into the dirt if he insists on rolling out for you like a red carpet.

I'll keep mine on.

Oh, okay. I hadn't noticed, usually I only play with around three mods at once. But it still amazes me how the AI has such good control of the jetpacks. I once lost a skirmish with Crobos digging up through my base. Maybe I just fail as a gamer.



I don't think so, it really changes the difficulty of the AI (I love it now that I can play an AI defense skirmish (Crobos vs. Crobos) on "Death" mode and know that I'm guaranteed to die within 2 minutes). Capnbubs really changed the gameplay of CC without changing the game.



I can still do that too, though. For some reason, it seems like Crobos can only walk through other Crobos. I can still kamikaze a dummy or clone with a Crobo at high speeds.

Yeah, what exactly is the distinction between HitsMOs and GetsHitByMOs

HitsMOs: Can it 'hit' other MOs?
GetsHitByMOs: Can it get 'hi' by other MOs?

All i know is, they both have to be = 0 before 255 0 255 will = invisible.

What the ♥♥♥♥ is this, blatant lies?
HitsMOs makes a MO hit other MOs that have GetsHitByMOs on.
GetsHitByMOs makes a MO get hit by MOs that have HitsMOs on, but can't be activated on MOSPs or MOPixels.

Just confused me to no end.
However, i meant the colours 255 0 255 = that horrible sprite background magenta.
But they just appear as white till HitsMOs = 0 and GetsHitByMos = 0.

Or at least, thats what i am grasping.

no, 255,0,255 magenta/pink is the masking colour and is always invisible on any sprite, no matter its physical status.

I meant making MOPixels invisible for making Jetpacks.

QFT.
Yeah, is there a clear cut functional difference between the two?

Just being able to have two sides for the same function?

Yes.
GetsHitByMOs objects will get hit by ones that have HitsMOs = 1
HitsMOs objects will hit GetsHitByMOs objects.
examples:
Object1 : GetsHitByMOs = 1, HitsMOs = 0
Object2 : GetsHitByMOs = 0, HitsMOs = 1
Object3 : GetsHitByMOs = 1, HitsMOs = 1
Object4 : GetsHitByMOs = 0, HitsMOs = 0

Object1 gets hit by 2 and 3, and doesnt collide with 4
Object2 hits 1 and 3, and doesnt collide with 4
Object3 hits 1, and gets hit by 2, and doesnt collide with 4
Object4 doesnt hit or get hit by anything.

I don't see the purpose of having two though. Why not just have HitMOs?

Goddamn. So you can make stuff that doesnt get hit, or stuff that does that doesnt hit stuff. Like, say, these actors. Notice how they can walk through each other? Yeah. HitsMOs = 0, GetsHitByMOs = 1, so they still get hit by bullets but dont collide with each other.

You know, that's the most confusing thing I've ever read.