Skip to content

fix(castle-siege): don't punish kills between opposing siege sides - #1348

Merged
sven-n merged 2 commits into
MUnique:masterfrom
icheat2win:fix/castle-siege-pk-exemption
Oct 29, 2026
Merged

sven-n merged 2 commits into
MUnique:masterfrom
icheat2win:fix/castle-siege-pk-exemption

Conversation

@icheat2win

Copy link
Copy Markdown
Contributor

Part of the Castle Siege epic (#735).

Problem

During the battle, killing a player of another siege side made the killer an outlaw, unless both guilds happened to be declared rivals. Attacks also started the self-defense. Every siege fight between attackers and defenders was punished as a normal player kill.

Change

  • CastleSiegeContext.AreOnOpposingSides: two players are enemies when the siege is in Start, both are on the Castle Siege map with a side, and the sides differ. The attacking sides are enemies of each other as well.
  • CastleSiegePlugIn now also implements the existing IPlayerKillPenaltyExemptionPlugIn point (the same seam the Gens battle zone uses), so the exemption covers the kill penalty and the self-defense.
  • Documented on the Castle Siege page of the docs website.

Kills of the own side, and kills outside the battle, stay normal player kills.

Tests

New CastleSiegePlayerKillTests (5 tests): side combinations, outside the battle, player off the siege map, exemption through the plugin manager, and the kill penalty for opposing vs. same side.

Ran dotnet test tests/MUnique.OpenMU.Tests --no-build --filter FullyQualifiedName~CastleSiegePlayerKillTests (5 passed). Not verified with a game client.


Generated by Claude Code

icheat2win and others added 2 commits October 28, 2026 18:11
During the battle, the attacks and kills between players of different
Castle Siege sides are exempted from the player killer penalty and the
self-defense, unless their guilds were declared rivals.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011xNc764bgrPZRQYCRzPj1x
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-29T16:09:16.026574Z ef3a30e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 9 complexity · 4 duplication

Metric Results
Complexity 9
Duplication 4

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@sven-n
sven-n merged commit 2e2defa into MUnique:master Oct 29, 2026
2 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.

3 participants