RedWire's Plugin

Supported MCreator versions
2022.3
2023.1
2023.2
2023.3
2023.4
2024.1
2024.2
2024.3
2024.4
2025.1
2025.2
2025.3
Tags / plugin type
Global triggers
Procedures
Pixel art of a blocky head winking wearing a rainbow beanie
Downloads:
8053
Upvotes: 64
About the plugin

RedWire's Plugin is a thing that I've been using mostly to help with my own mod-making experience. Hopefully, some of the additions from this plugin will be useful to other people :)

Supported plugin versions: 

Forge 1.19.2, Forge 1.19.4, Forge 1.20.1, NeoForge 1.20.4, NeoForge 1.20.6, NeoForge 1.21.1, NeoForge 1.21.4, NeoForge 1.21.8

A screenshot containing a compilation of procedures that RedWires Plugin offers

For info on most procedures and other stuff, check this file

Changelog

for the full list of changes, check this file

v6.3.7

  • Improved all global trigger procedures to include a warning line at the bottom of the procedure UI (so I'm not limited to the procedure blocks UI size)
  • Try-only, try-and-catch, and directly set itemstack variable procedures have some unique warnings of their own

v6.3.6

  • Slightly improved several procedures with the main goal being reducing generated line output + adding customBlockIndex to more procedures (likely more than I should have, but eh)
  • Improved "Get object from registry" procedure to only require a registry field. forgeregs.yaml is now basically reverted to how it was before I merged regclasses.yaml into it
  • "Set sound event" procedure now uses a safer holder wrapper: "BuiltInRegistries.SOUND_EVENT.wrapAsHolder" instead of "Holder.direct" to prevent any crashes
  • The "set damage to [x]" procedure for global damage triggers now better separates what event should be picked based on Forge/NeoForge (mind the gap inbetween NeoForge and the event name, I intentionally added a miniscule server-side icon just to "bypass" the 3-dot text cutoff)

v6.3.5

  • Yknow what? Screw version constraint syntax. Procedures limited by versions will instead read (min x.xx.x) or (max x.xx.x)

Plugin downloads
v6.3.7 - redwires_plugin_0.zip Uploaded on: 01/09/2026 - 00:21   File size: 326.24 KB

Comments

sorry but does the set dmg to 1 (NF:entity is attacked) work? because i thought it turned upcoming damaged into the inserted number, does the block work on its own or do i have to add anything else?, outside of the global trigger ofc

Uhh ur using the correct version, unless ur workspace is actually using Forge 1.20.1. Dunno why its ignoring the damage input cause it does what its intended to do.
Unless you have any other procedures that modify damage that might be overwriting yours, I dunno what I can do

Moved the display images for my plugins to my github page. You're welcome, anyone that lives in the UK

Is it possible to make it so that timed loops also support decimal values and not just integers?

NOTE (added to the plugin procedure info link): Canceling the "Item crafted from anvil (1.21.8<)" will cancel anvil damage, BUT will prevent charging the player XP and removing the input items. Handle accordingly.

The "set (entity) target to nothing" block doesn't seem to work for me, basically I am trying to do an item that make a certain entity "passive" when the player has it in his inventory/equipped

Dunno, works for me fine no problem. If you wanna attempt to keep entities from targeting you, you can set a "Entity sets its attack target" global trigger, use the "Set new target of source entity to [entity]" under the event procedures tab, and use the "No entity" block

How exactly does "Get X/Y/Z position of block inbetween Entity1 and Entity2" works? I'm trying to use it to check if there's a solid block between the player and my entity, but I'm not sure if I'm doing it right

I believe it checks for the first block that is closest to Entity1 thats in the way of it and Entity2, considering the raycasting starts from that.

Also, make sure you're using the "Can Entity1 find Entity2" check from my plugin aswell, as it'll just return 0,0,0 if there is no block in the way