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

LM4 Suggestion: Swarm Mechanic #441

Open
UltimaOath opened this issue Jan 17, 2023 · 0 comments
Open

LM4 Suggestion: Swarm Mechanic #441

UltimaOath opened this issue Jan 17, 2023 · 0 comments
Labels
priority: low Low priority status: confirmed Confirmed by a maintainer status: unassigned target version Needs a future version assigned to it type: improvement Add or adjust a feature

Comments

@UltimaOath
Copy link
Collaborator

UltimaOath commented Jan 17, 2023

  - function: 'activate-swarm-low-chance'
    triggers: ['on-entity-damage']
    processes:
      - process: 'engage-swarm'
        if:
          - condition: 'entity-type'
            in-list: ['zombie']
          - condition: 'entity-owner'
            not-in-list: []
          - condition: 'chance'
            value: 0.05
        do:
          - action: 'activate-swarm'
            duration: 5s
          - action: 'exit-function'

Was imagining a mechanic where if the activate-swarm action occurs, all entities within X distance of a player who caused the triggered event will be set to a follow range of the X distance plus 1, and will have their primary targets set to that player if the entity is not already following another player. This is to last for the set duration:, at which time the follow distance for those entities are then reset to their original values pre-swarm-event. If the entities have moved close enough to their target to naturally 'swarm' the player, then that's for the player to handle, but ideally the distance would mean that not the entire swarm would make it to the player before the duration ends (unless intended like a nightly event lol). This would only apply to entities that presently exist and not future entities. Should a second swarm event occur, entities that are already/currently swarming are skipped for the new player.

@lokka30 lokka30 added type: improvement Add or adjust a feature priority: low Low priority status: unassigned target version Needs a future version assigned to it status: confirmed Confirmed by a maintainer labels Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low Low priority status: confirmed Confirmed by a maintainer status: unassigned target version Needs a future version assigned to it type: improvement Add or adjust a feature
Projects
None yet
Development

No branches or pull requests

2 participants