Persistent and virulent bug

[chinkeeyong]

Straight to the point: If you check a projectile to be persistent and virulent, and kill a monster close up with it, the engine will act as if you were hit by your own projectile. This is, of course, completely impossible.

It seems to happen mainly with invisible projectiles, but I don't know for sure because I've only tested it with bullets.

Demonstration physics: [attachment=1839:Effect_D...stration.zip]

[treellama]

Persistent and virulent is broken in many ways. Don't use it.

[chinkeeyong]

Persistent and virulent is broken in many ways. Don't use it.

But when it works, it works AWESOME.

So, since you're the guy working with the code, how exactly is it broken?

[treellama]

So, since you're the guy working with the code, how exactly is it broken?

If you check a projectile to be persistent and virulent, and kill a monster close up with it, the engine will act as if you were hit by your own projectile.

Why do you keep posting

[chinkeeyong]

Why do you keep posting

You said "in many ways". I take that to be just one way.

[assassingao]

God, the bug's been there for ages. It used to cause A1 to give out error and quits itself.

Treellama fixed it so it won't force A1 to quit, not for people to abuse it and make a kewl railgun to pwn aliens with.

It seems to happen mainly with invisible projectiles, but I don't know for sure because I've only tested it with bullets.

As far as I know, appearance doesn't have anything to do with this bug.

[irons]

God, the bug's been there for ages. It used to cause A1 to give out error and quits itself.

Treellama fixed it so it won't force A1 to quit, not for people to abuse it and make a kewl railgun to pwn aliens with.

There's some of that G.A.O. prose we've been waiting for.

[treellama]

Treellama fixed it so it won't force A1 to quit

No, it still causes the engine to crash. The only fix is not to use it. Like I already said.

[chinkeeyong]

No, it still causes the engine to crash. The only fix is not to use it. Like I already said.

Uh, it doesn't crash? I said it just hurts you as well if you kill an enemy at a range of something like less than 1024 units.

[RyokoTK]

I think you might be barking up the wrong tree when you tell the game's only active developer that he's wrong about facets of his program.

[Winter_Wolf]

I find this all very strange, because I've been using "persistent and virulent" for a weapon for several months now and I've never had a problem. I even decided to check that it was tagged before I posted. A1 has never crashed, for me at least, using this tag.

With regards to the bug, well, that's there to stay chinkeeyong. Although, for the purpose I use it for, it makes sense that the player is going to be injured if he fires a frag grenade into monster at point blank range. The only reason I'm using it is to recreate an effect from PiD.

If "persistent and virulent" does actually cause problems in A1 on other computers I'd like to know so that I can disable it.

[treellama]

It can cause the engine to crash, depends on number of monsters and timing. If you can get the effect some other way (Lua would probably work pretty well) I'd advise doing that.

There's a "fix" here http://sourceforge.net/tracker/index.php?f...amp;atid=301997 that could stop the crashing, but it would break films and introduce other undesirable behavior.

[chinkeeyong]

I think you might be barking up the wrong tree when you tell the game's only active developer that he's wrong about facets of his program.

Good point.

It can cause the engine to crash, depends on number of monsters and timing. If you can get the effect some other way (Lua would probably work pretty well) I'd advise doing that.

OK, I get it now.