PaperMC / PaperMC/Paper

Stacking Raid farms aren't working

Open
#7,281 20 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs testing type: bug
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

Raids should be obtained every swing, but bad omen isn't acquired in every swing (of your sword)

Observed/Actual behavior

Bad Omen is only obtained once per Raid when it should be obtained every swing

Steps/models to reproduce

Download this world, and use the stacking raid farm.

Give yourself bad omen, and put yourself in survival mode, go and hit the minecart

Youtube video if your confused on how to use it: https://youtu.be/KjH2NA1eqIc?t=1707
World: https://www.mediafire.com/file/adhk7m1742ecksc/New_World.zip/file

Plugin and Datapack List

We have zero plugins and zero datapacks

Paper version

Latest Version

Other

Here is our stacking raid farm design.
https://www.youtube.com/watch?v=d4z7YzgIIB0

Here is our timings so you can see our config
https://timings.aikar.co/?id=3ab90888013d4a7a880db12a0c84d624

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the reproduction steps and linked world to reproduce the stacking raid farm behavior in survival mode. Compare whether Bad Omen is acquired on every sword swing or only once per raid; done means the observed behavior matches the expected behavior without plugins or datapacks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.