warjort

Issue with brutalbosses, make sure you have the latest version then contact the mod author.

See: https://forums.minecraftforge.net/topic/114981-render-thread-error-on-intellij-apple-silicon-m1/

The things you are describing sound like curseforge issues. It's not the same thing as minecraftforge. Ask for help here: https://support.curseforge.com/en/support/home

Yes for the event name. For the furnace ticker look at BlastFurnaceBlock.getTicker() and how its helper method creates a server side ticker for AbstractFurnaceBlockEntity.serverTick() The "litTime" in the BlockEntity would be equivalent to your ticks.

In 1.18.2 it is called WorldTickEvent I think if you subscribe to TickEvent you will get all tick events; server, level, player, etc. ? So you will get a lot more events than you want. As described above, you need to look at event.phase (either START or END) otherwise you will be doubling counting. Similarly, you might want to check event.side if you don't want your code to run on both the logical client and server, usually ticking is only done on the client to support things like animations. Finally, you can't store the ticking/ticks like you are probably doing. What if there are 2 blocks that you need to tick? What if somebody restarts the game while it is ticking. What is going to save/reload the ticking/ticks state? See the comments above about capabilities for how to solve this.

You can find the forge renames here: https://gist.github.com/SizableShrimp/882a671ff74256d150776da08c89ef72 The vanishing StructureFeatures is a Mojang change. The "equivalent" is now called StructureTypes which you can find in the vanilla Registry class. I know very little about structures in 1.18, 1.19 or any other version so I can't help you with the rest of your question. 🙂

This is an error with the elementalswords mod. Make sure you have the latest version then contact the mod author.

This is an error in a some configuration for structure processors. Either in a datapack you added or one of your mods. One of the things mentioned in that json is "stoneholm". According to curseforge, this mod does not have a version that is compatible with 1.18.2 https://www.curseforge.com/minecraft/mc-mods/stoneholm-forge/files

Your other questions would be better directed at Mojang/Microsoft. 🙂

This shows a crash after a server tick took more than 60 seconds. Mojang automatically crash the server when this happens assuming something is very wrong and that you will have something that restarts it. The stacktrace is a snapshot of what is happening at 60 seconds so it may or may not show what was actually taking a long time. In this case, it is that mixin again I mentioned earlier. Where it is searching for a feature using the chunk generator. From that it looks like one of yungsapi, betterdeserttemples, pollen or byg is responsible for the mixin. It might not be this mixin that is the cause, beyond what I said above, it could be some other mod "breaking" the chunk generator. But the fact this mixin has shown up twice now means it is something you should research with those mod authors.

Normally there are 2 ways to get a block to tick. Use a BlockEntity (like a furnace keeping track of burn time) or have the block implement random ticking (like crop growth). You can also use the LevelTickEvent to implement more generic things, but for your usecase you will then have the problem of where to keep track of per block state. You might for example attach a capability to the LevelChunk that contains the block to hold the data? See DataStorage here: https://forge.gemwire.uk/wiki/Main_Page

That 16 threads might be misleading, I am not sure what number it is reporting. e.g. whether it the total numbers of cores you have or something else.

Minecraft only has 1 server thread, its not a multithreaded game. It has other threads to offload work, like the network thread but they will likely be I/O bound. A useful metric might be to divide 100% by the 16 threads you have. That gives one thread (e.g. the server thread) running at full throttle being 6.25% of total cpu available.

Another thing it might be is your gradle cache is corrupted and you have an incomplete download of one the jars? If you exit your ide, then delete YOUR_HOME_DIRECTORY/.gradle/caches/forge_gradle that will mean everything gets redownloaded.

Can you run the vanilla game or the mdk on that machine?

I don't see anything in that log. The problem is the code in net.minecraft.client.main.Main.main is poorly written by Mojang. Pseudo code: try { // initialise } catch (Throwable throwable1) { // create for crash report } It looks like creating the crash report itself is crashing, so we can't see the real error "throwable1"? You could try to run it using a debugger to see what throwable1 is.

The error says there is something wrong with initializing the render system/opengl. Maybe the logs/debug.log has more information?

The versions of those 3 mods are for the beta. If you downgrade to a beta version of forge (not recommended) you will have to find versions of all your other mods that were also made for the beta (assuming that they even exist).

The versions of mining gadgets, whisperwoods and baubly heart canisters that you have, have not been updated to work with the forge 1.19 recommended release. Check you have the latest version, otherwise you will have to wait for the mod authors to update them.

Looking at your other view it seems to be spending most of its time ticking entities I don't see anything standing out within that. Though 5% of it is from a mixin to the ServerPlayer where it is searching for something on the map. The author of that mixin has not been very helpful. Its name "injectMethod" does not identify the mod.

e.g. when I look at your profile summary it shows this: With the top one being: So it is spending 10% of its time handling aiimprovement modifiers on entity spawns.

Your link is showing is an average of 10 ticks/sec when it should be 20. Since you already have spark: https://spark.lucko.me/docs/guides/Finding-lag-spikes

Doesn't BlockEvent.BreakEvent let you do this? It seems weird to have an unbreakable block in creative. 🙂

You can look at the static method Block.pushEntitiesUp() that is to avoid entities getting stuck inside blocks. Maybe you can adapt the logic to your usecase?

It's never going to be fully charged *after* an attack. Look at Player.attack() in particular where resetAttackStrengthTicker() is used compared with EnchanmentHelper.doPostDamageEffects()