Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

GapCells=integer warhead #3

Closed
Musketmarine opened this issue Nov 10, 2020 · 2 comments
Closed

GapCells=integer warhead #3

Musketmarine opened this issue Nov 10, 2020 · 2 comments
Labels
Feature / Enhancement Anything new not present in vanilla/Ares Reused / Expanded Logic Logic that is repurposed for other needs or extended to cover more cases

Comments

@Musketmarine
Copy link

Musketmarine commented Nov 10, 2020

GapCells when set to an integer above 0 will allow a warhead to inflict gap generator logic in the cells the warhead is detonated in. Uses Big Gap targeting flags. Defaults to 0 for all warheads.

Practical use would be a Gap Generator smokescreen or superweapon that shrouds an area.

[GapWH]
CellSpread=3
GapCells=3
BigGap.Affects=Enemy

Maybe GapCells could be a child of BigGap logic, so syntax would become BigGap.GapCells=integer.

@Metadorius Metadorius changed the title GapCells=integer GapCells=integer warhead Nov 10, 2020
@Metadorius Metadorius added Feature / Enhancement Anything new not present in vanilla/Ares Reused / Expanded Logic Logic that is repurposed for other needs or extended to cover more cases labels Nov 10, 2020
@GraionDilach
Copy link

syntax would become BigGap.GapCells=integer.

Sounds redundant to me. BigGap.Cells perhaps moreso.

@RexDraco
Copy link

For the sake of versatility, I suggest differentiating between global and weapon targeting, preferably in a way we can have both on the same weapon:

BigGap.AffectsImpact= (enemy, friend, ally, self) ; impact as in warhead. If you hit an enemy with this weapon and it is vulnerable, this happens. percentage influences BigGap.ImpactDuration
BigGap.AffectsGlobal= (enemy, friend, ally, self) ; impact as in global, like Phobos currently operates. This will be handy for smoke screens, but otherwise is like above which is handy for hacking. It is possible to have both, punishing the player it hits.

BigGap.ImpactDuration= (int) ; how long the impact variant will last, versus is taken into account
BigGap.GlobalDuration= (int) ; how long the global variant will last, versus does nothing

BigGap.ImpactLocation= (center, target) ; does it spawn the GapCells only at the center of the warhead or does it spawn multiple circles of gaps on every enemy the WH connects to? Meaning the bigger group of enemies, the more shroud created.

Metadorius added a commit that referenced this issue Dec 19, 2020
@Phobos-developers Phobos-developers locked and limited conversation to collaborators May 10, 2023
@Metadorius Metadorius converted this issue into discussion #870 May 10, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Feature / Enhancement Anything new not present in vanilla/Ares Reused / Expanded Logic Logic that is repurposed for other needs or extended to cover more cases
Projects
None yet
Development

No branches or pull requests

4 participants