Add SlimeTech compatibility

[PhoenixCodingStuff]

Short Description

Add SlimeTech compatibility Change register logic

Additions/Changes/Removals

Added SlimeTech rubber item Changed register logic

Related Issues

N/A

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 base Slimefun and made sure nothing breaks/unexpected happens.
• [ ] 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 which may not be obvious to maintainers.
• [ ] I have added Nonnull and Nullable annotations to my methods to indicate their behaviour for null values

[J3fftw1]

Have you tested this? im 99% sure this will break recipes in litexpansions that require item id rubber.

[PhoenixCodingStuff]

I'll make the necessary code changes in sometime and test it. Also just a clarification does prioritising meaning putting SlimeTech first in the if statement? If yes then I'll switch it to SlimyTreeTaps first.

[J3fftw1]

I'll make the necessary code changes in sometime and test it. Also just a clarification does prioritising meaning putting SlimeTech first in the if statement? If yes then I'll switch it to SlimyTreeTaps first.

yes :d

[PhoenixCodingStuff]

[PhoenixCodingStuff]

dun

[PhoenixCodingStuff]

Done, I thought if you do something more than once (this.rubberItem) it would be better to create a local variable instead. I fixed it.

[PhoenixCodingStuff]

Walshy just told me to rename to rubber

[J3fftw1]

ugh @WalshyDev we have conflicting reviews there is no need to make the diff bigger then it is

[PhoenixCodingStuff]

Am I supposed to create local variables or nah? Also rubber or rubberItem

[WalshyDev]

The diff literally cannot get smaller..

[WalshyDev]

Changing to rubber would be MORE not less.