ZDoom

Thank you

Tormentor667 wrote:In which way has it been implemented?

This way, I believe.

In which way has it been implemented? (or actually, how can this be applied to the WOlfenDoom grenades?)

Looks like this can be closed, now.

Is this hard to add, low prio or simply impossible? Some programmers' feedback would be appreciated

Exactly why I am looking forward to this as well:
http://forum.zdoom.org/viewtopic.php?f=3&t=48873

Sure. (You could also archive the OP in a spoiler and put the new concept above it.)

NeuralStunner wrote:Okay, yeah, I see that now. It's just that you weren't specific about "this" in the bump post.

Well, since I was indicating that I made the bump solely for the presence of the new flags parameter in A_CustomMissile, I figured it was implied that I wanted to take that route. And again, as you said before, it would be a more precise way to tell the engine what is desired; one of a number of reasons this is a more proper approach.

Though, come to think of it, I suppose it would be prudent of me to change the thread title to reflect the current desires?

Ed the Bat wrote:I'm pretty certain that the several posts preceding my latest bump are to that tune (read: I agree with you). I only proposed it as a flag the first time because I thought it would have a better chance of being done quicker. 19 months later, I wonder if I would've been right about that.

Okay, yeah, I see that now. It's just that you weren't specific about "this" in the bump post.

NeuralStunner wrote:Thinking about it, I'm unsure whether this would work... How would the firing functions "know" which firing function initiated the attack?

Personally I would vote for all generic attack functions getting a noautoaim flag in them.

I'm pretty certain that the several posts preceding my latest bump are to that tune (read: I agree with you). I only proposed it as a flag the first time because I thought it would have a better chance of being done quicker. 19 months later, I wonder if I would've been right about that.

Thinking about it, I'm unsure whether this would work... How would the firing functions "know" which firing function initiated the attack?

Personally I would vote for all generic attack functions getting a noautoaim flag in them.

Now that A_FireCustomMissile officially has a flags parameter, would it be possible to consider this again? For a long time now, I've had to hack up weapons where one method of fire needs to ignore autoaim and the other should not.

I've been mulling this idea over some more, recently. I wasn't sure how much work it would be, because I didn't really take account of how many different functions would need to be updated. But, I went through the list just now, and since I feel it would be acceptable to just add this to the customizable ones, and leave the more rigid ones (like A_FirePistol) alone, since those weren't meant to be customized anyway...

It looks likes it just boils down to A_FireBullets and A_FireCustomMissile, as things stand now. I'd also like it for A_RailAttack, but since rails don't even support autoaim of any kind right now, that would be contingent on a separate feature suggestion I made, and won't be affected unless that gets approved. So, knowing it would only really require two (or maybe three) functions to get updated, I feel a bit more confident about the validity of this suggestion, because I would very much like to see it implemented.

As all this is happening, it might also be the perfect opportunity to finally see about giving railguns the ability to honor/deny autoaiming.

Useammo would become a 'flags' field, that's correct. Aim already has more than two values, so it's not a boolean field. That one will stay as-is.