Assign Held Physcannon Entity to Pass into Commander Goal Trace

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.

[AgentAgrimar]

Within code that passes the held physcannon entity in to ignore when performing a commander goal trace, there is a mapbase-specific addition that checks if the player has a held entity first, but otherwise forgets to assign the held physcannon entity to the local variable, this pull request corrects that.

---

Does this PR close any issues?

N/A

PR Checklist

• My PR follows all guidelines in the CONTRIBUTING.md file
• My PR targets a develop branch OR targets another branch with a specific goal in mind

[Blixibon]

Thank you for catching this. This code was originally created to make it easier to carry a certain physics object through different parts of Entropy : Zero 2, and I brought it to Mapbase later as a general quality-of-life change. Players would normally carry said phsics object with +USE, so I must not have tested it with the gravity gun at the time.