Skip to content

Adding "wind-charge" flag (1.21.1+)#4520

Open
RedstoneFuture wants to merge 12 commits intoIntellectualSites:mainfrom
RedstoneFuture:feature/windcharge-flag
Open

Adding "wind-charge" flag (1.21.1+)#4520
RedstoneFuture wants to merge 12 commits intoIntellectualSites:mainfrom
RedstoneFuture:feature/windcharge-flag

Conversation

@RedstoneFuture
Copy link
Member

@RedstoneFuture RedstoneFuture commented Oct 12, 2024

Overview

This PR adds the "wind-charge" flag to prevent the block-update of minecraft:wind_charge and minecraft:breeze_wind_charge.

Description

  • updating serversoftware dependency from 1.20.4 to 1.21
  • adding new flag "wind-charge" to allow or block the block-trigger behavior (default false)
    • I check for build permission (added, trusted, owner) so that the permissions are similar to projectiles flag and users don't have to turn on the flag for everyone just because they want to work with it.
    • The projectiles flag must also be activated so that other players can use the wind-charges. I think it makes sense because the projectiles flag still seems to be ordered higher. -> wind-charge is more critical, so it has its own additional flag.
    • explosion flag still manage the explosion behavior (explosion clouds), but this is not necessary for the wind-charge effect.
  • adding checks in the ProjectileEventListener1211
### Submitter Checklist
- [X] Make sure you are opening from a topic branch (**/feature/fix/docs/ branch** (right side)) and not your main branch.
- [X] Ensure that the pull request title represents the desired changelog entry.
- [X] New public fields and methods are annotated with `@since TODO`.
- [X] I read and followed the [contribution guidelines](https://github.com/IntellectualSites/.github/blob/main/CONTRIBUTING.md).

@github-actions github-actions bot added the Feature This PR proposes a new feature label Oct 12, 2024
@RedstoneFuture RedstoneFuture changed the title Adding "windcharge" flag (1.21.1+) Adding "wind-charge" flag (1.21.1+) Oct 12, 2024
@github-actions
Copy link

github-actions bot commented Nov 1, 2024

Please take a moment and address the merge conflicts of your pull request. Thanks!

@github-actions
Copy link

Please take a moment and address the merge conflicts of your pull request. Thanks!

@RedstoneFuture RedstoneFuture marked this pull request as ready for review February 23, 2025 23:20
@RedstoneFuture RedstoneFuture requested a review from a team as a code owner February 23, 2025 23:20
@RedstoneFuture RedstoneFuture marked this pull request as draft February 23, 2025 23:20
@RedstoneFuture RedstoneFuture requested review from a team and removed request for a team February 23, 2025 23:21
@RedstoneFuture RedstoneFuture marked this pull request as ready for review June 15, 2025 11:02
@RedstoneFuture RedstoneFuture marked this pull request as draft June 15, 2025 11:03
@RedstoneFuture RedstoneFuture marked this pull request as ready for review June 15, 2025 11:44
@dordsor21
Copy link
Member

I think this is the same as the Java 21 PR where we would be required to drop <1.21 support due to binary incompatibilities somewhere with 1.21+ paper API

@TruaYT
Copy link

TruaYT commented Nov 15, 2025

Please adding ;)

@github-actions
Copy link

Please take a moment and address the merge conflicts of your pull request. Thanks!

@RedstoneFuture RedstoneFuture marked this pull request as draft January 24, 2026 14:20
@RedstoneFuture RedstoneFuture marked this pull request as ready for review January 24, 2026 14:31
@dordsor21 dordsor21 requested a review from a team February 7, 2026 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature This PR proposes a new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments