warjort

You are not setting the position for the lightning bolt entity. It is probably spawning at 0,0,0 Look at ServerLevel.tickChunk() for how vanilla does it. I assume you are spawning it on the server? See https://forge.gemwire.uk/wiki/Making_Entities for how to define the attributes for your entity and other things. The parameter passed to build() is used by DFU (datafixerupper) So it's pretty much irrelevant unless Mojang somehow know about your Entity and want to apply a fix to its persistent data. 🙂

Issue with FTB Essentials or ftblibrary. Check you have the latest versions of these mods then the contact the mod author(s).

Looks like a conflict between quark and xnet. It says it is ignoring the problem, but you should check with the mod authors to see if this is your issue.

Did you check the debug.log on both the client and server? I don't know how you expect me to help if I can't see the logs to look for potential problems. If you are confident it's not the mods whose blocks you are having problems with, I don't know. Maybe you've installed a mod that has like 100 downloads and was never properly tested outside of singleplayer? The mods with alpha or beta in the name would be my first candidates. I don't see an obvious problem in the mod list, like using a mod that's meant for minecraft 1.19. The debug log lists the found mods at the start. You could have killed 2 birds with 1 stone. 🙂

You can't have both jade and wthit, they are different forks of Waila.

One of your mods has broken networking code. There is no information in that error to say which one. Post the debug.log. Or experiment with removing mods until you find the problem mod. (Backup your world before removing mods).

I am "not sure" either, since you don't post the log. You haven't actually shown it is calling that register method. Only that there is a static method that does, which may or may not be called. Debuggers or logging are your friend.

https://forge.gemwire.uk/wiki/Capabilities#IItemHandler (for NOT using WorldlyContainer) https://forge.gemwire.uk/wiki/Capabilities/Attaching#Persisting_LevelChunk_and_BlockEntity_capabilities (for marking a block entity changed when its inventory actually changes) https://forge.gemwire.uk/wiki/Block_Entities (block entities in general)

The error says your entity is not registered. But you don't show the code that does that. Most likely because you haven't called register(IEventBus) for your EntityType's DeferredRegister https://forge.gemwire.uk/wiki/Registration/1.18 but there could be error in your run/logs/debug.log. You should also register your renderer by subscribing to EntityRenderersEvent.RegisterRenderers on the mod event bus with value = Dist.CLIENT

Just use the latest release of forge for 1.18.2 This kind of thing usually happens because mods want recent versions of forge for bug fixes and new features. e.g. create requires at least forge 40.1.60 while you have 40.1.0 https://github.com/Creators-of-Create/Create/blob/0c5ccf38ee15f446f385290f2238f2ae975681cd/gradle.properties#L11

If you want help you need to show the debug.log maybe there is an error that explains why there is a problem? The modlist you show doesn't even contain version numbers. But you should really contact the mod author. There is nothing we can do to fix mods, only point you at which mod is causing problems. You seem to already know that?

Show the error you are getting. If you add --stacktrace or --debug when building on the command line it will show the full error.

How can this be a bug in forge gradle if your standalone program is also giving you the same error? This is the code that forge gradle uses. It's just a URL.openStream() https://github.com/MinecraftForge/ForgeGradle/blob/1fce46ef54e42adb69176edb0e8c3401a707b39c/src/common/java/net/minecraftforge/gradle/common/tasks/DownloadMCMeta.java#L53 All the details are handled by java or beneath that your OS. I can only suggest you check your OS is up-to-date. And try a different more recent java, e.g. https://adoptium.net/ You can also ask on fedora's support forum to see if there are known issues in this area. Something like changing a dns cache setting may fix it?

Issue(s) with the krypton mod, check you have the latest version then contact the mod author.

IWorldReader is 1.16 and before. I guess you are following an out-of-date tutorial? There will probably be more than just class names that need changing. But if you really want to continue with it, use the discord bot mentioned in the link I provided to get the modern names of classes.

Use the 1.19.2 version of journeymap https://www.curseforge.com/minecraft/mc-mods/journeymap/files/all?filter-game-version=1738749986%3A73407

https://gist.github.com/50ap5ud5/beebcf056cbdd3c922cc8993689428f4#full-migration-to-mojang-mappings

This is some issue with your network connection. This recent thread (for a related error) rehearses some of the likely causes. https://forums.minecraftforge.net/topic/117671-forge-1181-mdk-error-building-the-project-could-not-find-netminecraftclient1181/#comment-518295 But we don't in general provide PC support in this forum.

As I said above. Delete this file it is corrupt. Forge will recreate it with default values. The new log you posted doesn't even show you starting minecraft.

Look at how the FenceBlock works. Note how the getStateForPlacement() and updateShape() uses connectsTo() to change the BlockState based on which blocks are around it. And how it uses a multipart blockstates to include multiple models depending upon the BlockState's properties (which sides it connects). https://github.com/misode/mcmeta/blob/assets/assets/minecraft/blockstates/acacia_fence.json

You are missing the structure_gel and balm mods.

Depending upon what you are doing there is more you need to do with this. You should really be using SpawnPlacements.checkSpawnRules(). That way you will include the rules defined by vanilla and mods for their blocks and entities. As part of it, it uses BlockStateBase.isValidSpawn(), which by default uses BlockStateBase.isFaceSturdy(). That is essentially what you asked for but not the complete answer. You can also look at NaturalSpawner and BaseSpawner if you are interested in the full logic for mob spawning. e.g. firing the forge events canEntitySpawn() and doSpecialSpawn() to allow other "3rd party" mods to apply their policies to spawns for entities they didn't write (such as vanilla mobs).

https://forge.gemwire.uk/wiki/Custom_Item_Animations

I don't really have much to add unless you post a link to your debug.log You don't show any new information, e.g. if other errors occur before these message that might explain what is happening or at least which entity(s) has the problem But did you try restoring your world from a recent backup before you started getting this problem?

There is an option in world/serverconfig/forge-server.toml that will remove broken entities instead of crashing the game. NOTE: The big warning about how this might itself cause problems.