This flag would be used with actors that are intent upon weaving, yet have no collision checks such as if it was a +NOINTERACTION object. In fact, I would think it's safe to say that only if NOINTERACTION was specified, then this flag would be taken into account as well.
Currently, things with A_Weave and +NOINTERACTION will ultimately still "hit" the ceilings/floors/walls on it's Y and Z axis (side/top/bottom respectively) and it would indirectly continue hitting them as well. This is most noticeable on actors which call A_Weave in a consistent manner.
I'd also consider this a "limited use" flag as it would only be for A_Weave to check.
+NOWEAVECOLLIDE
Moderator: Developers
5 posts
• Page 1 of 1
+NOWEAVECOLLIDE
by Major Cooke » Sat Jul 30, 2011 11:55 am
-
Major Cooke - That's how my uncle stole christmas three times in a row in a single year. -DBT
- Joined: 28 Jan 2007
Re: +NOWEAVECOLLIDE
by NeuralStunner » Sat Jul 30, 2011 12:01 pm
Sounds more like a broken feature than a need for another. IMO, +NOINTERACTION should do as it is stated to for all collision.
-
NeuralStunner - O'Neill with it.
- Joined: 21 Jul 2009
- Location: The Colonies
-
Major Cooke - That's how my uncle stole christmas three times in a row in a single year. -DBT
- Joined: 28 Jan 2007
Re: +NOWEAVECOLLIDE
by Xaser » Sun Jul 31, 2011 10:47 pm
Sounds like a bug to me. +NOINTERACTION is not doing what it should be, in that example.
-
Xaser - secretly a supercomputer being a government
- Joined: 20 Jul 2003
- Location: .plɹoʍɹǝʌǝu.
Re: +NOWEAVECOLLIDE
by Major Cooke » Mon Aug 01, 2011 9:24 am
Well, just in case if it was intended, I couldn't help but attempt to cover the loopholes. Simply just making sure never hurts. 
-
Major Cooke - That's how my uncle stole christmas three times in a row in a single year. -DBT
- Joined: 28 Jan 2007
5 posts
• Page 1 of 1
Who is online
Users browsing this forum: albiongeck and 0 guests