Circular dependencies because of skinsdb and bakedclay/nether about 3d_armor HOT 8 CLOSED

IMO the bug here is that i3 shouldn't depend on 3d_armor nor on skinsdb.

additionally, 3d_armor shouldn't depend on bakedclay (it doesn't even seem to use it? that's an easy fix)

from 3d_armor.

...its an autoclosed

i assumed so, but this autoclose is a natural language processing failure. a partial fix shouldn't have closed this. probably i could have phrased that differently? does github have a guide to how to not accidentally trigger the autoclose?

from 3d_armor.

If you are using the ethereal mod, could this be the root cause: mt-mods/moretrees#22 ?

from 3d_armor.

IMO the bug here is that i3 shouldn't depend on 3d_armor nor on skinsdb.
-snip-

i mean, it could not and use a register on mods loaded to handle that part, but at its core, it does provide features in itself that use apis/functionality from those mods, it should (optionally) depend on them

from 3d_armor.

should this have really been closed? the bakedclay dependency was only part of the issue, and i don't think everyone has agreed w/ me that i3's dependencies are the problem and not 3d_armor's dependencies.

in particular, i don't think that the API bit of 3d_armor should depend on nether, ethereal, etc. noting recipe ingredients should be part of the individual armor submods, right?

from 3d_armor.

...its an autoclosed issue since you linked it in the pr #90

from 3d_armor.

#100

from 3d_armor.

should be fixed with #100

from 3d_armor.