Entity Texture Features [ETF] "illegalPathSupportMode : All" breaks apotheosis (gems) in multiple ways
Closed this issue ยท 5 comments
Oof, okay... so.
With just neoforge .139 and 1.21.1 and apotheosis+depts and ETF, if you set ETF-misc-"Allow broken texture paths" to everything (All), and then close minecraft and reopen it.... you can't even launch the thing it just crashes during load (at least for me).
If for some reason it's possible to load past this, in my case adding an unholy combination of iris and sodium somehow fixes it, then the game is perfectly playable.
Except gems are then broken in two new magical ways.
- They won't drop from mobs. In singleplayer. Obviously, servers don't use sodium or iris or ETF, so there they drop fine. But are still bugged as per the next issue:
- If you somehow obtain them anyway (MP; or SP before turning on ETF-ABTP to ALL) they are orange stereotypical real diamond shapes with the name item.apotheosis.gem and say "Errored gem with no bonus!".
If you then turn back off ETF they are their appropriate gems with bonuses as per usual.
I assume overall (SP or MP) this is just a visual bug.
Separately, this issue seems to screw up random gear bonuses displaying, and bosses spawning. I can confirm it breaks boss spawning in SP (including /apoth spawn_boss @p), i'm not sure about MP; but I'm aware you can get random gear in MP (chest loot ?) and it should be a visual issue there (some boots changed my FOV implying speed works even though I can't see it on tooltip).
This is probably an ETF issue running headfirst into some way apotheosis is doing something. Whether it merits any actual changes??... probably not. Can just turn broken paths off. This is mostly posted for posterity and search results.
I have no idea what they're doing to trigger this. I suspect it's an ETF issue.
However, apoth does not rely on any broken paths for anything. So I don't know what ETF is on about.
Yes, this can be closed safely, I don't think it's worth investigating further. I wasn't finding any search results for this issue so it's mostly for google.
Anyone else coming across this, turn ETF "allow broken paths" to OFF
It could be this? Maybe?
Invalidating the contract of RL seems like a bad idea anyway