Ugdhar

These mods are known to be very hacky. If you remove them and try it, does it still crash? If so, please post the new debug.log. If not, you know what the problem is!

Really old versions aren't supported anymore. They should still be usable, but no supported is provided for them. In order to receive support, you need to be using a modern version, currently 1.14+ The LTS link at the top of every page has more information on supported versions.

What version is this for? How did you install the server? How are you launching the jar? Does anything happen?

But your logs says:

Where did you download your mods from? Some of the filenames suggest you downloaded them from 9 minecraft, or some other rehosting site, that illegally redistributes mods, and often times have incorrectly labeled versions, or even modified/tampered with files. You should only ever download forge from https://files.minecraftforge.net/ and only ever download mods from https://www.curseforge.com/minecraft/mc-mods See https://stopmodreposts.org/ for more information on what sites to avoid. Also, it looks like you may have fabric mods installed, which will not work with Forge.

You should post your entire debug.log, and not cherry pick it as there can be things in there that could be related that you are omitting without realizing it. Also your textures/blocks folder should be named block instead of blocks (I believe this was one of the 1.13 rewrite changes). That could be why you were getting a missing texture at on point like you mentioned. *edit: and in your blockstate, you need to specify at least 1 state for the block, if there's no variants use empty "", and it must specify a model for that state, and you have empty curly braces. The vanilla blockstates, if you wish to reference them, are in the client-extras jar in your IDEs referenced libraries.

I am not completely sure to be honest, I've always kept my installations separate to avoid potential world corruption, so that wasn't a feature I myself used, sorry!

This feature was removed as the launcher installations are the preferred method of separating mods for different versions.

Are the folders those packages represent separated by slashes and not dots? Just want to make sure, I've seen them be made using the dots in the folder names, which breaks stuff. i.e the folder should be assets/ringsandthings, not assets.ringsandthings

According to https://gist.github.com/williewillus/353c872bcf1a6ace9921189f6100d09a

It says it cant find this file. Double check folder/package names and that the file exists. use . instead of : i.e. item.modid.itemid

Your textures are in the wrong package/folder according to your screenshot. They should be in textures.item not textures.items, they were changed with 1.13 (I think it was) to match up with the same package structure as the models.

protected int energy; protected int capacity; protected int maxReceive; protected int maxExtract; Also in case you weren't aware, Items are singletons, so any fields you set in your Item classes are shared among all instances of that Item across the game world.

No prob, had the same problem myself while tinkering. Figures I've been tinkering with dimensions and worldgen, I believe a lot is going to change with it with 1.16! So relearning it'll be! lol

YourDimensionClass#getFogColor cannot return null

Then I guess post the new crashlog, that's weird there's no debug.log.

I don't think BoatEntity#getBoatType() will work for modded boats, as the BoatEntity.Type enum is coded with the vanilla boat materials, and doesnot appear extensible.

Post the new debug.log without optifine

BoatEntity#getItemBoat() And I'd poke around the recipe system maybe, I'm sure there's a way to get the ingredients/recipe for an item.

Check your debug.log, it will probably have an error in there somewhere about it, as it looks like the missing texture colors

Look closer at the registry event code, you've got 2 lines of code from my example smashed together into 1 line of code. Mine: @SubscribeEvent public static void registerFeatures(RegistryEvent.Register<Feature<?>> args) { StrucTest.BRICK_HOUSE_PIECE = Registry.register(Registry.STRUCTURE_PIECE, StrucTest.HOUSE_LOC, BrickHousePiece.Piece::new); args.getRegistry().register(new BrickHouse(NoFeatureConfig::deserialize).setRegistryName(StrucTest.HOUSE_LOC)); } Yours: public static void registerFeatures(RegistryEvent.Register<Feature<?>> args) { ModStructurePieceTypes.TOWER_PIECE = Registry.register(Registry.STRUCTURE_PIECE, ModStructurePieceTypes.TOWER_LOC, TowerPiece.Piece::new, args.getRegistry().register(new Tower(NoFeatureConfig::deserialize) .setRegistryName(ModStructurePieceTypes.TOWER_LOC))); } Also please post your debug.log (pref. as a github gist), it will provide more info than summarized error messages

Look at vanilla water or lava, and use net.minecraftforge.fluids.ForgeFlowingFluid Give it a try, if it doesn't work, post links to code and debug.log (or if you have it from your previous failed attempt, post that)

What version is this for? And you should post debug.log from both the client and server

You want to use the FMLClientSetupEvent and use RenderTypeLookup.setRenderLayer on your block with the RenderType you want. First mistakenly thought someone was saying those links weren't working, but I think it was more of a hint to use the forums search, as this question has been asked a million times already

Then you are probably not in the same folder/directory as the installer when you are running the command. the command dir will show files in your current location, make sure the forge installer is there.