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

Walshy/mc 1.21 bundles #4299

Open
wants to merge 11 commits into
base: experimental
Choose a base branch
from

Conversation

Intybyte
Copy link
Contributor

@Intybyte Intybyte commented Mar 9, 2025

Reopened version of #4278

Description

Bundles in 1.21.3+ will create some problems with backpacks that need to be addressed

Issues

  • Players can put bundles into backpack (Minor problem, maybe worth considering a config option for this)
  • Players can put backpacks into bundles (Major problem)

Proposed changes

  • Make a tag similar to shulker boxes in order to stop people from putting bundles inside backpacks
  • Block people from bundling up backpacks (Major problem)

Checklist

  • I have fully tested the proposed changes and promise that they will not break everything into chaos.
  • I have also tested the proposed changes in combination with various popular addons and can confirm my changes do not break them.
  • I have made sure that the proposed changes do not break compatibility across the supported Minecraft versions (1.16.* - 1.20.*).
  • I followed the existing code standards and didn't mess up the formatting.
  • I did my best to add documentation to any public classes or methods I added.
  • I have added Nonnull and Nullable annotations to my methods to indicate their behaviour for null values
  • I added sufficient Unit Tests to cover my code.

WalshyDev and others added 10 commits October 1, 2024 02:17
…istener to use the wrapper on Player#getOpenInventory
# Conflicts:
#	pom.xml
#	src/main/java/io/github/thebusybiscuit/slimefun4/api/gps/GPSNetwork.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/api/items/SlimefunItemStack.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/cargo/ReactorAccessPort.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/electric/machines/CarbonPress.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/electric/machines/ElectricPress.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/electric/machines/HeatedPressureChamber.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/electric/reactors/Reactor.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/magical/talismans/EnderTalisman.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/items/magical/talismans/Talisman.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/setup/DefaultItemGroups.java
#	src/main/java/io/github/thebusybiscuit/slimefun4/implementation/setup/SlimefunItemSetup.java
#	src/test/java/io/github/thebusybiscuit/slimefun4/implementation/items/TestSlimefunItem.java
Copy link
Contributor

github-actions bot commented Mar 9, 2025

Pro Tip!
You can help us label your Pull Requests by using the following branch naming convention next time you create a pull request. ❤️

Branch naming convention Label
feature/** 🎈 Feature
fix/** ✨ Fix
chore/** 🧹 Chores
api/** 🔧 API
performance/** 💡 Performance Optimization
compatibility/** 🤝 Compatibility

If your changes do not fall into any of these categories, don't worry. You can just ignore this message in that case! 👀

@Intybyte Intybyte force-pushed the walshy/mc-1.21-bundles branch from a178eee to 42655d1 Compare March 24, 2025 14:10
@Intybyte Intybyte marked this pull request as ready for review March 24, 2025 14:11
@Intybyte Intybyte requested a review from a team as a code owner March 24, 2025 14:11
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