Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Turrets target energy pulses #41

Open
sfiera opened this issue Mar 13, 2015 · 2 comments
Open

Turrets target energy pulses #41

sfiera opened this issue Mar 13, 2015 · 2 comments
Labels
Classic Compatibility Complexity:High Priority:Low Type:Defect
Milestone
Later

Comments

@sfiera
Copy link
Member

sfiera commented Mar 13, 2015

Original issue 38 created by sfiera on 2010-09-20T11:50:20.000Z:

What steps will reproduce the problem?

  1. Destroy a ship, releasing its energy.
  2. Fire a turret when the energy pulse is closer than any enemy.

What is the expected output? What do you see instead?

The turret will fire at the energy pulse. The way that ships are programmed to pick up energy pulses is for the pulses to be marked "Hated" but to not be shootable. Ships will therefore attempt to ram them (using logic similar to missiles). However, they are also targeted by turrets; this ought to be fixed.
@sfiera sfiera self-assigned this Mar 13, 2015
@sfiera
Copy link
Member Author

sfiera commented Mar 13, 2015

Comment #7 originally posted by paul.supanich on 2012-12-10T04:12:19.000Z:

Would the fix for this also influence guided weapons and how they interact with energy pulses?

@sfiera
Copy link
Member Author

sfiera commented Mar 13, 2015

Comment #8 originally posted by sfiera on 2012-12-10T06:27:26.000Z:

Yes. The way that energy blobs are implemented now is basically that they have the "enemy" bit (kHated) set, but not the "shootable" bit (kCanBeEngaged). We get the existing behavior because AI ships try to fight the energy blobs but don't know how to other than to ram into them. For missiles, it arguably makes more sense, since ramming into enemies is their normal course of action. The turret situation is less so, because the blobs are marked as non-shootable. It's still a bug in either case, of course.

@sfiera sfiera modified the milestone: Later Mar 14, 2015
@sfiera sfiera removed their assignment Aug 31, 2016
@sfiera sfiera modified the milestone: Later Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Classic Compatibility Complexity:High Priority:Low Type:Defect
Projects
None yet
Milestone
Later
Development

No branches or pull requests
1 participant
@sfiera