Ommina

Hello! The detailed description of how you got to where you are is certainly valuable. But, at the end of the day (well, any time of the day actually), it is going to be the actual logs that going to provide the necessary details to hopefully solve your startup issue. Part of me wonders if you have installed a client-only mod on a dedicated server. But I may very well be wrong, and it will be the logs that will tell that story.

For what it is worth, I'm seeing the same behaviour as described by the OP: some variation of "can't find the server", depending on which flavour of browser is being used. It resolves, but even their home page fails.

At the risk of intruding into another's thread, I've lost my ability to read crash reports sometime after 1.12.2. If I may ask, what was it that pointed to those particular mods as the culprit? I see just enough guns in the stack trace, but only in conjunction with other, presumably unrelated mods (like a caves generation mod). What narrows it down?

[ Five Months Later ] Did you, perchance, make any progress on this? I'm on 1.21.1 and am experiencing the same inability to find "Direction" in net.minecraft.core -- BlockPos from the same package, fine! The Direction Enum, nope. I don't think I have the patience to deal with the IntelliJ reporting an increasing number of not-really-errors.

I am actually registering separate blocks. I did consider block states, but felt their multiplicative nature would be prohibitive. If that's incorrect I'm willing to give them a go.

Background: For the past few versions (1.14 onward) I've maintained a decorative mod that adds a not insignificant number of blocks. I've done so in the simplest way possible, with a texture and JSONs for each individual block. Inevitably, I got requests for stairs and other models, and here things started to wobble. Memory requirement shot up, sharply, to the point where I felt I had to include stairs and the like as separate addons, so users could install them only if they did not have "Carpenters Blocks" (or something like it) that allowed them to apply an arbitrary block texture to a model. Over the months, I've wondered off-and-on if there is a better way for me to create the blocks that may be a bit more smarter, and a bit less memory hungry. Given a particular world is likely to only use a (smallish) fraction of the available models, perhaps the creation of the models could be postponed until they are actually needed? I don't really want to move to a TileBlock Entity, but could consider it. I've also looked at Baked Models, but here I'm not sure if they will help: I still need to get item models from somewhere, and if I'm creating the block model to create the item's, I've not made any progress. Additionally, I very much want to keep things with as vanilla a feel as possible. Stairs should follow the standard vanilla stair recipe, and be placeable as would a vanilla stair. So -- any thoughts, suggestions, or corrections? How can I best add many blocks, while not increasing memory demands proportionally?

This looks like "Missing Structure Fix"; see if you can do without it. See also https://github.com/Tfarcenim/Missing-Structure-Fix/issues/1

I've never looked into the details of mixins, but given what understanding I do have of them, I can't help but feel this should be a version targeting 1.17.1 instead of 1.16.3.

I need to make sure my understanding is correct. Within a mod, I appreciate that 'things' (whatever that thing might be) are registered in order of Block, Item, <rest of the stuff in whatever order it happen>. However, between mods, if one mod B is dependent on mod A, and is specified as such in mods.toml via ordering="AFTER", can I be confident that blocks from mod A will be registered before mod B registration begins? That is, can mod B fetch mod A blocks and be confident they are registered? I feel that's the whole point of indicating an order, but I've been caught by my own misinterpretations before.

I know it doesn't, and you don't need a sources jar. And not a flatDir repository. url "file:..."

OK. In the build.gradle for the library, at the bottom, there is a section for 'publishing'. Within that section is: repositories { maven { url "file:///${project.projectDir}/mcmodsrepo" } } Make note of the location. Or change it to something you like better. Or change it AND make note of it. I have to do a bit of hand-waving here, as I understand you are using Eclipse, and I don't know the Eclipse way of doing things. In IntelliJ there is a Gradle panel with a publishing section, command named 'publish'. Publish the library using this command. That will put the library into what amounts to a local Maven repository. In your mod, ADD that location to the mod's repositories section, keeping in mind you won't be able to use ${project.projectDir}. (This is why you might want to change it to a known convenient location.) THEN, under dependencies, compile fg.deobf("[path to library jar]") and that's it. The path matches how it appears under the mcmodsrepo folder.

If you've added JEI via gradle, you do NOT need to also add it via other means. Remove the JEI jar from ./run/mods

I'm going to back up here a little bit, to ensure that I'm understanding the goal correctly. You want to add your own library as a dependency of your mod. But you don't necessarily want to be able to edit both the library and the mod at the same time. Building the library, and adding it in via gradle so it is available to the mod is sufficient?

The JEI Getting Started guide includes instructions on editing your build.gradle to add JEI integration. See their Github wiki.

Excellent - I'm glad you were able to get it working there. Minecraft modding is often an exercise in frustration and perseverance. But normally not this soon. I note there is a difference in the two Eclipse screenshots. In the original, the resources tree was displayed with a series of folder icons. In the latter, working version, it's a set of white squares with a cross-hatch. Presumably this is relevant but I couldn't tell you how.