Useful information to include:

• Minecraft version 1.18.2
• CC: Restitched version 1.100.5
• Logs:
  crash-2022-05-26_20.36.06-client.txt
  didn't load up long enough for a latest.log
• Please send latest.log AND the appropriate crashlog,
• Detailed reproduction steps: Not quite sure

can you try with Not Enough Crashes AND the lastest version of CC:R? 1.100.6

it looks like something in the modpack is trying to register an turtle peripheral, and failing badly

yep! it even links you (on the right side of that message) to where alloy forgery threw an error,
line 1063
https://mclo.gs/PerHJsU#L1063

thanks for the help.

it also censors information it considers private (such as your windows username) so it helps with privacy!

WOW that site is handy.

This makes my headache so much less.

if you use https://polymc.org for your launcher, it will generate an log that can then be uploaded through an button

can you test with just CC:R and ACE? (plus fabric api) I just tested with latest versions of all and have had no issues,

please send the latest.log, because if it is registering that type of error, then an latest.log has indeed been generated

Then it's probably something to do with a mod conflict. I'm probably back at square one on trying to figure out which one it is.

Regardless, it's obviously not CC. for my sanity, Here's the logs of my modpack with polymc. Can you discern what might be the problem?
latest.log
crash-2022-05-27_22.24.04-server.txt
crash-2022-05-27_22.24.07-client.txt

for me, it only mentions CC as a potential problem.

please upload to https://mclo.gs so I dont have to download them,

there is an reason I say to do this as it color codes the logs so anyone can read them easily

latest log: https://mclo.gs/PerHJsU
Server crash: https://mclo.gs/gDD8scR
client crash: https://mclo.gs/sROMq05

now look at latest.log on the website, see how at the top it gives you an rundown of the MC environment?

it also says that an mod as thrown an error

Oh, that's handy. So it suspects alloy forgery?

it didn't get to the loading screen
crash.txt

Here's what I've gathered from reading through the logs:

1. The server crashes because of a mixin transformation error. The mixin in question is from the mod Arcanus.
2. Alloy Forgery gets blamed for the server crash because they're at the base of the stack trace. Their main class's static initializer sets up some sort of particle system library that touches the mixin's target class.
3. CC: Resitched manages to cause a client crash because the server crash prevented our initialization from completing and we assume elsewhere in the code that it always will. We could fix this just so we're not blamed for future unrelated crashes.

I don't know why Arcanus's mixin is failing. I'd file an issue over there so they can look into it.

Sadly arcanus isn't being updated, it's why i tried to test out ace before i commit to swapping.

I should probably just remove arcanus.