Team-EnderIO/EnderIO
1
0
Fork 0
Code Issues 114 Pull requests 13 Projects Releases 79 Packages Wiki Activity Actions

REplace EIOChestLootEvent with loot modifiers #1154

New issue
Open
opened 2025-10-04 14:55:16 +00:00 by Rover656 · 1 comment
Rover656 commented 2025-10-04 14:55:16 +00:00 (Migrated from github.com)
Copy link

Now that we're flattening things down and making sure that the "internal addons" can stand on their own, we should ditch this event and use loot table modifiers instead for adding armory loot to the Ender IO tables.

Now that we're flattening things down and making sure that the "internal addons" can stand on their own, we should ditch this event and use loot table modifiers instead for adding armory loot to the Ender IO tables.
Rover656 commented 2025-10-04 17:10:26 +00:00 (Migrated from github.com)
Copy link

Armory loot is temporarily disabled in dev/1.21.1 until I action this :)

Armory loot is temporarily disabled in dev/1.21.1 until I action this :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
dev/1.21.1
feat/more-balancing-changes
chore/clean-buildscript
feat/farming-station
dev/1.20.1
feat/mod-id-filter
feature/soul_pot
feat/conduit-redstone-insert-control
feature/sculk
l10n_dev/1.21.1
l10n_dev/1.20.1
feat/alloy-revert
chore/editorconfig-update
chore/graph-fixes
archive/1.21
archive/1.20.6
archive/1.20.4
archive/1.20.2
meta/security-policy
archive/1.19.4
archive/1.19.x
feature/modern-resources
feature/io-config-renderer
archive/1.18.x
archive/1.17.x
v8.0.4-alpha
v8.0.3-alpha
v8.0.2-alpha
v8.0.1-alpha
v8.0.0-alpha
v6.2.15-beta
v6.2.14-beta
v6.2.13-beta
v6.2.12-beta
v7.1.8-alpha
v7.1.7-alpha
v6.2.11-beta
v6.2.10-beta
v6.2.9-beta
v6.2.8-beta
v7.1.6-alpha
v7.1.5-alpha
v7.1.4-alpha
v7.1.3-alpha
v7.1.2-alpha
v7.1.1-alpha
v7.1.0-alpha
v6.2.7-beta
v6.2.6-beta
v7.0.11-alpha
v6.2.5-beta
v6.2.4-beta
v7.0.10-alpha
v6.2.3-beta
v7.0.9-alpha
v6.2.2-beta
v7.0.8-alpha
v6.2.1-beta
v7.0.7-alpha
v6.2.0-beta
v7.0.6-alpha
v6.1.11-beta
v7.0.5-alpha
v7.0.4-alpha
v7.0.3-alpha
v6.1.10-beta
v7.0.2-alpha
v6.1.9-beta
v7.0.1-alpha
v7.0.0-alpha
v6.1.8-beta
v6.1.7-beta
v6.1.6-beta
v6.1.5-beta
v6.1.4-beta
v6.1.3-beta
v6.1.2-beta
v6.1.1-beta
v6.1.0-beta
v6.0.25-alpha
v6.0.24-alpha
v6.0.23-alpha
v6.0.22-alpha
v6.0.21-alpha
v6.0.20-alpha
v6.0.19-alpha
v6.0.18-alpha
v6.0.17-alpha
v6.0.16-alpha
v6.0.15-alpha
v6.0.14-alpha
v6.0.13-alpha
v6.0.12-alpha
v6.0.11-alpha
v6.0.10-alpha
v6.0.9-alpha
v6.0.8-alpha
v6.0.7-alpha
v6.0.6-alpha
v6.0.5-alpha
v6.0.4-alpha
v6.0.3-alpha
v6.0.2-alpha
v6.0.1-alpha
Labels
Clear labels   
Area-Assets

   
Area-Backend

Backend work not usually visible to players.

  
Area-Conduits

Everything involving conduits

  
Area-Datapacks

   
Area-Lang

   
Area-Mod Compat

   
Area-Parity

1.12.2 missing features

  
Area-Rendering

Rendering code, might be shaders specific or general.

  
Good first issue

   
MC-1.19.2

   
MC-1.20.1

   
MC-1.20.4

   
MC-1.20.6

   
MC-1.21

   
MC-1.21.1

   
Modtoberfest

   
P-0-High

High priority, crash/breaking.

  
P-1-Medium

Medium priority. Potentially deleting items or breaking functionality.

  
P-2-Low

Low priority. Not hurting anyone, just annoying.

  
Status-Awaiting Response

Waiting for OP to respond

  
Status-Behind-Flag

This change is available but is placed behind a feature flag.

  
Status-Blocked

Blocked by a specific issue or protocol.

  
Status-Cannot Reproduce

   
Status-Duplicate

This issue or pull request already exists

  
Status-Help Wanted

We need some help to try and track this thing down..

  
Status-Incomplete Report

   
Status-Invalid

This doesn't seem right

  
Status-Needs LTS Backport

Fixed in latest but requires LTS backport.

  
Status-Needs Updating

Needs updating to a newer Minecraft version.

  
Status-Stale

This may not be updated by the OP any further.

  
Status-To Implement

   
Status-Triage

A Triage Member should take a look at this

  
Status-Wontfix

This will not be worked on

  
Status-Wontmerge

This PR won't be merged, but is left now for reference of ongoing or future works.

  
Type-Backport

   
Type-Bug

There is a problem.

  
Type-Documentation

Improvements or additions to documentation

  
Type-Enhancement

New feature or enhancement to existing feature.

  
Type-Question

Further information is requested

  
Type-RFC

Request for comments.

  
Type-Suggestion
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Team-EnderIO/EnderIO#1154
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?