Skip to content

[lua] Various battlefield superlinking setup#10028

Merged
Xaver-DaRed merged 1 commit into
LandSandBoat:basefrom
Skold177:Superlink-Fix
May 14, 2026
Merged

[lua] Various battlefield superlinking setup#10028
Xaver-DaRed merged 1 commit into
LandSandBoat:basefrom
Skold177:Superlink-Fix

Conversation

@Skold177
Copy link
Copy Markdown
Contributor

I affirm:

  • I understand that if I do not agree to the following points by completing the checkboxes my PR will be ignored.
  • I understand I should leave resolving conversations to the LandSandBoat team so that reviewers won't miss what was said.
  • I have read and understood the Contributing Guide and the Code of Conduct.
  • I have tested my code and the things my code has changed since the last commit in the PR and will test after any later commits.

What does this pull request do?

Fixes superlinking in several battlefields by letting it be handled by the battlefield framework. A follow up to Franks PR.

  • Battlefields where the monsters are grouped in a single bracket (all spawned at once) are now defined with superlink = true

  • Battlefields where the monsters are in different brackets due to being spawned at different points during the fight are now linked with superlinkGroup = 1,

  • Battlefields setup with content:addEssentialMobs already have superlink applied automatically.

  • Removes superlink mobmod from several enemies, as it is no longer needed.

Steps to test these changes

Run Automaton Assault, Wyrmking Descends, When Hell Freezes Over, Steamed Spouts or any of the other changed BCNMs, see superlink now works.

@Skold177 Skold177 changed the title [lua] Superlinking [lua] Various battlefield superlinking setup May 13, 2026
Fixes super linking in multiple battlefields
@Xaver-DaRed Xaver-DaRed merged commit 46d9dfb into LandSandBoat:base May 14, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants